Migration to SQL 2008 in a Mission Critical Environment<br />
<ul><li>Agenda
About 888
Upgrade Methodology
Upgrade Tools
Upgrade Process
Demo – Real-Time Migration</li></li></ul><li><ul><li>Agenda
About 888
Upgrade Methodology
Upgrade Tools
Upgrade Process
Demo – Real-Time Migration</li></li></ul><li>About 888<br /><ul><li>888.com is a global online gaming company.
  Our purpose is to provide quality entertainment for people who enjoy gambling.
  Giving them the opportunity to do so in a safe, fun, fair, regulated and secure environment. </li></li></ul><li>Our prod...
888 Database Environment<br />
R&R Of DB Infrastructure Team<br /><ul><li>Installations
Maintenance
Backups
Indexes
Statistics
Data retention
Monitoring
Performance Tuning
Version Uploads
Security</li></li></ul><li>SQL 2008 Project Summary<br /><ul><li>50 production  clustered instances were upgraded
300  development and QA instances were upgraded
All SQL server hosts upgraded windows 2008 R2 OS
Cut licensing costs by more than $500,000
Reduce load from IO subsystems by using SQL server compression
Minimal interference to the operation</li></li></ul><li>DB Infrastructure Team<br />
<ul><li>Agenda
About 888
Upgrade Methodology
Upgrade Tools
Upgrade Process
Demo – Real-Time Migration</li></li></ul><li>In Place Upgrade<br />Advantages<br /><ul><li>Simple
No connection string changes
No need to copy system objects – system DBs are upgraded
No need to copy the user databases</li></ul>Disadvantages<br /><ul><li>No control over the process
A standby server is mandatory for a quick rollback</li></li></ul><li>Side by Side Upgrade<br />Advantages<br /><ul><li>Ful...
A quick rollback
OS upgrade can be included</li></ul>Disadvantages<br /><ul><li>The necessity of copying the system objects
Connection string changes pose an overhead</li></li></ul><li>In Side Upgrade<br />
Copy System Objects<br /><ul><li>Linked servers
Jobs
Configurations
Logins and Credentials
Upcoming SlideShare
Loading in …5
×

Upgrade to 2008_d_binfra ver12

860 views
821 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
860
On SlideShare
0
From Embeds
0
Number of Embeds
190
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Upgrade to 2008_d_binfra ver12

  1. 1. Migration to SQL 2008 in a Mission Critical Environment<br />
  2. 2. <ul><li>Agenda
  3. 3. About 888
  4. 4. Upgrade Methodology
  5. 5. Upgrade Tools
  6. 6. Upgrade Process
  7. 7. Demo – Real-Time Migration</li></li></ul><li><ul><li>Agenda
  8. 8. About 888
  9. 9. Upgrade Methodology
  10. 10. Upgrade Tools
  11. 11. Upgrade Process
  12. 12. Demo – Real-Time Migration</li></li></ul><li>About 888<br /><ul><li>888.com is a global online gaming company.
  13. 13. Our purpose is to provide quality entertainment for people who enjoy gambling.
  14. 14. Giving them the opportunity to do so in a safe, fun, fair, regulated and secure environment. </li></li></ul><li>Our products<br />
  15. 15. 888 Database Environment<br />
  16. 16. R&R Of DB Infrastructure Team<br /><ul><li>Installations
  17. 17. Maintenance
  18. 18. Backups
  19. 19. Indexes
  20. 20. Statistics
  21. 21. Data retention
  22. 22. Monitoring
  23. 23. Performance Tuning
  24. 24. Version Uploads
  25. 25. Security</li></li></ul><li>SQL 2008 Project Summary<br /><ul><li>50 production clustered instances were upgraded
  26. 26. 300 development and QA instances were upgraded
  27. 27. All SQL server hosts upgraded windows 2008 R2 OS
  28. 28. Cut licensing costs by more than $500,000
  29. 29. Reduce load from IO subsystems by using SQL server compression
  30. 30. Minimal interference to the operation</li></li></ul><li>DB Infrastructure Team<br />
  31. 31. <ul><li>Agenda
  32. 32. About 888
  33. 33. Upgrade Methodology
  34. 34. Upgrade Tools
  35. 35. Upgrade Process
  36. 36. Demo – Real-Time Migration</li></li></ul><li>In Place Upgrade<br />Advantages<br /><ul><li>Simple
  37. 37. No connection string changes
  38. 38. No need to copy system objects – system DBs are upgraded
  39. 39. No need to copy the user databases</li></ul>Disadvantages<br /><ul><li>No control over the process
  40. 40. A standby server is mandatory for a quick rollback</li></li></ul><li>Side by Side Upgrade<br />Advantages<br /><ul><li>Full control over the process
  41. 41. A quick rollback
  42. 42. OS upgrade can be included</li></ul>Disadvantages<br /><ul><li>The necessity of copying the system objects
  43. 43. Connection string changes pose an overhead</li></li></ul><li>In Side Upgrade<br />
  44. 44. Copy System Objects<br /><ul><li>Linked servers
  45. 45. Jobs
  46. 46. Configurations
  47. 47. Logins and Credentials
  48. 48. Server master key</li></ul>By The Book: <br /><ul><li>Generate Export/Import Scripts</li></ul>Q: Can I copy system databases across different versions?<br />
  49. 49. Copy system databases across different versions of SQL servers<br />System DBs<br />System DBs<br />
  50. 50. Connection String Change<br />By the book: <br /><ul><li>Stop application
  51. 51. Change connection strings
  52. 52. Start application </li></ul>𝑋 (𝑁𝑢𝑚 𝑜𝑓 𝐴𝑝𝑝𝑠) 𝑋 (𝑁𝑢𝑚 𝑂𝑓 𝐼𝑛𝑠𝑡𝑎𝑛𝑐𝑒𝑠)<br /> <br />
  53. 53. Downtime Timeline<br />Downtime ends<br />Downtime starts<br />Conn stringchanges<br />DBs RW2008<br />DBsRO2000/2005<br />Backup log<br />Stop allapps<br />Start all apps<br />Restore log<br />Q: Can we do it in one step and faster?<br />
  54. 54. Server Identification<br /><ul><li>Hostname / Virtual-name
  55. 55. IP
  56. 56. Port
  57. 57. Service Name
  58. 58. Connection Examples:
  59. 59. hostnameINST1
  60. 60. Virtual-nameINST1 (in clusters)
  61. 61. Virtual-name, port
  62. 62. IP, port</li></ul> Q: What can I change?<br />
  63. 63. Change the SERVER Identification<br />2005<br /><ul><li>REAL-APR-SQLAPR
  64. 64. 10.10.10.193
  65. 65. Port 1433</li></ul>2008<br /><ul><li>REAL-APR-SQL2APR
  66. 66. 10.10.10.198
  67. 67. Port 1433</li></li></ul><li>Downtime Timeline<br />Downtime ends<br />Downtime starts<br />Conn stringchanges<br />DBs RW2008<br />DBsRO2000/2005<br />Backup log<br />Stop allapps<br />Start all apps<br />Restore log<br />
  68. 68. Copy User Databases<br /><ul><li>Storage Level
  69. 69. Move LUNs
  70. 70. Clone LUNs
  71. 71. Database Level
  72. 72. Database Mirroring
  73. 73. Log shipping </li></ul>- Works at the database level<br />
  74. 74. <ul><li>Agenda
  75. 75. About 888
  76. 76. Upgrade Methodology
  77. 77. Upgrade Tools
  78. 78. Upgrade Process
  79. 79. Demo – Real-Time Migration</li></li></ul><li>Installation Challenge #1<br />Number of installations<br />SQL 2008 Basic Installation<br />SP1<br />CU6<br />
  80. 80. Slipstream<br />Means to integrate packages of updates, patches or service-packs into one installation pack.<br />Robocopy<br />
  81. 81. Slipstream Advantages<br /><ul><li>66% less installations
  82. 82. Less restarts & less failovers
  83. 83. Saves time</li></li></ul><li>Installation Challenge #1<br />Number of installations<br />SQL 2008 SP1<br />CU6<br />SQL 2008 Basic Installation<br />SP1<br />CU6<br />
  84. 84. Installation Challenge #2<br />Installation Duration<br />SQL 2008 <br />Full Installation<br />
  85. 85. Silent Installation<br />Installation that does not display messages or windows during its progress<br />
  86. 86. Silent Installation Advantages<br /><ul><li>Easy to use – less parameters than GUI
  87. 87. Saves time
  88. 88. Install many instances with one script
  89. 89. Coherence and uniformity in all environments</li></li></ul><li>Silent Installation<br />
  90. 90. Installation Challenge #2<br />Installation Duration<br />SQL 2008 SP1<br />CU6<br />SQL 2008 SP1<br />CU6<br />
  91. 91. Copy User Databases<br />Microsoft Log Shipping<br />Works at the database level<br />888 AutoRestore<br />Works at the instance level<br />
  92. 92. In-House Tool – Autorestore<br />
  93. 93. Auto Restore Implementation  <br /><ul><li>An in-house tool that facilitates the control and management of restores from a central location
  94. 94. Uses transaction log backups from the source servers
  95. 95. Supports parallel restore operations
  96. 96. Works on an instance level (several databases) and not on a per-database basis (Mirroring)</li></li></ul><li><ul><li>Agenda
  97. 97. About 888
  98. 98. Upgrade Methodology
  99. 99. Upgrade Tools
  100. 100. Upgrade Process
  101. 101. Demo – Real-Time Migration</li></li></ul><li>Pre-Migration <br />Preparation Stage<br /><ul><li> Run Windows cluster validation
  102. 102. Install a new instance on a new cluster
  103. 103. Perform a failover
  104. 104. Network – check open ports
  105. 105. Open UDP 1434 or create aliases</li></li></ul><li>Pre-Migration<br />Preparation Stage<br /> Restore server objects by restoring the system databases<br />Windows 2008<br />Windows 2003<br />Restore <br />Upgrade<br />Restore <br />Instance 2005<br />Instance2008<br />Instance<br />20002005<br />Instance<br />2008<br />
  106. 106. Pre-Migration<br />Preparation Stage<br /> Copy user databases using instance level log shipping (Auto-Restore)<br />Windows 2003<br />Windows 2008<br />Auto-Restore<br />Instance<br />20002005<br />Instance<br />2008<br />
  107. 107. Pre-Migration<br />Simulation Stage <br /><ul><li> Application sanity checks
  108. 108. System health checks – OS ,Storage, Host, Network
  109. 109. Migration Process (scripts, time)
  110. 110. Compression Preparations</li></li></ul><li>Migration Day<br /> On 2000/2005 Instance<br /> Stop SQL server agent <br />2. Set all databases to read-only<br />Run last log backup for all databases <br />
  111. 111. Actual Migration<br />On 2008 Instance<br />4. Restore last logs with no recovery<br />5. Check if all the logs were restored from the old server<br />6. Restore with recovery for all databases<br />7. Set all databases to read-write<br />8. Fix orphan logins<br />9. Change compatibility to 100<br />
  112. 112. Actual Migration<br />Changing Instance Identification <br />10. Take offline the old instance group <br />Take offline the new instance group<br /> Delete the old and the new virtual IP and name DNS records from the DNS server<br />
  113. 113. Actual Migration<br />Changing Instance Identification <br /> Clear the DNS server’s cache<br />Give the new server the old server’s virtual IP & <br /> name<br />15. Flush DNS cache clients of new server, Arpcache <br />16. Start the new instance group<br />
  114. 114. Post-Migration<br /> Perform Sanity Checks<br /> Check NOC Alerts<br />3. Check SSIS, MSDTC and Job statuses<br />4. Run a Profiler’s Error Trace<br />5. Check  SQL Error Log & Event Log<br />6. Check Performance Baseline<br />7. Run Full Backups<br />
  115. 115. Compression <br /><ul><li> Compression Advisory – in-house utility
  116. 116. Compression Scripts</li></li></ul><li><ul><li>Agenda
  117. 117. About 888
  118. 118. Upgrade Methodology
  119. 119. Upgrade Tools
  120. 120. Upgrade Process
  121. 121. Demo – Real-Time Migration</li></li></ul><li>

×