Visual Studio Database Project Will Not Be Used for SQL Azure

Question

I ran into a problem very similar to. I have a Visual Studio.dbproj database project. It works great in SQL Server Express. Now I want to deploy it to SQL Azure - I change the connection settings, but the deployment does not work with the following text:

C: \ Program Files \ MSBuild \ Microsoft \ VisualStudio \ v10.0 \ TeamData \ Microsoft.Data.Schema.TSqlTasks.targets (120.5): Error Deploy01234: The target database schema provider could not be determined. Deployment cannot continue. Completed the task "SqlDeployTask" - FAILED.

Is deployment of .dbproj projects for SQL Azure supported? How to get Visual Studio to deploy a database in SQL Azure? What are other ways to achieve more or less the same results besides recreating the database manually using the Azure portal?

Answer 1

As far as I know, database projects are still not supported by Windows Azure. You can deploy the project to a local SQL server, and then use the Generate Scripts function to transfer the database to Azure SQL. See Link.

Answer 2

If you use Visual Studio 2012, now you can create a database project and go to "Properties" - set its target platform to the "SQL Azure" tab on the "Project Settings" tab. You can also configure a parameter for dacpac output. Use this file to import directly as a new Azure SQL Database.

Answer 3

A simple solution is to create a local database and use the Azure Migration Wizard to migrate to Azure SQL. It works very well in just a few clicks (and fixes common errors).

Answer 4

Database projects do not work with SQL Azure. I do this before deployment, create a new database on the local server (to make sure it is updated without dev scripts), and then synchronize this database with Azure using RedGate SQL Compare. First, I back up with RedGate SQL Azure backup backup.

Answer 5

When we first built database projects, SQLAzure was still experiencing a crisis of its identity and did not know what it wanted .;)

DBProjects supports a significant superset of features compared to SQLAzure. Therefore, it is possible that he will create scripts that will not work against SQLAzure.

I know that a team using DBProject tools looked at restricting database project generators to output SQLAzure compatible scripts, but I don’t know how far they reached or whether they decided to continue.

I suggest the echo dunnry above and use the Azure Migration Wizard for migration or Jeremy and use SQL 2008 R2 and create Azure compatible scripts.