1. Migration to SQL 2008 in a Mission Critical Environment

3. About 888

4. Upgrade Methodology

5. Upgrade Tools

6. Upgrade Process

8. About 888

9. Upgrade Methodology

10. Upgrade Tools

11. Upgrade Process

13. Our purpose is to provide quality entertainment for people who enjoy gambling.

15. 888 Database Environment

17. Maintenance

18. Backups

19. Indexes

20. Statistics

21. Data retention

22. Monitoring

23. Performance Tuning

24. Version Uploads

26. 300 development and QA instances were upgraded

27. All SQL server hosts upgraded windows 2008 R2 OS

28. Cut licensing costs by more than $500,000

29. Reduce load from IO subsystems by using SQL server compression

32. About 888

33. Upgrade Methodology

34. Upgrade Tools

35. Upgrade Process

37. No connection string changes

38. No need to copy system objects – system DBs are upgraded

41. A quick rollback

45. Jobs

46. Configurations

47. Logins and Credentials

49. Copy system databases across different versions of SQL servers System DBs System DBs

51. Change connection strings

52. Start application 𝑋 (𝑁𝑢𝑚 𝑜𝑓 𝐴𝑝𝑝𝑠) 𝑋 (𝑁𝑢𝑚 𝑂𝑓 𝐼𝑛𝑠𝑡𝑎𝑛𝑐𝑒𝑠)

53. Downtime Timeline Downtime ends Downtime starts Conn stringchanges DBs RW2008 DBsRO2000/2005 Backup log Stop allapps Start all apps Restore log Q: Can we do it in one step and faster?

55. IP

56. Port

57. Service Name

58. Connection Examples:

59. hostnameNST1

60. Virtual-nameNST1 (in clusters)

61. Virtual-name, port

62. IP, port Q: What can I change?

64. 10.10.10.193

66. 10.10.10.198

69. Move LUNs

70. Clone LUNs

71. Database Level

72. Database Mirroring

73. Log shipping - Works at the database level

75. About 888

76. Upgrade Methodology

77. Upgrade Tools

78. Upgrade Process

80. Slipstream Means to integrate packages of updates, patches or service-packs into one installation pack. Robocopy

82. Less restarts & less failovers

84. Installation Challenge #2 Installation Duration SQL 2008 Full Installation

85. Silent Installation Installation that does not display messages or windows during its progress

87. Saves time

88. Install many instances with one script

90. Installation Challenge #2 Installation Duration SQL 2008 SP1 CU6 SQL 2008 SP1 CU6

91. Copy User Databases Microsoft Log Shipping Works at the database level 888 AutoRestore Works at the instance level

92. In-House Tool – Autorestore

94. Uses transaction log backups from the source servers

95. Supports parallel restore operations

97. About 888

98. Upgrade Methodology

99. Upgrade Tools

100. Upgrade Process

102. Install a new instance on a new cluster

103. Perform a failover

104. Network – check open ports

106. Pre-Migration Preparation Stage Copy user databases using instance level log shipping (Auto-Restore) Windows 2003 Windows 2008 Auto-Restore Instance 2000005 Instance 2008

108. System health checks – OS ,Storage, Host, Network

109. Migration Process (scripts, time)

111. Actual Migration On 2008 Instance 4. Restore last logs with no recovery 5. Check if all the logs were restored from the old server 6. Restore with recovery for all databases 7. Set all databases to read-write 8. Fix orphan logins 9. Change compatibility to 100

112. Actual Migration Changing Instance Identification 10. Take offline the old instance group Take offline the new instance group Delete the old and the new virtual IP and name DNS records from the DNS server

113. Actual Migration Changing Instance Identification Clear the DNS server’s cache Give the new server the old server’s virtual IP & name 15. Flush DNS cache clients of new server, Arpcache 16. Start the new instance group

114. Post-Migration Perform Sanity Checks Check NOC Alerts 3. Check SSIS, MSDTC and Job statuses 4. Run a Profiler’s Error Trace 5. Check SQL Error Log & Event Log 6. Check Performance Baseline 7. Run Full Backups

117. About 888

118. Upgrade Methodology

119. Upgrade Tools

120. Upgrade Process