Re: Different Collation designator Settings

From: Jacco Schalkwijk (jacco.please.reply_at_to.newsgroups.mvps.org.invalid)
Date: 01/24/05 

Date: Mon, 24 Jan 2005 22:06:18 -0000

Hi Shadow,

You can have databases (and even columns) with different collations on SQL
Server 2000. That wasn't possible on SQL Server 7.

Whether it is going to work with 3rd party application is uncertain though.
The problem is that temporary tables are created with the collation of
tempdb on your server. And unless the 3rd party applications are good
quality code (which unfortunately is quite unlikely), there is a good chance
that they will compare character values in permanent tables with character
values in temporary tables while assuming that tempdb has the same collation
as the database that application uses. And if that is not the case, you will
get collation conflicts.

This can be avoided by specifying COLLATE DATABASE_DEFAULT with each
character column when creating temporary tables so that the default
collation of the database the user is currently connected to is used. But as
I said earlier, applications very rarely get up to this level of code
quality.

You would probably best off to have 2 servers, one with Latin1_General
collation and one with Turkish collation. 

-- 
Jacco Schalkwijk
SQL Server MVP
"Shadow" <shadowfaxx001@hotmail.com> wrote in message 
news:ePhKpPlAFHA.2112@TK2MSFTNGP14.phx.gbl...
> Greetings,
>
> In our company we have different kinds of SQL databases and SQL servers. 
> We are trying to consolidate those servers under a couple of powerful 
> servers. But when we began to tell this project to software houses and ask 
> their idea; we met a big problem .
>
> Some of those companies are using SQL databases with Collation Designator 
> = Latin1_General setting. But the majority is using with Collation 
> Designator = Turkish setting. We want to consolidate them under a big MS 
> SQL Server 2000. Anybody that we asked said that is impossible to 
> consolidate those databases under a server.
> So my questions are ;
>
> 1- Is is really impossible to consolidate SQL dbases with different 
> character sets under a single server ? (Latin1_General  +  Turkish )
>
> 2- If no, how should I setup this MS SQL Server to support those char.sets 
> ?
>
> I will be very happy if anybody can help me .
>
> Best regards.
> Shadowfax
>
>
>
>

Relevant Pages

  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.odbc)
  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.connect)
  • Re: Different Collation designator Settings
    ... You can have databases with different collations on SQL ... That wasn't possible on SQL Server 7. ... values in temporary tables while assuming that tempdb has the same collation ...
    (microsoft.public.sqlserver.setup)
  • Re: How to move system databases to new SAN drive in cluster serve
    ... I have moved model, msdb, and tempdb on a cluster ... Moving SQL Server databases to a new location with Detach/Attach ...
    (microsoft.public.sqlserver.clustering)
  • Re: Migrate stand alone sql server to a cluster without downtime
    ... Use backup and restore to create the databases on the new system. ... Run a log backup WITH STANDBY on each database on the old server. ... I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.clustering)
Loading