Download presentation
Presentation is loading. Please wait.
1
Upgrade Roadmap: Taking YOU to R2
Craig Purnell Baker & Hostetler LLP @CraigPurnell
2
About Me Career Database Professional 12 years in IT
9 years working with SQL Server Member of Ohio North SQL Server User Group and PASS 9th SQL Saturday this year
3
How I got here
5
Intended Audience Database Administrators Database Professionals
Technical Project Managers
6
Assumptions/Survey About 25% of you still running SQL 2000 in production Most of you are on SQL 2005 with some 2008 sprinkled in Many of you are running Standard with larger sites on EE (or clustered)
7
Goals Checklist of considerations
Review upgrade vs build out new migration Upgrade Advisor Deprecated / Removed features Enumerate Interfaces and “hooks” Framework for planning YOUR upgrade Real world lesson learned or example
8
Upgrade 200x Instance R2 Instance
9
Side by Side=Migration=Build out new
10
Side by Side 2000 2000 R2
11
Run don’t walk and get this guide.
12
Version History Version Internal RTM Date Current SP Status
SQL Server 2000 8.0 11/2000 SP4 Extended Support ends 4/9/2013 SQL Server 2005 9.0 11/7/2005 Extended Support ends 4/12/2016 SQL Server 2008 10.0 8/6/2008 SP2 Mainstream Support ends 1/14/2014 SQL Server 2008 R2 10.5 4/21/2010 SP1 SP1 is now out for R2
13
Upgrade Paths (simplified)
Data Center Enterprise Standard See the document : Version and Edition Upgrades (SQL Server 2008 R2) on MSDN for complete information Workgroup Web Express (MSDE) Developer Evaluation
14
Considerations Checklist
Upgrade vs. Migrate DTS Hardware Servers SAN vs. DAS High Availability 3rd Party ISV
15
Degree of Radical Change
Remember how big of a deal SQL 2005 was? CLR, DMV’s, etc. SQL 2008 is a polished version of 2005. R2 is a polished version of 2008. Evolutionary vs Revolutionary
16
Considerations Checklist
Interfaces and Reporting Data Warehousing 3rd Party Backup Utilities Drive Layouts (mount points, anyone?)
17
Great Time to Rethink SKU How applications connect (Cname, aliases)
Named instances The classic model (1 app = 1 SQL Server) Consolidation / virtualization Collation
18
The Upgrade Approach Use when on newer hardware Eg, SQL 2008 2008 R2
(maybe) SQL 2005 2008 R2 Hail Mary pass Replace an existing instance Rollback is usually difficult
19
In Place Upgrade on a cluster
Not for the faint of heart We did it (x3) back in ‘06 (2000 to 2005) Clustering changes in Windows Server 2008 R2 On 2000, IA-64 upgrades are not supported
20
Upgrade Pro/Con Pro Use when already on 64bit Quicker , one shot deal
Keep the same network name No reconfiguration of application DSN Interfaces stay the same Con No cross platform support (32 bit 64 bit) More hazardous Rollback difficult Impossible to fully test applications beforehand Carry forward legacy baggage
21
Coming from 2000? Likely going to be a migration
Say goodbye to Enterprise Manager and Query Analyzer 2000 Log shipping has no upgrade path MAPI SQL mail deprecated Maintenance Plans Fulltext catalogs
22
2000 32 bit considerations Can upgrade to R2 using WOW64 on 64bit
This will be a 32bit instance on 64bit OS Not supported: upgrading clustered WOW64 instances of 2000 and 2005
23
The DTS Package Problem
Upgrade? You can continue to run 2000 packages.* Use DTSBACKUP 2000 to move packages Install DTS Designer Components (05 Feature pack page) Long term: Package Migration Wizard or rewrite from scratch. DTS Xchange from Pragmatic Works for larger sites
24
Side by Side New hardware Existing hardware (< 2 yrs)
Default Instance / Named Instance considerations Scenario: SQL Server bit to R2 64bit
25
Side by Side Manually move databases Config settings Security settings
Copy Database wizard Backup/Restore Detach/Reattach Config settings Security settings Agent Jobs Logins
26
Side by Side Pro/Con Pro Con Manually move databases Config settings
Copy Database wizard Backup/Restore Detach/Reattach Config settings Security settings Agent Jobs Logins More manual labor Time consuming Move each app separately
27
Example: Baker Hostetler
Thomson Elite Enterprise 3.6 financial system Deployed to Eagan in 11/2010 on SQL 2005 Upgrading to /2011 Clustered SQL Server 2005 Enterprise x64 OS: Windows Server 2008 R2 Enterprise Dell R810 and MD3200 SAS
28
Meet the Upgrade Advisor
The upgrade advisor is your friend
29
Upgrade Advisor Get it at the R2 Feature Pack download page
30
Upgrade Advisor Analyze code / Database objects
Look for Deprecated features Trace Capture / *.sql files
31
Where does the code run? Using stored procedures for business logic
Upgrade Advisor – OK! Ad Hoc SQL or batches coming from middle tier servers Need to capture a trace
33
Upgrade Advisor Demo
34
Deprecated vs. Removed Deprecated Removed Still works in R2
“Don’t use this for new stuff” “Get rid of this” You might have to use 80 or 90 compat level Removed “Gone forever”
35
Test for Deprecated features
36
Database Compat Level Version DB Compat Internal Version 2000 80 539
2005 90 611/612(with vardecimal) 2008 100 655 2008 R2 661 R2 really is a minor upgrade Note that R2 does not have a 150 compat level. Very Odd.
37
Databases are NOT backward compatible between R2 and 2008
38
Interfaces and Applications
Reporting Data Sharing Enterprise Interfaces Linked Servers [DS_SAP_PROD]
39
Enumerate Usage Linked Server Usage Check SQL Agent Jobs
Login Sharing / Analyze Logins
40
Audit Logins in the Errorlog
42
Framework: Pre Upgrade Tasks
43
Pre Upgrade Tasks Create Service Accounts for Engine and Agent
Review documentation Release Notes Readme Books online section on upgrading Upgrade Advisor Help Build a Rollback plan Get familiar with setup log files
45
Pre Upgrade: Document Everything
Sp_configure SQLDIAG Drive layouts /Free space Capture performance baseline Linked servers Xprocs Logins (sp_help_revlogin)
46
Pre Upgrade: Agent Enable Windows authentication
Service account MUST be in Sysadmin group
47
Pre Upgrade Tasks Install prerequisites on server
.NET 3.5 SP1 Windows Installer 4.5 Powershell 2.0 Run full backups of all databases Test your restores Run DBCC checkdb at T - 1
48
Showstoppers and Hazards
Applications that require 65 or 70 compat Side by Side with SQL 7 (?) R2 not supported on Server 2008 “Core” DC installs supported but NOT recommended
49
Disk Space Must have 3.6 GB Available on the C: drive Feature
Disk Space Minimum Required Engine, Replication, Full Text Search 711MB Analysis Services 345MB Reporting Services and Report Manager 304MB Integration Services 591MB Client Components 1823MB SQL Server 2008 R2 Books Online 157MB Need 3.6 GB to do the setup / install process (this is temp) Must have 3.6 GB Available on the C: drive
50
In Place Upgrade Install Prereq (.NET 3.5 SP1, SNAC, WI 4.5) SQL
Check for upgrade blocking issues SQL Install R2 binaries SQL Stop Legacy Instance SQL Update select component data and objects (system db’s , resource db) SQL Start New Instance SQL Setup remove legacy binaries (All) and tools (2K) SQL
51
Framework: Post Upgrade Tasks
52
Post Upgrade Tasks Apply SP1 and the latest Cumulative Update
Run another Full backup DBCC Checkdb with Data_Purity Rebuild Indexes Upgrade your skills Watch the Error Log closely
53
Post Upgrade Tasks Modify your backup jobs to use CHECKSUM *
Turn on Backup compression Analyze TempDB usage Change database compatibility level Means coming from 2000 only You can run a database in a lower compat level on R2
54
Post Migration Upgrade Tasks
Coming from 2000? SQL Mail Database Mail Sp_OA* CLR Sp_OA* means OLE automation create,manipulate (COM) objects CLR is better, native and more stable
55
Key Takeaways Upgrade/Migration is 75% planning 25% execution
Upgrade vs. Migration is locale specific Upgrade Advisor is pure awesomeness! The devil is in the details Interfaces Agent Jobs Etc Keep an eye on your applications
56
Thank You Please don’t forget to fill out an evaluation
Contact Information: @CraigPurnell
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.