December 17, 2003 at 4:45 am
Hello
very shortly I will have the opportunity to install SQL 2000 Enterprise on a Cluster Setup using a SAN. This is a v.good thing as the company I work for has little DR protection at the moment. I will not be setting up the hardware, as we have an 'Ops' department for this, but will be involved in installing SQL and migrating the data from the current platform. My Question is this:
The current Collation on the Production Environment is incorrectly set to charset=iso_1 sort_order=nocase_iso charset_num=1 sort_order_num=52
AKA SQL_Latin1_General_CP1_CI_AS
What is the best way to move the data from the current 'Production' Platform to the new one, changing the collation on the way?
* Restore From Backup?
* DTS?
* bcp?
* Other?
Cheers
Jacko
December 17, 2003 at 5:18 am
The most bullet proof way is to restore the databases. If you can though. I would detatch your user databases from the current system copy the files over to the san clustered drives and reattach them. That is the quickest way, and you shouldn't have any problems with that ether. I've done several moves in this mannor.
Wes
December 17, 2003 at 7:49 am
Thanks Wes
Just to be sure, did Restoring the Backups change the collation?
I have a test environment with a different collation, & using SSCodeGen (available from this site), I get an error stating
'can't resolve collation conflict for equal to operation.'
This error does not occur if I run the Util against the 'production' system, or on a db I am developing locally.
I am loathe to get this wrong & it not show up until several weeks later...
December 17, 2003 at 6:29 pm
Collation will be what the collation of the database is if you restore or detatch and reattach collation shouldn't change.
Wes
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply