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 |
|
jason7655
Starting Member
24 Posts |
 Posted - 2008-07-08 : 11:19:53
|
| Currently our environment has one main production database server running SQL Server 2000 SP4. Would it be possible to migrate a few of those databases to SQL Server 2005 on a different server without seeing any problems with the databases talking to each other? I know you can't cover ever scenario but I'm basically wondering that if on the surface everything is very similar with logins and such then can the above scenario work at all in theory? |
|
|
mdubey
Posting Yak Master
133 Posts |
Posted - 2008-07-08 : 11:22:26
|
| That is not recomnded. If this is DEV server then probably "Yes", you can do that, but if it is PROD then "NO".ManojMCP, MCTS |
 |
|
|
jason7655
Starting Member
24 Posts |
Posted - 2008-07-08 : 11:26:08
|
quote:
Originally posted by mdubey
That is not recomnded. If this is DEV server then probably "Yes",
well, it would be tested first with dev but it would be a quicker route to getting the production dbs to 2005. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-08 : 11:31:02
|
| Depends in what resources you have on new server like memory,processor and which edition on SQL 2005.Rebuild all fragmented index(Which will update stats as well) and update stats for remaining DB and check in SQL 2005. |
|
|
|
jason7655
Starting Member
24 Posts |
Posted - 2008-07-08 : 11:42:28
|
quote:
Originally posted by sodeep
Depends in what resources you have on new server like memory,processor and which edition on SQL 2005.
64 bit high end machine running Enterprise. So you are saying it's ok and we don't run any risk?I would just like to know what the gotchas are and what might be a problem if this was tried. |
|
|
|
maninder
Posting Yak Master
100 Posts |
Posted - 2008-07-08 : 14:22:21
|
Well you have to move to Logins over to the new Box, using the http://support.microsoft.com/kb/246133.Also check for ORPHANED Logins once you move the Databases over. (exec sp_msforeachdb @command1='use  exec sp_change_users_login ''Report'' ')Use Backup and Restore instead of other Methods.RUN DBCC UPDATEUSAGE and DBCC CHECKDB after the UPGRADE.Also Check to see the Functions/SP's in the Database does not have any depreciated Code.Best Methond will be RUN the UPGRADE ADVISOR before Proceeding.nothing is SIMILAR in the SURFACE, as a DBA you have to Check all aspects internally, before making the move.ManinderSQL server Architect / Admin (DEV&PROD) |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-09 : 23:07:32
|
| Also rebuild indexes after moving to sql2k5. |
|
|
|
|
|
|
Running 2000 and 2005 simultaneously