Last week I wrote an article for Creating DAC packages. Today I’m going to cover how to deploy a DAC package. It’s very easy  for the DBA’s to deploy the DAC in few clicks that means in few clicks database implementation will get completed, it’s as simple as like that. I’m going to use the DAC package which I created last week. To deploy a DAC package proceed the steps below

In previously article I’ve covered what is DAC package and how it helps during deployment. In this article I’m going we are going to see how can we create a new data tier application (DAC) package for deployment. All SQL Server related objects can be included in this package for deployment, this includes both database and server level objects. You can create DAC package through any of the following methods

This is one of the new feature released with SQL Server 2008 R2. I know it’s late to cover this topic. It has greater flexibility and easy of implementation for database perspective. I could say it’s a build which has all database & instance level objects for implementation, just run the build and get the database work done, just simple like that. I’m not sure why Microsoft chosen same acronym for Data tier applications as DAC is also know as Dedicated Administrator Connection, lets not dig into it, only Microsoft can answer!!

SQL Server 2005 provides a special diagnostic connection for administrators when standard connections to the server are not possible. This diagnostic connection allows an administrator to access SQL Server to execute diagnostic queries and troubleshoot problems even when SQL Server is not responding to standard connection requests.