Migrating To Sql Server 2005

2,146 views
2,064 views

Published on

Migrating To Sql Server 2005

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,146
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
74
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Migrating To Sql Server 2005

  1. 1. Migrating To SQL Server 2005 Just Like A Trip To The Beach Michael Townshend & Dennis Murphy DNREC
  2. 2. Step 1 – Assess Your Readiness <ul><li>Swim Suit Still Fit? </li></ul><ul><ul><li>Time to upgrade hardware? </li></ul></ul><ul><li>Sun Screen Out of Date? </li></ul><ul><ul><li>Inventory User Accounts, Databases & Delete Unneeded </li></ul></ul><ul><li>Make a To Do List </li></ul><ul><ul><li>Run SQL Server Upgrade Advisor </li></ul></ul>
  3. 3. Step 1 – Assess Your Readiness <ul><li>DNREC Hardware </li></ul><ul><ul><li>Pre-Upgrade </li></ul></ul><ul><ul><ul><li>2 quad Processor Servers in Active/Passive Configuration with 1 TB SAN </li></ul></ul></ul><ul><ul><li>Post Upgrade </li></ul></ul><ul><ul><ul><li>2 Dual Core Hyper-threaded 64 bit Quad Processor Servers in Active/Passive Configuration with 3 TB SAN </li></ul></ul></ul>
  4. 4. Make A Plan <ul><li>Pick Vehicle </li></ul><ul><li>Make Load Plan </li></ul><ul><li>Set Date </li></ul>
  5. 5. Pick A Vehicle <ul><li>Bicycle (Express) </li></ul><ul><ul><li>Max CPU: 1 Max RAM: 1GB </li></ul></ul><ul><ul><li>Max DB Size: 4GB </li></ul></ul><ul><ul><li>Failover Clustering: No </li></ul></ul><ul><ul><li>Report Server: No </li></ul></ul><ul><ul><li>Management Studio: No </li></ul></ul><ul><ul><li>SSIS: No </li></ul></ul><ul><ul><li>Free </li></ul></ul>
  6. 6. Pick A Vehicle <ul><li>Compact (Workgroup) </li></ul><ul><ul><li>Max CPU: 2 Max RAM: 3 GB </li></ul></ul><ul><ul><li>Max DB Size: No Limit </li></ul></ul><ul><ul><li>Failover Clustering: No </li></ul></ul><ul><ul><li>Report Server: No </li></ul></ul><ul><ul><li>Management Studio: Yes </li></ul></ul><ul><ul><li>SSIS: No </li></ul></ul><ul><ul><li>$ </li></ul></ul>
  7. 7. Pick A Vehicle <ul><li>Sedan (Standard) </li></ul><ul><ul><li>Max CPU: 4* Max RAM: No Limit </li></ul></ul><ul><ul><li>Max DB Size: No Limit </li></ul></ul><ul><ul><li>Failover Clustering: Yes </li></ul></ul><ul><ul><li>Report Server: Yes </li></ul></ul><ul><ul><li>Management Studio: Yes </li></ul></ul><ul><ul><li>SSIS: Yes (Simple Transforms) </li></ul></ul><ul><ul><li>$$ </li></ul></ul>
  8. 8. Pick A Vehicle <ul><li>Luxury Sedan (Enterprise) </li></ul><ul><ul><li>Max CPU: None Max RAM: No Limit </li></ul></ul><ul><ul><li>Max DB Size: No Limit </li></ul></ul><ul><ul><li>Failover Clustering: Yes </li></ul></ul><ul><ul><li>Report Server: Yes </li></ul></ul><ul><ul><li>Management Studio: Yes </li></ul></ul><ul><ul><li>SSIS: Yes (Advanced Transforms) </li></ul></ul><ul><ul><li>$$$$ </li></ul></ul>
  9. 9. Make Load Plan <ul><li>Coolers>Chairs>Towels </li></ul><ul><ul><li>Install SS 2005 on staging server with same name as new server </li></ul></ul><ul><ul><li>Migrate DBs Individually to Staging Server </li></ul></ul><ul><ul><ul><li>Use Backup & Restore </li></ul></ul></ul><ul><ul><ul><li>Point Apps to New Location </li></ul></ul></ul><ul><ul><li>Over Weekend </li></ul></ul><ul><ul><ul><li>Move DBs to new cluster </li></ul></ul></ul><ul><ul><ul><li>Rename cluster to name of staging server </li></ul></ul></ul>
  10. 10. Fix Your Tools <ul><li>Migrate DTS Packages To SSIS </li></ul><ul><li>There are problems directly migrating DTS packages from the server to SSIS </li></ul><ul><li>Online resources indicate problems lie in Package names. </li></ul><ul><li>Upgrade advisor does not check this. </li></ul><ul><li>We chose to export from 2K5 to Structured Text Files then upgraded each separately. </li></ul>
  11. 11. Fix Your Tools <ul><li>Migrate DTS Packages To SSIS </li></ul><ul><li>Upgrade wizard will not convert all tasks. </li></ul><ul><li>Tasks not converted will remain DTS tasks within a SSIS rapper. </li></ul><ul><li>This causes confusion with connection strings as they are changed in the DTS package, not the SSIS rapper. </li></ul>
  12. 12. Fix Your Tools <ul><li>Migrate DTS Packages To SSIS </li></ul><ul><li>Packages not upgraded will need to be redeveloped in SSIS. </li></ul>
  13. 13. Fix Your Tools <ul><li>Migrate DTS Packages To SSIS </li></ul><ul><li>SSIS Development </li></ul><ul><ul><li>Be careful of the 64 bit environment </li></ul></ul><ul><ul><li>SSIS will not use 32 bit drivers event if installed on the server. </li></ul></ul><ul><ul><li>This has implications when accessing data with Jet drivers as no 64 bit versions do not exist. </li></ul></ul><ul><ul><li>Explicit data type conversions are expected especially between Unicode and non-Unicode. </li></ul></ul>
  14. 14. Fix Your Tools <ul><li>Migrate DTS Packages To SSIS </li></ul><ul><li>SSIS development environment validates on the fly. </li></ul><ul><ul><li>While this is a nice feature it can take some time when validating large packages. </li></ul></ul><ul><li>SSIS will not retain passwords within the connection strings. </li></ul><ul><ul><li>Workaround is to use configuration files. </li></ul></ul>
  15. 15. Meet Your Neighbors <ul><li>Set Up Linked Servers & Distributed Queries </li></ul>
  16. 16. 64-bit 2K5 to 32-bit 2k <ul><li>Install SP3 or SP4 on 2K boxes </li></ul><ul><li>Manually run Instcal.sql </li></ul><ul><li>Reference: </li></ul><ul><ul><ul><li>http:// support.microsoft.com/default.aspx?scid =kb;en-us;906954 </li></ul></ul></ul>
  17. 17. Enjoy! <ul><li>Sit Back </li></ul><ul><li>Relax </li></ul><ul><li>Chill Out </li></ul>

×