dbTalk Databases Forums  

Re: Changing Collation of SQL2K

microsoft.public.sqlserver.setup microsoft.public.sqlserver.setup


Discuss Re: Changing Collation of SQL2K in the microsoft.public.sqlserver.setup forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
kris yumul [MS]
 
Posts: n/a

Default Re: Changing Collation of SQL2K - 07-15-2003 , 11:58 AM






From SQL Books Online:

The COLLATE clause can be specified at several levels, including the
following:
1.. Creating or altering a database.
You can use the COLLATE clause of the CREATE DATABASE or ALTER DATABASE
statement to specify the default collation of the database. You can also
specify a collation when you create a database using SQL Server Enterprise
Manager. If you do not specify a collation, the database is assigned the
default collation of the SQL Server instance.

Note: SQL Server can support only code pages that are supported by the
underlying operating system. When you perform an action that depends on
collations, the SQL Server collation used by the referenced object must use
a code page supported by the operating system running on the computer.

--
Kris Yumul [MS]

This posting is provided "AS IS" with no warranties, and confers no rights

"Ida" <i.espiritu (AT) weserv (DOT) com.ph> wrote

Quote:
We recently upgraded our database from SQL7 to SQL 2000.
SQL 2000 automatically set its collation order to
SQL_Latin1_General_CP1_CI_AS, which was not helpful at all
because Korean characters that are suppose to be displayed
are displayed as special characters. We tried to change
the collation order to Korean_Wansung_CI_AS through the
ALTER DATABASE command. This did not solve the problem as
the collation order of all the tables still remains
SQL_Latin1_General_CP1_CI_AS inspite of the change.

My question is, would there be a better and effecient way
to use the collation order of the database for all the
tables without changing the collation order (of the
tables) one by one?

Thanks in advance.



Reply With Quote
  #2  
Old   
Jasper Smith
 
Posts: n/a

Default Re: Changing Collation of SQL2K - 07-15-2003 , 05:09 PM






For existing data, it's either a case of doing the alter table with
the associated dropping of indexes and constraints on those
columns and recreating after the collation change, or creating an
empty copy of the database with the target collation and moving
the data. Here's a good post on the subject http://tinyurl.com/h1ir

--
HTH

Jasper Smith (SQL Server MVP)

I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org

"Ida" <i.espiritu (AT) weserv (DOT) com.ph> wrote

We recently upgraded our database from SQL7 to SQL 2000.
SQL 2000 automatically set its collation order to
SQL_Latin1_General_CP1_CI_AS, which was not helpful at all
because Korean characters that are suppose to be displayed
are displayed as special characters. We tried to change
the collation order to Korean_Wansung_CI_AS through the
ALTER DATABASE command. This did not solve the problem as
the collation order of all the tables still remains
SQL_Latin1_General_CP1_CI_AS inspite of the change.

My question is, would there be a better and effecient way
to use the collation order of the database for all the
tables without changing the collation order (of the
tables) one by one?

Thanks in advance.



Reply With Quote
  #3  
Old   
Ida Espiritu
 
Posts: n/a

Default Re: Changing Collation of SQL2K - 07-15-2003 , 10:29 PM




Thank you. We will try your recommendations and we'll let you know.

Million thanks!




*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.