collate in SQL server (value CS/table CI) 
Author Message
 collate in SQL server (value CS/table CI)
I want the values of my tables be CS and not the table/column names.  
In Oracle, this works fine.   But on SQL Server, either they are both
CS or CI.

Is there a work around this?

I tried adding COLLATE to each of my columns.   As a result, the
table/column names were no longer CS.   But I ran into some other
problems.

I couldn't find any best practice docs on MSDN.

thanks
reza



Mon, 05 Dec 2005 21:18:36 GMT
 collate in SQL server (value CS/table CI)

You could create the database using a collation of CS, create all of your objects and then alter the database to be CI.

--
Tom

---------------------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql

I want the values of my tables be CS and not the table/column names.  
In Oracle, this works fine.   But on SQL Server, either they are both
CS or CI.

Is there a work around this?

I tried adding COLLATE to each of my columns.   As a result, the
table/column names were no longer CS.   But I ran into some other
problems.

I couldn't find any best practice docs on MSDN.

thanks
reza



Mon, 05 Dec 2005 21:30:55 GMT
 collate in SQL server (value CS/table CI)
However, when the db's collate is CI, I run into a
different problem.

I have a lot views that I create like this
CREATE VIEW X AS select 'form' as object_id, ....

Later, joins between these views and other tables fail
because of collate incompatiblities.   I like to keep my
view definitions db independent and not cast 'form' to the
correct collate.  Is there a way around this?

Ideally, I want a pure CS db.   Except that I don't want
the CS-ity to be applied to table/column names.  

thanks
reza

Quote:
>-----Original Message-----
>You could create the database using a collation of CS,

create all of your objects and then alter the database to
be CI.
Quote:

>--
>Tom

>----------------------------------------------------------
-----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql




Quote:
>I want the values of my tables be CS and not the

table/column names.  
Quote:
>In Oracle, this works fine.   But on SQL Server, either
they are both
>CS or CI.

>Is there a work around this?

>I tried adding COLLATE to each of my columns.   As a
result, the
>table/column names were no longer CS.   But I ran into
some other
>problems.

>I couldn't find any best practice docs on MSDN.

>thanks
>reza



Tue, 06 Dec 2005 02:17:27 GMT
 collate in SQL server (value CS/table CI)

Did you get this when you created the views while the DB was CS and later changed it back to CI, once the views had been created?

--
   Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada
www.pinnaclepublishing.com/sql
.
However, when the db's collate is CI, I run into a
different problem.

I have a lot views that I create like this
CREATE VIEW X AS select 'form' as object_id, ....

Later, joins between these views and other tables fail
because of collate incompatiblities.   I like to keep my
view definitions db independent and not cast 'form' to the
correct collate.  Is there a way around this?

Ideally, I want a pure CS db.   Except that I don't want
the CS-ity to be applied to table/column names.  

thanks
reza

Quote:
>-----Original Message-----
>You could create the database using a collation of CS,

create all of your objects and then alter the database to
be CI.
Quote:

>--
>Tom

>----------------------------------------------------------
-----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql




Quote:
>I want the values of my tables be CS and not the

table/column names.  
Quote:
>In Oracle, this works fine.   But on SQL Server, either
they are both
>CS or CI.

>Is there a work around this?

>I tried adding COLLATE to each of my columns.   As a
result, the
>table/column names were no longer CS.   But I ran into
some other
>problems.

>I couldn't find any best practice docs on MSDN.

>thanks
>reza



Tue, 06 Dec 2005 02:57:13 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. About the use o collate on Table or Database(MS sql server 7.0/2000)

2. Sql 2000 - Import tables - Incorrect syntax near COLLATE

3. Table Corruption. ( oncheck -cI )

4. Upgrating to SQL Server 2000: collate problem

5. Importing EXEL file into sql server 2000 Database gives COLLATE error

6. Turkish CI Collation on server MSSQL2000

7. case sensitive function in CI-SQL

8. Documents in tables in CS ?

9. How to get default values into dataset from sql server table

10. getting distinct values from one table ordered by value from another table

11. DEFAULT values not in SQL Server table after (recrodset).update

12. update values in table A from values in table B


 
Powered by phpBB® Forum Software