2. Time SQL Server 2012 Highlights and ColumnStore Index09:00 – 10:15 AlwaysOn and Contained Databases10:45 – 12:15 PowerPivot and PowerView (BI)13:00 – 14:15 Applinaces and Reference Architectures, Azure IaaS14:45 – 16:00

6. EnterpriseBusiness IntelligenceStandard Target scenarios CPU Memory DB Size For Mission Critical & Applications Data Warehousing For Premium Self- Service and Corporate Business Intelligence Continues to offer basic database, reporting and analytics capabilities Operating System maximum Limited to lesser of 4 Sockets or 16 cores Operating System maximum 64 GB 524 PB

7. EnterpriseBusiness IntelligenceStandard Licensing Options Windows Server Core Edition Support Basic High Availability Basic OLTP Basic Reporting & Analytics Programmability & Developer Tools (T-SQL, CLR, data types, FileTable) Manageability (Management Studio, Policy-Based Management) Enterprise Data Mgmt. (Data Quality Services, Master Data Services) Self-service Business Intelligence (Power View, PowerPivot for SPS) Corporate Business Intelligence (Semantic model, advanced analytics) Advanced Security (Advanced auditing, Transparent Data Encryption) Data Warehousing (ColumnStore Index, compression, partitioning) AlwaysOn High Availability StreamInsight Core-Based Advanced Server + CAL Basic Core-Based or Server+CAL Basic

8. SQL VersionMainstream SupportExtended Support SQL Server 2000 SP4 08.04.200809.04.2013 SQL Server 2005 SP4 12.04.201112.04.2016 SQL Server 2008 14.01.201408.01.2019 SQL Server 2008 R2 14.01.201408.01.2019 Prepare and execute on your upgrade and/or sustained engineering plans as early as possible for these SQL versions. Remaining current on your SQL Server version ensures that your product remains supported per the Support Lifecycle policy. Additionally, your software benefits from the many enhancements, fixes, and security updates provided through the latest releases.

11. New Installation Install a new server and instances SIDE BY SIDE Install an instance next to the existing one INPLACE UPGRADE Replace an existing instance by one/one upgrade Less granular control over upgrade process Instance remains offline during part of upgrade Not best practice for all components Considerations for Rollback Strategy Easier, mostly automated, generally fast overall process System data upgraded May require no additional hardware Applications remain pointing to same server/DB More granular control over upgrade process at DB level Can be used to perform test migration Ability to run systems side-by-side for parallel runs Relatively straightforward rollback strategy Usually require additional hardware Server/database name changes Not practical for VLDB (Very large DB) unless utilizing SAN More granular control over upgrade process at DB level Can be used to perform test migration Ability to run systems side-by-side for parallel runs Goes frequently together with OS upgrade Goes frequently together with platform upgrade (x86->x64) Requires additional Hardware Server/Database name changes Not practical for VLDB unless utilizing SAN

12. SSRS Power View SharePoint Mode Data Alerts Report Server Projects in SQL Server Data Tools for Visual Studio 2010 Excel Renderer for Microsoft Excel 2007-2010 and Microsoft Excel 2003 Word Renderer for Microsoft Word 2007-2010 and Microsoft Word 2003 http://msdn.microsoft.com/e n-us/library/ms170438.aspx http://msdn.microsoft.com/e n-us/library/ms170438.aspx SSIS Deployment Management and Troubleshooting Development Enhancements Performance Data Quality Access to Samples and Tutorials http://msdn.microsoft. com/en- us/library/bb522534.a spx http://msdn.microsoft. com/en- us/library/bb522534.a spx