Access your Pro+ Content below.
Pros and cons of the DACPAC with SQL Server 2008 R2
This article is part of the SQL Server Insider issue of August 2010, Vol. 3
Microsoft has combined SQL Server 2008 R2 and Visual Studio 2010 to give us a new feature called data-tier applications, or DACs. Deployment of DACs from Visual Studio into SQL Server is done through a data-tier application package, also known as a DACPAC. The good DACPACs are great for small shops that are deploying minor application changes to SQL Server. It allows the code to be kept within the existing source control and gives developers an easy way to edit SQL Server objects from within the already familiar Visual Studio environment. This means that developers can work against their development database for all their coding, and then package up all the changes into a single DACPAC for release to production. The DACPAC can also be handed off to a DBA for release into a production or quality assurance (QA) environment. The DACPAC handles versioning of the database through data-tier editing, providing the developer with an easy way to use the database editing system. The .NET developer has the ability to edit the tables, ...
Features in this issue
PowerPivot, SQL Azure and ‘Dallas’ combine to create BI applications in the cloud. Is that integration seamless and is it even for you?
Data-tier applications are among SQL Server 2008 R2’s most talked-about new features, though version-one limitations could minimize their impact in the short term.
SQL Azure offers full-blown SQL Server functionality in the cloud and could ease management and development. But whether it’s ready to fully replace SQL Server remains to be seen.