MSDE dbase move & local FulldbImport.

[d1nnsear]

Evening folks.

I want to move a VM only 2.4.6 system onto a new box with 4.0(4) and UM.

The new server will have a new IP address & comp name. I'm planning on doing a fulldbexport, fulldbimport & then a user data migration to point the correct mailboxes to the new subs (as my aliases are different on the 2 Exchange boxes).

I'm hoping that part's all good and the new ip & name won't be a prob.

What I'd like to clarify is when to move the MSDE database from the c:\ to the d:\? Normally I'd do this before adding any subs. I know the import is pretty fussy & won't import if you've made ANY changes on the new install.

So should I move the dbases before I do the dbimport or after? I'd kinda rather do it before.

Cheers.

NJ.

[d1nnsear]

Anyone done this before?

[lindborg · Accepted solution]

FullDBImport doesn't care where your DB is - it doesn't go that low level. When it's adding items into the database it's doing it using the "UnityDB" DB name and it lets SQL figure out where the physical DB files and logs are located.

Personally, I'd move the DB first and make sure everything is working properly before doing the import.

[d1nnsear]

Thanks for the clarification.