1. Redmond Protocols Plugfest 2016 Joe Yong Hybrid cloud solutions with Stretch Database Sr. Program Manager joeyong@Microsoft.com

2. Lightning poll Thinking of you own or your customers’ largest OLTP or ODS databases, how many rows are in the largest tables? What percentage is cold data? Of your customers that have databases with very large tables: What is their maintenance (e.g. re-index, performance tuning) experience? What is their experience in meeting HA/DR and performance SLAs for the business? What are the most common causes of these performance and/or availability complaints? How much time do your support/services teams spend on solving platform issues vs. application issues?

3. Actual customer responses we’ve collected 45 billion rows in a single table (99% cold) 54 billion rows in a single table (~80% cold) 1.3 trillion rows in a partitioned table (>80% cold) 8TB of data in a single table ~5PB total (multiple DBs), 80% cold, incoming rate ~5TB /month aggregate data (0.5-1PB raw) Re-index? That’s not funny, man I can’t even update statistics We are down for about one day if we need to do a full database restore although about 70-80% of the data is cold No backup, no DBCC CHECKDB in 1.5 years Tune I/O, schema, statistics, contention, memory, RBAR queries…

4. Ever-growing databases Massive tables (hundreds of millions/billions of rows, TBs size) Users want/need to retain data indefinitely Closed business (cold) data accessed infrequently but must be online Maintenance challenges (e.g. re- index) Business SLAs at risk (e.g. restore time) Why Stretch Database? Existing solutions Keep adding storage and datacenter capacity Does not solve maintenance and SLA issues (unless you put cold data in SSDs) Move data to another location – database, flat-files, backups, tapes Data is near-line or offline Delete older data Unknown if data is valuable Unacceptable or illegal in some organizations/industries

5. Stretch SQL Server into Azure Stretch Database Order history NameSSN Date Steve Karimicm61ba906fd2/28/2005 Mike Wanox7ff654ae6d3/18/2005 Sapna Matuszyki2y36cg776rg4/10/2005 SQL Mojoenx290pldo90l4/27/2005 Blazej Zwillingypo85ba616rj5/12/2005 Cheng Jeswanibns51ra806fd5/22/2005 Nikhat Lindellmci12hh906fj6/07/2005 Whitney Langutb76b916gi6/18/2014 Lorenzo Oldspx61hi9306fj7/1/2014 Sophie Cookol43bi506gd7/12/2014 Aida Durhamtx83hal916fi7/29/2014 Jaclyn Wadenb95re926gi8/10/2014 Adrienne Battlevc61ira536fe8/23/2014 Order history NameSSN Date Steve Karimicm61ba906fd2/28/2005 Mike Wanox7ff654ae6d3/18/2005 Sapna Matuszyki2y36cg776rg4/10/2005 SQL Mojoenx290pldo90l4/27/2005 Customer data Product data Order History Stretch to cloud App Query Microsoft Azure Mike Wanox7ff654ae6d3/18/2005

6. Why should a non-DBA care about Stretch Database? Focus on application value, not platform issues Applications do not suffer availability, performance, or maintenance issues with 1MB or 1TB tables Enable new scenarios; retain data indefinitely at minimal effort and cost Avoid complexities of partitioned tables, read-only filegroups, etc… Provide a RAM to cloud solution (even if you’re a storage solutions vendor) Make your support/services colleagues happy

7. Does StretchDB play nice with non-MSFT apps? All public interfaces, no private features, APIs, etc… Available in all editions of SQL Server Globally available Can be implemented and managed by Cloud Solution Providers

8. Data in motion always via secure channels (default TLS 1.2) Supports Always Encrypted Encryption key remains on- premises with your application Row Level Security SQL Server and SQL Azure audit just works Secure by default (and then some)

9. On-premises SQL Server instance On-premises application(s) DB in SAN/Local Storage Ord_Detail Storage Ord_detail_ archive table Trickle data migration Ord_detail_ archive table Txn_detail Txn_detail (cold rows only) Hot + cold rows in same table Compute Entire archive table moved Only cold rows moved Azure SQL Stretch Database SQL Server Trickle data movement

10. Smart query processing On-premises SQL Server instance On-premises application(s) DB in SAN/Local Storage Ord_Detail Storage Ord_detail_ archive table Txn_detail Txn_detail (cold rows only) Transparent remote data access Hot + cold rows in same table Compute Local data only queries Local + remote data queries Trickle data migration Azure SQL Stretch Database SQL Server

11. Supports existing SQL Server HA/DR solutions (including Always On AG with Readable Secondary), except DB mirroring – deprecated for SQL Server Replication – not supported for Stretch Database in general DBAs backup/restore local SQL Server hot data only Stretch Database ensures remote data is transactionally consistent with local Upon completion of local restore, SQL Server reconciles with remote using metadata High availability and disaster recovery Backup/restore

12. Current limitations and non-use cases Limitations Certain data types, replication, computed columns, etc… Table with primary key in a PK/FK relationship – cannot stretch parent tables, child tables ok Cross database constraints not supported Detailed list at https://msdn.microsoft.com/en-us/library/mt605114.aspxhttps://msdn.microsoft.com/en-us/library/mt605114.aspx Non-use cases Not for frequently accessed data (hot) Can connect directly to Azure SQL Stretch database but not recommended Does not alleviate performance/scale issues for application that have inefficient design/queries Can amplify existing performance issues

13. Stretch Database takeaways Transparent to most applications; benefits are automatic Alleviates issues with business SLA, performance, administration and TCO if you have very large tables containing cold data Secure by default with optional advanced security features Supports existing HA/DR solutions and requirements, may have significant restore time reduction for some scenarios Performance will be at reasonable levels for cold data scenarios; not intended for active OLTP data SQL Server 2016 targets customers with large amounts of cold data

14. Next steps Try stretching your app – Azure provides free trial accounts Certify your application for Stretch Database In most cases, you just need to stretch a known large table then run your tests Engage customers that have very large tables with cold data Technical assistance available Business incentives may be available for some Review current applications for new capabilities leveraging Stretch Database, especially with temporal tables Stuck? Questions? We want to help! Contact us halligancustomers@microsoft.com

15. Resources SQL Server 2016 Stretch Database http://go.microsoft.com/fwlink/?LinkId=627389 Azure SQL Stretch Database service https://azure.microsoft.com/en-us/services/sql-server-stretch-database/ Pricing http://go.microsoft.com/fwlink/?LinkID=724357 Q&A forums Stackoverflow: http://stackoverflow.com/questions/tagged/sql-server-2016stackoverflow.com/questions/tagged/sql-server-2016 MSDN: http://go.microsoft.com/fwlink/?LinkId=627390http://go.microsoft.com/fwlink/?LinkId=627390

16. Redmond Protocols Plugfest 2016 Questions or Comments?