Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
latingntlman
Yak Posting Veteran
96 Posts |
 Posted - 2009-02-10 : 12:43:34
|
| We've been asked to take lead on some of the migration tasks from 2000 to 2005 as follows:Identify / migrate all used tables to 2005.Identify / migrate used views to 2005.Identify / migrate used functions to 2005.Identify / migrate used sprocs to 2005.Identify / migrate user RS2005 reports to 2005 (along w/data sources, sprocs or queries).Identify / migrate active DTS jobs to 2005.My grand question: What are the best practices or steps that should be followed, and in what direction or sequence for a smooth, effective transition?Any input from the experts will be welcome and definitely given some thought.Regards,John |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
latingntlman
Yak Posting Veteran
96 Posts |
Posted - 2009-02-10 : 15:45:08
|
| Maybe I wasn't specific enough and I apologize, but our DBA has already done those tasks. I guess the tasks that I've been asked of are Data Analysis/Reporting related tasks, such as, identifying the RS2000 Reports that need to be migrated to SSRS2005. Any sprocs used by our RS2005 reports; functions; tables or views; DTS packages that need to be migrated to SSIS 2005. I could look at each report and log the datasource, sproc, etc that it uses and make sure all this gets migrated to 2005. I was just wondering if there was a more efficient way. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-10 : 19:59:23
|
quote:
Originally posted by latingntlman
Maybe I wasn't specific enough and I apologize, but our DBA has already done those tasks. I guess the tasks that I've been asked of are Data Analysis/Reporting related tasks, such as, identifying the RS2000 Reports that need to be migrated to SSRS2005. Any sprocs used by our RS2005 reports; functions; tables or views; DTS packages that need to be migrated to SSIS 2005. I could look at each report and log the datasource, sproc, etc that it uses and make sure all this gets migrated to 2005. I was just wondering if there was a more efficient way.
You can use this: We use this approach to move Reporting Services:http://msdn.microsoft.com/en-us/library/ms156421(SQL.90).aspx[quote] |
|
|
|
|
|
|
|
|
Migrating from SQL 2000 to 2005