Collation settings for a website in Russian

I am using html, vbscript, asp and sql server.
The website is mainly in Russian but may have some English.
The consensus appears to be that it is best to use utf-8, so I plan to use
html charset utf-8, asp codepage 65001 and ntext, nchar and nvarchar
character
types.
If the above is correct, what collation should I use in SQL Server?
Thanking you in anticipation.
Posted Via webservertalk.com Premium Usenet Newsgroup Services
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
http://www.webservertalk.com
It all depends on what type of data you are storing and is it
case-sensitive/case-insensetive in the DB. Run the following query and
will explain you each collation usage.
SELECT *
FROM ::fn_helpcollations()
-SAI

Collation settings for a website in Russian

I am using html, vbscript, asp and sql server.
The website is mainly in Russian but may have some English.
The consensus appears to be that it is best to use utf-8, so I plan to use
html charset utf-8, asp codepage 65001 and ntext, nchar and nvarchar
character
types.
If the above is correct, what collation should I use in SQL Server?
Thanking you in anticipation.
Posted Via mcse.ms Premium Usenet Newsgroup Services
----
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----
http://www.mcse.msIt all depends on what type of data you are storing and is it
case-sensitive/case-insensetive in the DB. Run the following query and
will explain you each collation usage.
SELECT *
FROM ::fn_helpcollations()
-SAI

Collation settings for a website in Russian

I am using html, vbscript, asp and sql server.
The website is mainly in Russian but may have some English.
The consensus appears to be that it is best to use utf-8, so I plan to use
html charset utf-8, asp codepage 65001 and ntext, nchar and nvarchar
character
types.
If the above is correct, what collation should I use in SQL Server?
Thanking you in anticipation.
Posted Via Usenet.com Premium Usenet Newsgroup Services
----
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----
http://www.usenet.comIt all depends on what type of data you are storing and is it
case-sensitive/case-insensetive in the DB. Run the following query and
will explain you each collation usage.
SELECT *
FROM ::fn_helpcollations()
-SAI

Collation setting

Hi
We have a sqlserver 2005 DB which is mainly used by sharepoint. We are
using "Latin1_General_CI_AS_KS_WS" collation for SharePoint Portal Server
2003 databases. When I have installed the server I have installed
"Latin1_General_CI_AS
" collation which is the default collation setting for canada.
So now we have different collation settings for the the system databases and
sharepoint databases. Which collation setting should I keep?
Thanks
--
ontario, canadaI would go with the default collation (sort id 52) that is
SQL_Latin1_General_CP1_CI_AS. (This depends on what your need)
However, in your current situation it appears that your databases are using
a different collation and the server is installed using a different
collation. you can do one of the following things:
1) Change the collation at the database level to match the collation of the
server.
2) Change the collation at the server level. (recommended)
Take a look at this tip on how to change the collation at the server level:
http://www.sqlcommunity.com/SQLTips/tabid/77/grm2id/21/Default.aspx
--
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide SQL Server Community)
SQLTips, Scripts, Discussions, Blogs, Articles, Radio and a lot of SQL
Server Fun.
"db" wrote:
> Hi
> We have a sqlserver 2005 DB which is mainly used by sharepoint. We are
> using "Latin1_General_CI_AS_KS_WS" collation for SharePoint Portal Server
> 2003 databases. When I have installed the server I have installed
> "Latin1_General_CI_AS
> " collation which is the default collation setting for canada.
> So now we have different collation settings for the the system databases and
> sharepoint databases. Which collation setting should I keep?
> Thanks
> --
> ontario, canada|||On Oct 4, 5:40 pm, db <d...@.discussions.microsoft.com> wrote:
> Hi
> We have a sqlserver 2005 DB which is mainly used by sharepoint. We are
> using "Latin1_General_CI_AS_KS_WS" collation for SharePoint Portal Server
> 2003 databases. When I have installed the server I have installed
> "Latin1_General_CI_AS
> " collation which is the default collation setting for canada.
> So now we have different collation settings for the the system databases and
> sharepoint databases. Which collation setting should I keep?
>
Sharepoint's Collation.
If Sharepoint is the only application that server serves, then it
would be better
you rebuild the server with Sharepoint's collation. If the server
serves other
applications too, then you can maintain the server with multiple
collations,
but this is a risky business.
Regards,
Sasi.
> Thanks
> --
> ontario, canada|||Thanks saleem and sasiraj. What is the difference between
"Latin1_General_CI_AS_KS_WS" and "Latin1_General_CI_AS" collation.
ontario, canada
"sasiraj" wrote:
> On Oct 4, 5:40 pm, db <d...@.discussions.microsoft.com> wrote:
> > Hi
> > We have a sqlserver 2005 DB which is mainly used by sharepoint. We are
> > using "Latin1_General_CI_AS_KS_WS" collation for SharePoint Portal Server
> > 2003 databases. When I have installed the server I have installed
> > "Latin1_General_CI_AS
> > " collation which is the default collation setting for canada.
> >
> > So now we have different collation settings for the the system databases and
> > sharepoint databases. Which collation setting should I keep?
> >
> Sharepoint's Collation.
> If Sharepoint is the only application that server serves, then it
> would be better
> you rebuild the server with Sharepoint's collation. If the server
> serves other
> applications too, then you can maintain the server with multiple
> collations,
> but this is a risky business.
> Regards,
> Sasi.
> > Thanks
> > --
> > ontario, canada
>
>|||db wrote:
> Thanks saleem and sasiraj. What is the difference between
> "Latin1_General_CI_AS_KS_WS" and "Latin1_General_CI_AS" collation.
The difference is unimportant for most parts of the world (except
Asia). Latin1_General_CI_AS_KS_WS is Kana-sensitive and
Width-sensitive. The Latin1_General_CI_AS is much more common, because
it's the default in most installations.
"Kana-sensitive" means that it distinguishes between the two types of
Japanese kana characters: Hiragana and Katakana. If this option is not
selected, SQL Server considers Hiragana and Katakana characters to be
equal for sorting purposes.
"Width-sensitive" means that it distinguishes between a single-byte
character and the same character when represented as a double-byte
character. If this option is not selected, SQL Server considers the
single-byte and double-byte representation of the same character to be
identical for sorting purposes. In this context, double-byte characters
does not reffer to Unicode characters in general. It reffers to
Double-Byte Character Sets, such as Shift-JIS, GB2312, etc.
--
Razvan Socol
SQL Server MVP