SQL Azure -- VS.NET Database Project and/or Data Tier Project support?


  • I am familiar with SQL Azure Explorer, but...

    Will Visual Studio 2010 support SQL Azure in either Database Projects (e.g. like VS.NET 2008 Database Edition does for SQL 2005/2008) or in the new Data Tier projects? If so are they supported in the RC of VS 2010? If not... any plans? When?
    Friday, February 12, 2010 7:37 PM


All replies

  • VS2010 supports Data Tier projects (Beta 2) and should do so in the RC. I have not installed RC yet. Beta 2 also supported VB and C# SQL CLR Database Projects. All of these under Datbase templates.
    However I have not tested with SQL Azure.


    I don't believe it can support Data Tier projects with SQL Azure since you do not have support for this in SQL Server 2008 R2's SSMS.l
    Saturday, February 13, 2010 1:15 PM
  • Hello, currently VS 2010 Database projects do not support SQL Azure directly. The script generated by Visual Studio contains a lot of features that are incompatible with SQL Azure. But you can first deploy the database project to a local SQL Server, and then use SSMS 2008 R2's "Generate scripts" feature to port the database to SQL Azure as described in This approach works fine for me. That is: Develop against local SQL Server using Visual Studio, and then deploy to SQL Azure using SSMS.
    Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, February 15, 2010 2:25 AM
  • Jayaram, I am already aware that Data Tier projects are in Visual Studio 2010, the question is whether or not they support SQL Azure. Also, you do have support for SQL Azure in SQL 2008's SSMS R2 -- I'm not sure if you were trying to say that you don't or if you meant that you don't have support for data tier projects in SSMS R2?
    Friday, February 19, 2010 4:55 PM
  • Yi-Lun,

    Thank you for clarifying and for the additional information you provided.

    While it is certainly helpful to be able to use SSMS R2 to "Generate scripts" for SQL Azure, this really only addresses a one-time deployment to Azure (or a schema copy from Azure back down to a local database, but without the data). It flat-out misses the normal use case of ongoing development and updates to a maturing website. For example, you can use Schema Compare in VSDB to aid in the generation of migration scripts. Data Tier projects have similar, even enhanced, functionality for updating a target database with new schema (and possibly data) changes.

    Perhaps the SQL Azure team can lobby the VSDB team to add support for SQL Azure databases as a project type. This would allow these enhanced productivity tools to be used. As it currently stands, a great deal of manual labor would be involved in trying to pull down the production schema from a SQL Azure database to a local environment and/or generating migration scripts which then need to be hand modified and thoroughly tested before running them against a SQL Azure database. At the very least, the ability to take a snapshot of an Azure database, restore it to a local SQL 2008 server, do schema compares, and then modify the output to be Azure compatible, would be very useful. Even better though would be the ability to run Schema Compare directly from VSDB against a SQL Azure database.

    Friday, February 19, 2010 5:05 PM
  • Please consider this to be a request for support for SQL Azure Database Projects in VSDB 2008 as well as VS2010 for both Database Projects and Data Tier Projects. See also
    Saturday, February 27, 2010 6:57 PM

    The Data-tier Application projects in VS 2010 RTM will have partial support for SQL Azure. It allows you to connect directly to SQL Azure databse and import your schema in the project using the 'Import Data-tier Application' wizard. You can also deploy the schema back to SQL Azure service. However, upgrading the target database is not supported i.e. its a one time deployment. The data copying will require manual steps.
    Wednesday, March 03, 2010 4:18 PM
  • I'd like to second (or third) these requests.  Database Projects are fantastic for my purposes, and being unable to use my Database Project to automatically deploy to SQL Azure as my production database is a blow. I have no doubt it will come in time; clearly that's the direction Microsoft is going in.  But sooner would definitely be better for me.


    David Cater

    Thursday, April 01, 2010 6:31 AM
  • I'd like to third (or fourth) these requests, I am sure this is being worked on ? But right now its sucking time in a major way. 
    Friday, July 01, 2011 9:47 PM
  • You folks might want to check out SQL Server Developer Tools, Codenamed "Juneau" that's available here: SSDT is an evolution of the existing Visual Studio Database project type and also supports DACPACs and deploying to SQL Azure.

    Sanjay Nagamangalam Principal Program Manager, SQL Server Manageability

    Friday, July 15, 2011 7:16 PM