What is a good way to copy a dev database to an Azure database?

Question

0.00/5 (No votes)

See more:

Right now I'm in my 10th minute of waiting for a script to create schema and data on Azure, through a VS 2015 connection. This morning I did this three times, each resulting in some line of script that Azure didn't like, so I had to remove it and try again.

I generated the script with the "Generate scripts" wizard in SSMS, for SQL 2014 and then for 2012, and still had to edit out bits Azure didn't like, e.g.

Quote:
Keyword or statement option 'GLOBAL' is not supported in this version of SQL Server.

I'm wondering if I can't perhaps upload a .bak of the db to Azure Storage, and then do a restore all on the server side. I tried their new Sync tooling, but found the UI and docs obscure and or inaccurate or outdated.

Posted 25-Sep-15 4:52am

Brady Kelly

Add a Solution

Comments

Afzaal Ahmad Zeeshan 25-Sep-15 12:50pm

Deploy it?

But, I would recommend always create a new database for your schema with the database server provided on the hosting environment. This allows you to not only ignore these errors that come up with a conflict of features and services, but you also get to know how-to create the database there.

[no name] 25-Sep-15 14:30pm

[Delete]
Not sure whether this help. Acording to your rep Points most probably not :)
http://stackoverflow.com/questions/5475306/how-do-i-copy-sql-azure-database-to-my-local-development-server[^]
[/Delete]
Was more the other way :(

Brady Kelly 25-Sep-15 14:47pm

Somewhat useful. I might be able to use the BACPAC approach moving to Azure as well as from.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)