SQL Server 2008 R2 for the DBA Patrick LeBlanc Objectives New Editions Multi-server management Datacenter Parallel Data Warehouse Utility Control Point Data Tier Applications Dacpac New SQL Server Editions Datacenter Built on SQL Server 2008 R2 Enterprise Application and Multi-Server management Manage over 25 instances Supports more than 8 processors and up 256 logical processors Supports memory limits up to OS maximum New SQL Server Editions Parallel Data Warehouse Massive Parallel Processing (MPP) 10s to 100s TB to 1+PB enabled Advanced DW Capabilities Star Join Queries Change Data Capture Integrates with SSIS, SSRS, and SSAS Supports Industry DW Hub and spoke architecture Multi-Server Management Utility Control Point Requirements Datacenter, Enterprise, Developer, or Evaluation Instance must be Database Must Operate within a single Windows domain, or across domains with two-way trusts Service accounts must have read permission to Users in AD. Multi-Server Management UCP Monitors Instances of SQL Server Data-tier applications Database files Storage Volumes Monitored Resources CPU utilization Storage space utilization Demo Data-tier Application Developers define & manage the logical structure of an application Define tables, views, etc. By means of a DAC “My apps” dashboard Sharepoint-like experience for data Utility auto-configures, installs & maintains the app storage Sets physical app properties (target instance, filegroups, DB config); Installs/maintains the app (e.g., autoindexing, resource allocation, DAC move) DBA / Admin manages the entire Utility from a single node What is a data-tier application? New unit of deployment for TSQL apps Core parts of the DAC An “MSI” for T-SQL apps DAC metadata App definition Deployment requirements Separation of concerns between app developer and DBA DAC DAC Metadata (Name, Version, …) Definition (Schema) Develop Tables, Views, Constraints, SProcs, UDFs, Users, Logins Deploy Indexes, Partitions FileGroups … DAC Deployment Profile Deployment Requirements, Management Policies, Failover Policies Rich set of services DAC packages Transportable file (.dacpac) Zip format Content Stores the DAC metadata, logical definition, deployment policies Can contain “extra” files Post deployment scripts Readme Scripts to handle data Created by Extracting a DAC from existing app DB Creating / building a new DAC in Visual Studio Contact Information pleblanc@pragmaticworks.com Twitter: @patrickdba Blog: http://www.bidn.com/blogs/PatrickLeBlanc Who am I? BI Architect for Pragmatic Works SQL Server MVP Decade of SQL Server Experience Founder SQL Lunch (www.sqllunch.com) Leader Baton Rouge, LA SQL Server User Group Twitter:@patrickdba Author: Knight’s Microsoft Business Intelligence 24-Hour Trainer Thank You !