Building Efficient Code with Data Tier Applications

A The intent behind creating data tier application was to enable data tier application developers to write efficient codes so that the gap between data base administrator and developers is reduced, and it mitigates chances of error.

This is important because if there is any mismatch between logic and data tables, then correcting this mismatch is quite error prone. There is also a need to centrally control data application. DAC is an entity that contains both database and instance objects. There is a single unit for authoring, deploying, and managing the data-tier objects which makes management of these components quite easy. If an application is built using the data tier approach, an administrator has a view of all resources used in the application that helps one to centrally control the data application. There are two ways to create DAC. The first method is to register the database as DAC with the host instance, while on the other hand, the second method results in DAC package file which can be deployed to other instance of SQL server or can be given to application developers. One point to keep in mind is that the DAC package file has no data. It is only a schema, which can therefore be easily transfered.

Click on the image to enlarge