I'm getting an error with exporting the database that's housed in SQL Azure. The database itself is already v12. When I try to export the database, I get this error:
The element ExtAuth_Key10 is not supported in Microsoft Azure SQL Database v12. (Microsoft.Data.Tools.Schema.Sql)
I checked the related posts and saw that one recommendation was to update the DacFx framework. I've installed the latest I can find from Microsoft (16.5 at time of writing) as well as the SSMS (16.5.3 at time of writing). However I still get the same error.
It's very puzzling because this is an export operation, so it does not make sense to have something that is not supported in a V12 database in well, a V12 database.
What can be done to export this?
What element is ExtAuth_Key10? is that a master key?
The latest version of SSDT bundled wtih DacFX is RC 3 https://learn.microsoft.com/en-us/sql/ssdt/sql-server-data-tools-ssdt-release-candidate
Can you give that a try and let me know if you see any errors?
Related
I have a live SQL Server database which was originally on an Express version and has compatibility 100. I am inspecting it using SSMS 2016 RC, which seems to have highest compatibility level of 120.
On performing the task Deploy Database to Microsoft Azure SQL Database... it goes through all the verification steps and then bails out with the error:
Could not import package. Unable to connect to master or target server X. You must have a user with the same password in master or target server X
Is the only solution to upgrade the compatibility version of the database and is that even possible from such an old level? Do I have to install a newer SSMS to do this?
I've seen a similar question below, but it refers to SSDT, not SSMS:
SSDT failing to publish: "Unable to connect to master or target server"
I installed latest SSMS v18.3 and performed the deploy operation again and it went through without a hitch, without even requiring me to change the compatibility level
Tried to export data in CosmosDB but it was not successful. According to https://learn.microsoft.com/en-us/azure/cosmos-db/storage-explorer, by using this tool I can export the data inside the cosmosdb, but no option to export. Tried to do the instructions here https://azure.microsoft.com/en-us/updates/documentdb-data-migration-tool/ and https://learn.microsoft.com/en-us/azure/cosmos-db/import-data#JSON, but error is being encountered.
Can you help me how to do this in Data Factory or any steps just to manual backup cosmos DB?
i tried doing the backup through azure data factory but data factory can't seem to connect to cosmos db, it's so weird 'cause the primary string/secondary string that I used is in the details of the cosmos db
Thank you.
Can you help me how to do this in Data Factory
According to your description,it seems you have trouble with export data,not import data. You could use Copy activity in ADF which supports cosmos db connector.For you needs,cosmos db is source dataset and please add one more sink dataset(destination). Such as some json files in the blob storage.Just make sure you configure right authentication information with your cosmos db account.
ADF is more suitable for the batch back up or daily back up.
or any steps just to manual backup cosmos DB
Yes,Storage Explorer is not for exporting data from cosmos db,Data migration tool is the suitable option.Please install the tool and refer to some details from this link:https://learn.microsoft.com/en-us/azure/cosmos-db/import-data#export-to-json-file
DMT is more suitable for single back up.Surely,it also supports execution in the batch if you use command line to execute it.
Cosmos DB Data Migration tool can be used to export data from Cosmos DB.
Refer https://learn.microsoft.com/en-us/azure/cosmos-db/import-data#export-to-json-file
this one worked for me... since my SSL in my Macbook did not work, I did these steps from the Azure VM that I created.
Steps:
Download MongoDB Community Server Client tool as per your OS version and MongoDB compatible version.
(Or you can download [v3.2.22 for Windows X64] directly at here, please don’t download the version beyond 4.2 as it’s incompatible)
After installing the MongoDB client tools, go to the installation directory -> go to the subfolder “bin” containing the mongoexport.exe, then issue below command to export your data:
mongoexport --host=: -u= -p= --db= --collection= --ssl --sslAllowInvalidCertificates --out=
Note 1: You can find the , , and in Cosmos DB Portal – “Connection String”
Attempting to view the a view or procedure:
from SQL Server Management Studio 17.4 in Azure SQL Datawarehouse notes the error:
I can however, delete and create any object that I want.
How can I work to ensure I can view the objects definition?
UPDATED
Concerning setting the options in SSMS to SQL Datawarehouse, there is not that option:
Please change this setting under Tools... Options. That should resolve the error. I wish we didn't have to change this but at lease we have a workaround.
In SSMS 17.5 there are a few more options. You can have it automatically detect what type of database you're connected to and script accordingly. Or you can force it to script for a particular database type like the following screenshot.
It appears there is a bug in certain versions of SSMS (such as 17.5) where if the DW user isn't also a user in the master database then scripting fails. The easy fix for this is having the server admin connect to the master database and run:
CREATE USER MyUserNameHere FROM LOGIN MyUserNameHere;
Sorry you're seeing this. I've been able to repro this on SSMS 17.4 and 17.5. We are looking at this now.
This seems to be a defect in the upgrade path for 17.5 as this should be supported without having to change the script settings. We are investigating this and will try to get an update out as soon as possible.
I have a SQL Azure database which is approximately 10GB in total size.
I wanted to have a local copy of the database for development so I saved an export of the database to my storage account and downloaded it. I was a little suspicious when the backup size was 500MB but I backed up the database twice, the file size was the same both times.
I am using SSMS 2014 on a SQL Server 2012 database and selecting 'import data tier application', the backup appears to be working BUT I get an error with the largest table. The error is:
TITLE: Microsoft SQL Server Management Studio
Data plan execution failed with message One or more errors occurred.
(Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
One or more errors occurred. (mscorlib)
One or more errors occurred.
One or more errors occurred.
Unknown block type. Stream might be corrupted. (System)
I cannot find any examples of others with this problem, but it can't be only me that has it?
FYI When I try to use SSMS 2012 to import that database I get the following error:
TITLE: Microsoft SQL Server Management Studio
Could not load schema model from package. (Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
Internal Error. The database platform service with type
Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is
not valid. You must make sure the service is loaded, or you must
provide the full type name of a valid database platform service.
(Microsoft.Data.Tools.Schema.Sql)
Which is why I installed 2014.
#
UPDATE, After installing SSMS 2016 I got the same error:
TITLE: Microsoft SQL Server Management Studio
Data plan execution failed with message One or more errors occurred. (Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
One or more errors occurred. (mscorlib)
One or more errors occurred.
One or more errors occurred.
Unknown block type. Stream might be corrupted. (System)
Please try with the latest version of SSMS that you can download and install from SQL Server Management Studio Download page
Azure SQL Database has a numerous new features being added in a fast pace manner. SSMS from this unified download page provides up-to-date supports for the latest features in Azure SQL Database.
That error indicates that the compressed table data stored in the bacpac file couldn't be decompressed. That can happen if the file gets corrupted at some point during a file copy operation. If it happens with multiple bacpac files, though, that would be concerning. Have you tried exporting the bacpac a second time?
A couple of days ago I set up Azure Database Sync in order to keep the backup DB and the primary one synced. But after doing that, the database used as a hub is no longer visible on SSMS Object Explorer. If I stop the DB Sync, it shows up normally. I have admin rights on the database. The problem is that if I have to check anything on the database, now I cannot. Has anyone any advice about this issue?
UPDATE:
For everyone facing the same issue, one workaround is to open the database via Visual Studio. in VS, the database is listed as it should be
Applying getting the latest SSMS will most likely solve this problem.
msdn.microsoft.com/en-us/library/mt238290.aspx