Manual Azure Backup Cosmos DB - azure

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”

Related

Azure SDK - Copy Azure SQL database Schema only through code

Currently use the Microsoft.Azure.Management.Fluent libraries in our solution to create copies of Azure SQL databases - works well:
await server.Databases.Define(databaseName).WithExistingElasticPool(elasticPoolName).WithSourceDatabase(source).WithMode(CreateMode.Copy).CreateAsync();
Is there a way to do the same thing but only copy the schema - no data rows?
I was hoping for a WithMode option but nothing stands out in the documentation.
Thanks much in advance

tCosmosDBConnection component is not showing in Talend Open Studio for Data Integration

Im using Talend Open Studio fro Data Integration Version 7.1.1. I need to Connect Azure Database to data extract and data upload from Talend to our SQL databases. I have gone through below link to connect to Azure cosmos dbs.
https://help.talend.com/r/OgamG5JTIU2aMhx2HjGp8g/L1KG9WTDgOCS8RO9RzqIQw
But in my Talend DB Connection I can find the any CosmosDBconnection type or component. Even I tried to search in packages but didnt find. Could someone tell me how install or enable CosmosDBConnection or how to connect to Cosmos database using Talend.
As per Talend documentation -
tCosmosDBConnection
Creates a connection to a CosmosDB database and reuse that connection in other components.
tCosmosDBConnection Standard properties
These properties are used to configure tCosmosDBConnection running in the Standard Job framework.
The Standard tCosmosDBConnection component belongs to the Cloud and
the Databases families.
The component in this framework is available in all Talend products
with Big Data.
As you are using Talend Open Studio for Data Integration Version 7.1.1, you are not able to see these specific components in your palette.
Also, you might want to check out Project Settings -> Designer -> Palette settings and check out the components that are available and selected for your studio.

Cannot view object schema Azure Datawarehouse

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.

Cannot export a BACPAC from SQL Azure -- ExtAuth_Key10 is not supported in Microsoft Azure SQL Database v12

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?

Cannot connect to Azure SQL Data Warehouse database-error "Incorrect syntax near 'ANSI_NULLS'"

I could successfully deliver the new Azure SQL Data Warehouse database.
If Í try to connect to the SQL Data Warehouse Database, I receive following error message:
"Parse error at line: 1 ,column: 5: Incorrect syntax near 'ANSI_NULLS'".
This happens in VS 2013 and VS 2015! The data load process with BCP to the SQL Data Warehouse database was successfully!
Thanks, Herbert
Azure SQL Data Warehouse does not currently support setting ANSI_NULLS on (SET ANSI_NULL ON). You can simply remove that statement from your query and you should have success.
Additionally, make sure that you are running the June 2015 Preview of SSDT (http://blogs.msdn.com/b/ssdt/archive/2015/06/24/ssdt-june-2015-preview.aspx). This has the supported SSDT capabilities for SQL Data Warehouse.
I had the same error, when tried to Use Visual Studio to query Azure SQL Data Warehouse 
 and selected my database.
The Workaround was to select master database, connect to it, then in top drop-down for the query change to my database.
I think your connection isn't actually recognised as a SQL DW connection. I bet your query window is a .sql file, not a .dsql as it needs to be. If you connect as a .sql query, it will try to set various settings that aren't supported.
Go back into the Azure portal and use the link to connect using SSDT from there. You should get a connection in the SQL Server Explorer pane which looks different, and when you start a New Query based on it, you should get a .dsql window, not a .sql one.

Resources