April 27, 2015 at 1:10 pm
Can some kindly help me how to move sql 7.0 to sql 2008R2. We have 10 databases and there are 15 DTS Packages but when I script out the jobs I found that only one job is calling only two packages and seem like other are inactive. Can someone help me to find out that these DTS Package are running or idle. Also step how to move everyone with breaking anything. Thanks
April 27, 2015 at 1:56 pm
sureshjevani 78421 (4/27/2015)
Can some kindly help me how to move sql 7.0 to sql 2008R2. We have 10 databases and there are 15 DTS Packages but when I script out the jobs I found that only one job is calling only two packages and seem like other are inactive. Can someone help me to find out that these DTS Package are running or idle. Also step how to move everyone with breaking anything. Thanks
Quick question, is a side by side upgrade an option? Easiest would be a two phased, first to 2005 and then to 2008, evaluate the DTS at the 2005/middle stage.
😎
April 27, 2015 at 2:19 pm
I would try to use Upgrade Advisor first....however, I'm not sure it will work with SQL Server 7.0. Check this link out..
https://msdn.microsoft.com/en-us/library/ms144256(v=sql.105).aspx
That (if if works for 7.0) will let you know which objects will no longer work in SQL Server 2008 R2. Those objects will need to be recoded getting rid of the old syntax. The advisor will even tell you what the issue is.
If the Upgrade Advisor doesn't work with 7.0, then you will have an issue as some objects may not upgrade properly. I would backup all your databases, then make them read-only on the 7.0 version. Restore them onto the 2008R2 version allowing the upgrade to happen. If anything fails, you'll need to resolve the issue. By leaving the databases on the 7.0 version, it gives you a fall-back if the database doesn't upgrade properly. you can use the 7.0 version while you work on resolving the issues.
-SQLBill
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply