Is this collation correct?

Hi Everyone,
I've taken over this database and asked to optimize performance. I noticed
that we have 'SQL_Latin1_General_CP1.CI_AS' set for out database collation.
We collect data from two points in the USA and in Hong Kong.
Question: Is this the best collation to use for this environment?
Thanks in advance.
Larry
That is the default collation for SQL Server and probably will meet your
needs fine.
Your life will probably be easier if all the servers are using the same
collation.
You won't get a performance boost from using a different collation.
Brian
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:4E8914BF-B1C8-4CC7-9994-5BDB1656E664@.microsoft.com...
> Hi Everyone,
> I've taken over this database and asked to optimize performance. I
noticed
> that we have 'SQL_Latin1_General_CP1.CI_AS' set for out database
collation.
> We collect data from two points in the USA and in Hong Kong.
> Question: Is this the best collation to use for this environment?
> Thanks in advance.
> Larry
|||Note that that collation can only store Chinese text in Unicode fields
(nvarchar, nchar). You should use Unicode data types if you have an app
with international users. If your schema currently does not use Unicode
data types, though, you should probably be using a Chinese collation so
that you can store Chinese non-Unicode text safely. This recommendation
doesn't have anything to do with performance. As Brian mentioned,
collation isn't the right place to start if you're looking to optimize
performance.
Bart
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "Brian Moran" <brian@.solidqualitylearning.com>
| References: <4E8914BF-B1C8-4CC7-9994-5BDB1656E664@.microsoft.com>
| Subject: Re: Is this collation correct?
| Date: Fri, 17 Sep 2004 09:47:44 -0400
| Lines: 30
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| Message-ID: <OxXUrzLnEHA.132@.TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: pcp02581462pcs.reston01.va.comcast.net 68.50.27.82
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:360329
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| That is the default collation for SQL Server and probably will meet your
| needs fine.
|
| Your life will probably be easier if all the servers are using the same
| collation.
|
| You won't get a performance boost from using a different collation.
|
| --
|
| Brian
|
|
| "Larry" <Larry@.discussions.microsoft.com> wrote in message
| news:4E8914BF-B1C8-4CC7-9994-5BDB1656E664@.microsoft.com...
| > Hi Everyone,
| >
| > I've taken over this database and asked to optimize performance. I
| noticed
| > that we have 'SQL_Latin1_General_CP1.CI_AS' set for out database
| collation.
| > We collect data from two points in the USA and in Hong Kong.
| >
| > Question: Is this the best collation to use for this environment?
| >
| > Thanks in advance.
| >
| > Larry
|
|
|