Data Tier Applications Presentation SQL Saturday DC and NYC.

1. Deploying Data Tier Applications with VS 2010 and SQL Server 2008 R2 Joe D’Antoni PSSUG 08 December 2010

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 TwitterAbout Me

7. My favorite moment…

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

10. DBAs and Developers

11. How Did We Get Here?

13. Allows developers to own the database schema and definitions

14. Still needs work (more to come)

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

16. Interacts with SQL Azure—way to deploy applications thereData Tier Applications

17. “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)

18. 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

19. 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

20. Architecture

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

22. What’s in a DACPAC File

23. Sounds pretty cool right?

24. 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)

25. 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)

26. Problems?

27. 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)

28. 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

29. 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

30. Building and Deploying Data Tier Application Demos

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

32. Questions

33. 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

34. @jdanton on Twitter jdanton1@yahoo.com Contact Info