Ad
More Related Content
What's hot (20)
Similar to SQL Server Upgrade and Consolidation - Methodology and Approach (20)
Ad
Recently uploaded (20)
Ad
SQL Server Upgrade and Consolidation - Methodology and Approach
- 4. Workshop Outline • Today’s Challenges • What Is Consolidation? • Consolidation Approach • The Benefits of Consolidation • Time to upgrade??? • Why Upgrade? • Upgrade Methodology • Upgrade & Consolidation Tools • Q&A
- 5. Today’s Challenges • Financial Resources • Major economic reset AKA a recession • Organizations are cutting costs in response • Managing Complicated Infrastructure • Too many servers, too few DBAs • Management tools not always effective • Unknown servers contribute to license issues • Keeping software current presents challenges • Security risks posed by non-homogenous environment
- 6. What Is Consolidation? Consolidated Server Database Server Database Server Database Server • Consolidation is the process of methodically decreasing the number of database servers to reduce the size and complexity of the data infrastructure.
- 7. What Is Consolidation? Consolidated Server Redundant Application Redundant Application Redundant Application • Consolidation can also include reducing the number of duplicate applications.
- 8. Consolidation Approach • Identification • Existing servers are identified and then classified by either internal or vendor application. • Classification • The process continues to break down and classify each database further using a set of criteria. • Organization • The conclusion of the process yields a set of databases that are organized into those that can be consolidated and those that cannot.
- 9. The Benefits of Consolidation • Reduced hardware costs by removing under-utilized server resources from production. • Avoid ever-increasing storage costs by leveraging compression and other features of SQL Server 2016 • Improved data security and auditing capabilities • Better manageability for the data infrastructure • Improved overall performance of existing database resources • Reduced equipment environmental requirements such as cooling and AC • Improved business efficiency through a better managed, more agile data infrastructure
- 10. …journey so far: SQL Server 2008 R2 to 2016 Support for ‘R’ Query StoreStretch Databases JSON Support Level Always Encrypted
- 11. Time to upgrade??? • How can you perform upgrade (pro-actively)? • What tools can help collect data for analysis? • What kind of upgrade strategy you would follow on various SQL instances? • How can you detect troubled instances/databases?
- 12. The List… • Why Upgrade? • Building plans & strategies… • Upgrade Route…. • Best Practices…… • Round-up
- 13. Why Upgrade? • End of mainstream support • SQL Server 2000 • SQL Server 2005 • SQL Server 2008 & R2 • SQL Server 2012 • Hardware upgrade • Consolidation • ….and
- 14. Mainstream and Extended support Version Mainstream Extended SQL Server 2000 SP4 08-04-2008 09-04-2013 SQL Server 2005 SP4 12-04-2011 12-04-2016 SQL Server 2008 SP4 08-04-2014 09-07-2019 SQL Server 2008 R2 SP3 08-07-2014 09-07-2019 SQL Server 2012 SP4 11-07-2017 12-07-2022 SQL Server 2014 SP2 09-07-2019 09-07-2024 SQL Server 2016 SP1 31-07-2021 14-07-2026 https://support.microsoft.com/en-us/lifecycle
- 15. Why Upgrade? • New features • AlwaysOn Availability Groups • Windows Server Core Support • Columnstore Indexes • User-Defined Server Roles • Enhanced Auditing Features • BI Semantic Model • Sequence Objects • Enhanced PowerShell Support • Distributed Replay • PowerView • SQL Azure Enhancements • Big Data Support •Improved In-memory engine •Enhanced Windows 2012 Integration •Enhanced AlwaysOn Availability groups •Backup Enhancements •Updatable Columnstore Indexes •SSDT for BI •Power BI for Office 365 integration •Always Encrypted •Stretch Database •Real-time Operational Analytics •PolyBase into SQL Server •Native JSON support •Always-On enhancements •Enhanced In-memory OLTP •Revamped SSDT 2012 2014 2016
- 17. Planning • Preparing to Upgrade • Review upgrade documentation and resources • Document your resources and environment • Identify upgrade requirements • Decide on upgrade strategy • Upgrade High-Availability servers • Establish backup and rollback plans • Test the plan!!!
- 18. Pre-Upgrade • Check environment • Run Data Migration Assistant (2012, 2014, 2016 & Azure SQL) • Ensure environment is clean • Check database consistency • Consider shrink Data file (read-only DB) and log files • Rebuild indexes • Run SQL Server Best Practices Analyzer (BPA) • Back up your environment • System and user databases including DTS/SSIS packages • …what else • Documentation
- 19. Prepare to Post-upgrade • The Upgrade • Document every step • System health checks • Perform the upgrade - strategy • Environment backup (pre to post) • Go/No-go (Checkpoint) • Review the logs • Troubleshoot - upgrade failure • Test functionality and performance. • Determine application acceptance
- 20. Upgrade Strategy • Side-by-Side • In-Place
- 21. Side-by-Side (Migration) Upgrade • Install new instance of SQL Server without affecting existing instance • Can be same or different server • Database objects are manually copied to new instance • Copy Database Wizard/Detach -> Copy -> Attach/Backup -> Restore Pros & Cons.
- 22. In-Place Upgrade • Upgrades an existing installation • Instance name remains the same after upgrade • Old instance no longer exists • User data and configuration is preserved • Mostly automated process through SQL Server Setup • Performed on same machine as existing installation Pros & Cons.
- 23. Upgrade & Consolidation Tools • MAP (Microsoft Assessment and Planning) Toolkit for SQL Server • https://www.microsoft.com/en-us/download/details.aspx?id=7826 • DMA (Data Migration Assistant) • https://www.microsoft.com/en-us/download/details.aspx?id=53595 • Best Practices Analyzer for SQL Server • https://www.microsoft.com/en-in/download/details.aspx?id=29302 • SQL Server 2016 Setup: System Configuration Checker • Custom scripts
- 24. Upgrade & Consolidation Tools (MAP & BPA)
- 25. Upgrade & Consolidation Tools (DMA)
Editor's Notes
- #5: Upgrade strategies - planning, options, methodology and tools Upgrade scenarios – Clustering, Mirroring and so on Lessons learned and recommended practices
- #10: Consolidation results in lower operating costs and a greater return on infrastructure investment.
- #14: If you are comfortable with current solution – stay with it AlwaysOn – use secondaries for reporting, backups, loading datawarehouse and other activities