Developing Data-tier Applications using Visual Studio 2010

Play Developing Data-tier Applications using Visual Studio 2010
Sign in to queue


DBAs and developers alike find it hard to effectively develop, deploy and manage a data-tier application throughout its lifecycle. SQL Server developers today want to create a data-tier application they can test, declaratively deploy across multiple instances while the system deals with version upgrades. SQL Server DBAs on the other hand want to know deployment requirements a priori and they too want the system to perform some of the mechanical upgrade operations instead of managing data-tier applications via a bunch of scripts. In this video we will dive into Microsoft’s investments in the SQL Server data-tier application space and demonstrate the concepts and tools that simplify development and deployment of data-tier applications using Visual Studio 2010 and SQL Server Management Studio in SQL Server 2008 R2.


NOTE: Visual Studio 2010 Beta2 currently supports deploying Data-tier applications only to SQL Server 2008 R2. Please download and install the upcoming CTP3 of SQL Server 2008 R2 in order to use Data-tier Application Projects in Visual Studio 2010 Beta2.



Download this episode

The Discussion

  • User profile image

    Does it work with SQL Azure?

  • User profile image

    Hey Now Elisaj,


    Nice vid, @ 11:30 minutes when debugging Stored Procedures in VS10 sure is a good example.


    Thx 4 the info,


  • User profile image

    Hey, Elisaj, this really fixes many deployment issues we have currently at the bank.


    I'm trying to test this out as in the vid but get this error when trying to deploy:




    MyProj.dacpac(0,0): Error :

    -->An exception occurred while executing a Transact-SQL statement or batch.

    -->Invalid object name 'msdb.dbo.sysdac_instances'.



    I am running Sql Server 2008 Developer (version 10.0.1600.22), and VS 10 (Version 10.0.21006.1 B2Rel)

  • User profile image

    Answered my own question: CTP3 of SQL Server 2008 R2

  • User profile image


     Thanks for this.It helps in Build Integration a lot.


    Any plans to support this in SQL Server 2008 in VS 2010 RTM?


    Also I observed one thing.When you deployed dacpac file to SSMS it took a default .mdf and .ldf .

    How does it handle the scenario when i shipped code with partitions/filegroups/files(typical large scale db)

  • User profile image



    First thanks for this video. I just have a question concerning the update of an existing application. If I understood the process, when you deploy the new version the process is :

    1. Create a new database using the schema

    2. Copy all data from previous db to the new one

    3. Switch databases.


    Is this still the case in the final release of studio? If yes, doesn't this disqualify it in case of database with a large amount of data?



  • User profile image

    Agree with Phertzog. Most of what you descibe can be done with scripting. What about upgrade paths of existing database projects? First time deployment is always easy. Talk more about difficult use cases (existing DB with tons of data).

Add Your 2 Cents