1 / 8

Exploring DAC and DACPAC: Key Features and Considerations

Dive into the world of Utility Control Point, Data Tier Applications, and DACPACs with insights on deployment, limitations, and monitoring capabilities. Learn how DACPAC is transforming database management for .NET developers.

aria
Download Presentation

Exploring DAC and DACPAC: Key Features and Considerations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Exploring the DAC and everyone’s favorite feature the DACPAC Denny Cherry Manager of Information Systems mrdenny@mrdenny.com twitter.com/mrdenny MVP, MCSA, MCDBA, MCTS, MCITP

  2. Agenda • Utility Control Point • Data Tier Applications • DACPACs

  3. Utility Control Point • Databases are mapped to Applications • Monitors CPU, IO load per Application • Monitors CPI, IO per Instance • Monitors CPU, IO per Server • Enterprise Edition can manage 25 instances • Data Center can manage 200+ instances • (License says unlimited) • Data Center is only available in a CPU license

  4. Data Tier Application • Allows for .NET developer to create and manage schema within Visual Studio 2010 • Can be packaged as a DACPAC for easy deployment to SQL Azure or native SQL Server Instance • Doesn’t support Security, Service Broker, Synonyms, SQL Logins, etc • (Basically if Azure supports it, it is supported by DAC) • Foreign Key Constrints have to be done by hand

  5. Data Tier Applications • Used to define a database as an application • Creates Schema Version which can match Application Version

  6. DACPAC • Deployment method requires double hard drive space, downtime, Consistency problems. • A single schema change requires a full redeployment • A single comment change requires a full redeployment • Currently only can be deployed to SQL 2008 R2 • SQL 2008 R1, SQL 2005 coming soon • Breaks Log Shipping, Mirroring, Log backups • All objects are placed within an XML document for parsing

  7. DACPAC – My Conclusions • Usable only for the smallest of applications. • Definitely not ready for Tier 1 Applications • Full Backups must be taken after each release to maintain some sort of backup restore capabilities.

  8. Denny Cherry Please fill out the survey at http://speakerrate.com/mrdenny. mrdenny@mrdenny.com http://itke.techtarget.com/sql-server Contact Info Blog Twitter

More Related