-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use DMT. #176
Comments
@jenkins123 thank you for reaching out have you seen this part of the README: https://github.com/AzureCosmosDB/data-migration-desktop-tool#using-the-command-line. I just double checked on macOS Sequoia that the current release of dmt works. Here's output from my terminal: If you are running the release out of your Downloads folder make sure:
|
Hi Mr Phil, Thank you for the response, yeah I figured it out that it was a permissions issue and could run the tool. the config I am using is {
}, |
Hi, I just confirmed on the same Mac with the latest 2.2.0 release and your settings file that I was able to transfer data from Cosmos DB to JSON. It sounds like perhaps your connection string isn't correct. You can copy the connection string directly from the Settings->Keys section in Azure Cosmos DB account (https://learn.microsoft.com/azure/cosmos-db/nosql/tutorial-dotnet-console-app#create-api-for-nosql-resources). Can you also check that you can access the database from Azure Portal and view data in the Data Explorer? |
@jenkins123, hi wanted to see if copying your connection string directly from the Azure Cosmos DB account was able to resolve your issue. I've spent an extensive amount of time using dmt on macOS this week and it's been working great. |
I have downloaded the data migration tool on Mac machine, and tried to execute the dmt.
but I am unable to execute the dmt from terminal, I see error
sudo: dmt: command not found
I tried setting up the dmt file in the path , still no use. Not sure what need to be done to run this tool.
The text was updated successfully, but these errors were encountered: