1. Deploying Data Tier Applications with VS 2010 and SQL Server 2008 R2 Joe D’Antoni SQL Saturday Philadelphia 05 March 2011

3. Primarily in health care

4. Vice President of the Philadelphia SQL Server User Group

5. I like to talk about and use new technologies

6. @jdanton on Twitter

7. Blog—joedantoni.wordpress.comAbout Me

8. My favorite moment…

9. Data Tier Applications Requirements The Good, the Bad and the Ugly Demos Overview

11. DBAs and Developers

12. How Did We Get Here?

14. Allows developers to own the database schema and definitions

15. Still needs work (more to come)

16. Microsoft seems to have invested deeply to build this, so it will get better (hopefully)

17. Interacts with SQL Azure—this is one method of deploying application code thereData Tier Applications

18. “A data-tier application (DAC) is an entity that contains all of the database and instance objects used by an application. A DAC provides a single unit for authoring, deploying, and managing the data-tier objects instead of having to manage them separately. A DAC allows tighter integration of data-tier development with the development of the associated application code. It also gives administrators an application level view of resource usage in their systems.“ Definition (Books Online)

19. Visual Studio 2010 SQL Server 2008 R2 Enterprise (for deployments—Data Tier Applications can be created from versions of SQL back to 2000) or SQL Azure Requirements

20. Model for Development Data-Tier Application Project (Departmental apps in V1) Database Project (Mission or business critical) Visual Studio Visual Studio Build Build .sql Generate scripts Deploy .dacpac .dbschema SQL Server 2008 R2 Deploy

21. Architecture

22. Target DBs for DAC V1 Number of Apps CRM ERP App Sophistication

23. What’s in a DACPAC File

24. Sounds pretty cool right?

25. We’re going to be here for a while. Extended Stored Procedures XML Schema Collections XML Indexes SQL Server Passwords CLR Objects SQL Server Service Broker Limitations (The Bad)

26. Filestream columns Symmetric keys, asymmetric keys, certificates DDL triggers Application roles Full-text catalog objects Encrypted objects (for example, encrypted stored procedures, views, functions, and triggers) Objects containing cross-database dependencies and linked server references Extended properties Synonyms Limitations (continued)

27. Problems?

28. The upgrade process Generates new database with a temporary name Generates all of the objects in the new database Moves all data from the V 1.0 database to V 1.1 database Requires data file space full size of database twice. Also requires transaction log space for the largest table in the database Not all databases can be converted into DACPACs Pubs and Northwind do not work Problems (The Ugly)

29. Required for SQL Azure Better SQL code management If you are developing fairly simple applications—this can be a great utility. Example—My shop does a good bit of in house web development, with small SQL Server databases, most are compatible. Speculation in that version two of DACPAC will work with older versions of SQL Server and be more feature rich. Why Use Data Tier Applications

30. MSDB [dbo].[sp_sysdac_rename_database] [dbo].[sp_sysdac_setreadonly_database] [dbo].[sp_sysdac_update_history_entry] Recovery model is pulled from Model on target instance Internals

31. Extracting a Data Tier Application from an Existing Database Creating a new data tier application project in Visual Studio Deploying a data tier application project to SQL Server Upgrading a data tier application Demos

32. MS White Paper http://msdn.microsoft.com/en-us/library/ff381683%28SQL.100%29.aspx References

33. Questions

34. Data Tier Applications can make database code deployments more consistent Currently this feature has a lot of limitations Overall, it’s worth learning and will get better in time. Summary

35. @jdanton on Twitter Joedantoni.wordpress.com Contact Info