Is my problem too complex for even Forum MVPs to solve? 1

[DeepDiverMom]

I’m posting my problem a second time since I have had no respondents since my original post last Monday morning, June 28. I cannot believe that this problem is so complex that no one (including MVPs) can give me some guidance. If my only option is to get help directly from Microsoft Tech Support, please advise me of that. I must resolve this issue before it turns 1 week old, so I am becoming desperate.

Here is our problem: We attempted to restore .BAK files on MS SQL Server 7.00.1063 that we dumped from another SQL Server instance. At the beginning of the restore, we encountered this error:

"Microsoft SQL-DMO SQL (ODBC SQLState: 42000)
The database you are attempting to restore was backed up under a different Unicode locale (ID 33280) or Unicode comparison style (0) than the Unicode locale ID (1033) or Unicode comparison style (196609) currently running on this server. Backup or restore operation terminating abnormally. [OK]

I have reviewed Thread962-705843 "2 different Unicode Collation", which indicates that there is a way to overcome this issue, but that thread did not disclose the resolution method. We would like to avoid having to reinstall SQL Server with the "old" server's Unicode settings.

What, then, is the easiest/best way to resolve this issue?

Becca

 

[JayKusch]

First off to get on the same page, we are talking about a SQL Server 7 to another SS7 installation ... Correct?

Thanks

J. Kusch

 

[JayKusch]

Nigel did give two methods of attack in the link you have listed in your post. the first is on a "column level" the other is on a "database level".


You can also specify the collation at the column level but this will still cause problems and probably mean a lot of work.

Changing the collation of the database on the transfer would be easiest but it's a business decision as to whether or not this will cause problems.


If you are going from SS7 platform to another SS7 platform, you have only 2 options ... rebuild the Master DB or ReInstall SS7. Here is a blurb on that subject matter.

Unfortunately, SQL Server 7.0 doesn't provide a mechanism for changing collations on the fly. To change the collation of an existing database, you need to rebuild the master database or reinstall SQL Server. You can find information about the rebuild process in SQL Server Books Online (BOL) in "How to rebuild the master database (Rebuild Master utility)." Remember, rebuilding the master database means recreating all logins. And in SQL Server 7.0, you can't reattach a database that has a different collation than the server. You'll need to use another mechanism, such as Data Transformation Services (DTS) or bulk copy program (BCP), to bring the data back in. The process isn't much different than starting from scratch with a complete reinstall.


Now if you have SQL Server 2000 running, and you just want to change the collation on 1 database, you can use the ALTER DATABASE w/ the COLLATION verb to change it.

If you want to change ALL of the database to a different collation you will need to ...


rebuild the master database

Shutdown Microsoft® SQL Server™ 2000, and then run Rebuildm.exe. This is located in the Program Files\Microsoft SQL Server\80\Tools\Binn directory.

In the Rebuild Master dialog box, click Browse.

In the Browse for Folder dialog box, select the \Data folder on the SQL Server 2000 compact disc or in the shared network directory from which SQL Server 2000 was installed, and then click OK.

Click Settings. In the Collation Settings dialog box, verify or change settings used for the master database and all other databases.
Initially, the default collation settings are shown, but these may not match the collation selected during setup. You can select the same settings used during setup or select new collation settings. When done, click OK.

In the Rebuild Master dialog box, click Rebuild to start the process.
The Rebuild Master utility reinstalls the master database.

Note To continue, you may need to stop a server that is running.


Hope this give you something to work with!!!

Let us know how it works out and GOOD LUCK!



Thanks

J. Kusch

 

[DeepDiverMom]

Jay,

Thank you so much for your responding.

In your first reply, you wondered about versions. In my case, the source database was SQL Server 6.5; the target 7.0. Given these circumstances, what are my options? A re-install of the target 7.0 database?

Becca

 

[JayKusch]

That may be your best bet!

Thanks

J. Kusch

 

[DeepDiverMom]

Jay,

Thanks for all your excellent help and information. Please accept a "Purple Twinklie".

Becca