Moving Database To A New Server

[MasterRacker]

We are getting ready to decommission a server and as part of that I need to move a SQL 2000 DB to a different server. The new server is running SQL 2005. I'm attempting to get info from the vendor about the 2000 vs 2005 issue with their product, however I'm thinking that part should be OK.

Looking at the system via Mgmt Studio, the app appears to use Windows Authentication, however looking at the defined logins, I don't even see a user role assignment to this app for any of the logins. There are SQL logins also, but none are assigned to this app and I'm almost certain they're for a different app (that will hopefully be retired) anyway.

I'm hoping to simply detach the DB, move the mdf and ldf appropriately and re-attach, duplicating logins. Is there a SID sync that has to happen with Windows logins?

Also, this app actually appears to use 3 DB's, "App". "App_Admin" and "App_Model". What caveats/problems does this suggest?



_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[MasterRacker]

Got some good info back from the vendor. There's actually a server component that also has to be installed. After a full server installation, I just copy the live data over the new blank DB's.

(Now if I could just do something about the SQL ID whose password is stored in an INI file.... )

_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]