September 25, 2007 at 12:26 pm
Planning to upgrade from 2000 to 20005. Just want to know what is going to break. So I can have a plan for it.
September 25, 2007 at 12:31 pm
Run Microsoft's Upgrade Adviser (including a check of SQL running on the machine from a profiler trace).
September 28, 2007 at 7:22 am
Did upgrade...I unistalled 2000 and installed 2005. I think i did it wrong. Cause i lost all the user names and linked servers. But I dunnot what i did wrong.
September 28, 2007 at 8:33 am
x-portal (9/28/2007)
Did upgrade...I unistalled 2000 and installed 2005. I think i did it wrong. Cause i lost all the user names and linked servers. But I dunnot what i did wrong.
How did you upgrade exactly? Did you just back your database up and restored? Linked servers and login information are stored in the master database.
Regards,
Andras
October 2, 2007 at 1:59 pm
i uninstalled SS2k and installed SS2k5. Then attached the 3 Databses, recreated the link servers and logins
October 2, 2007 at 2:13 pm
As Andras stated, that information is stored in the master database. The loss of logins, etc, that you describe is expected behavior for the upgrade path that you used. Your best bet is to do a backup / restore of all databases and to script out all users. roles etc.
October 2, 2007 at 8:53 pm
thanks, you guys are very helpful.
October 3, 2007 at 1:12 pm
There's a stored proc on microsoft's site called sp_help_revlogins that will script all the windows and sql logins that are in master. Run that and save the output. Apply that to the new instance to get your logins. Then resolve your orphaned users and you're fine.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply