COLLATE SQL_Latin1_General_CP1_CI_AS

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Development (2000)

COLLATE SQL_Latin1_General_CP1_CI_AS

Author

Topic

dbleyl
Starting Member

21 Posts

Posted - 2004-07-02 : 11:35:45

Before attaching a database to our server, varchar characters appeared
this way in scripts:
col_name varchar(3) NULL, ...
After attaching a certain database, all the scripts generate this
col_name varchar(n) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

I understand this specifies the character code for sorting purposes,
but it is not necessary for our applications and the attached db has
since been removed.
1.) How do you get rid of this?
2.) Is it better to have it?

X002548
Not Just a Number

15586 Posts

Posted - 2004-07-02 : 11:43:01

You're going from SQL 7.0 to 2000, correct?

Brett

8-)

dbleyl
Starting Member

21 Posts

Posted - 2004-07-02 : 12:36:28

We were evaluating some software that used SQL Server. The db may have been
7, but all the servers are 2k.

X002548
Not Just a Number

15586 Posts

Posted - 2004-07-02 : 12:55:36

quote:

I understand this specifies the character code for sorting purposes,
but it is not necessary for our applications and the attached db has
since been removed.

1.) How do you get rid of this?
2.) Is it better to have it?

Well it is nessacary..you just never noticed in 7.

1). You don't and you can't
2). No Choice

In 7.0 it was at the sever level.

In 2000 Collation can go down to the column level

You've got standard everything, out of the box settings.

Count your blessings. You should have no problems..

Do this and tell me if you get an error message..


SELECT * FROM INFORMATION_SCHEMA.Tables a 
INNER JOIN OneOfYourTables b ON a.TABLE_NAME = b.someVarcharColumn
WHERE 1=0

Tell us if you get any errors

Brett

8-)

dbleyl
Starting Member

21 Posts

Posted - 2004-07-02 : 13:07:02

No errors, and no rows returned. So everything is fine?
The db that we attached had some French columns, and I was concerned
because I had never seen the COLLATE. I guess I just didn't notice it.
Thanks for the assurance.

X002548
Not Just a Number

15586 Posts

Posted - 2004-07-02 : 13:33:02

Sounds like you're ok...

You've never noticed it before because it was a server level option in 7.0

For example, if you had two different setups between servers, you wouldn't ne able to dump and restore the 2.

In 2k, like I said, it can go dsown to the column level.

I've just been going through collation hell lately

Brett

8-)

dbleyl
Starting Member

21 Posts

Posted - 2004-07-02 : 13:58:49

Thanks a lot for the help!

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources