Detach removes the database from original MS SQL instance, but it can always be re-attached.
The only caveat I can think of is with regards to users in 2 different ways: 1) when you re-attach a database the user ID that re-attached is the DB owner. That may or may not cause a problem but something to be mindful of. 2) End-user accounts if your application uses database users for authentication - those are stored in the "master" DB of the SQL 2000 SP4 instance and won't transfer over automatically, regardless of whether you use the detach/reattach or backup/restore method. If you use detach/reattach you might end up having to redo those. BTW, the backup/restore method I'm thinking of is the one in the Enterprise Manager. If your application has it's own backup/restore procedure it would be best to use that for the backup. In my experience the application-specific backup/restore procedure will take care of point 2. I suspect you will want to ask some of your questions in a MS SQL-specific forum - SQL Server Central (http://www.sqlservercentral.com/) comes to mind. Don't you have a test environment for this application? Joseph L. Casale wrote: > Just asking as once I apply SP4 and attempt the migration I can't > undo this (other reasons). I know SQL versions sometimes perform > upgrades... > > On another note, I don't know sh!t about mssql, but I was going to > backup to a file, then restore from a file. Is the this detaching > method you speak of the same thing or what caveats occur between the > two methods? -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
