Collation problem

Personally I would do a Cyrillic_General_CI_AS to Unicode,
then Unicode to the english translastion.
I would make up a new database with all your char, varchar
and text set to nchar, nvarchar and ntext then copy it
over using DTS.
Then you use the data in the new table to copy over to the
english collation.
Warning though with Unicode, it takes double the space, so
the maximum you can have is 4000 characters as opposed to
8000, so check the maximum sizes before you do it.
Peter
"Age is an issue of mind over matter. If you don't mind,
it doesn't matter."
Mark Twain

>--Original Message--
>Hi,
>I have database in russia with collation:
>Cyrillic_General_CI_AS
>Now I would like to transport data to English database
with english
>collation.
>I would like to convert cyrillic text to latin text, that
can be rad from
>english program.
>What is the best way to do that?
>Thank you,
>Simon
>
>.
>Hi, Peter
I don't want to copy cyrilic text into my database - so, I don't need
nvarchar data type.
I would like to convert cyrlic to latin and then insert into varchar type.
So, that is some kind of translation of data.
Do you have any idea?
lp,S
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:5a0c01c523d0$b46eb0d0$a401280a@.phx.gbl...
> Personally I would do a Cyrillic_General_CI_AS to Unicode,
> then Unicode to the english translastion.
> I would make up a new database with all your char, varchar
> and text set to nchar, nvarchar and ntext then copy it
> over using DTS.
> Then you use the data in the new table to copy over to the
> english collation.
> Warning though with Unicode, it takes double the space, so
> the maximum you can have is 4000 characters as opposed to
> 8000, so check the maximum sizes before you do it.
> Peter
> "Age is an issue of mind over matter. If you don't mind,
> it doesn't matter."
> Mark Twain
>
> with english
> can be rad from|||Hello,
The reason I sugested nchar, nvarchar and ntext is that it
is collation independant, basically its designed to what
you want in converting to different collations.
Have a look at 'Using Unicode Data' in BOL.
So the plan was to convert it into Unicode, then convert
than into Latin.
Your numbers should remain the same regardless of which
collation.
Peter
"There is no such thing as public opinion. There is only
published opinion."
Winston Churchill

>--Original Message--
>Hi, Peter
>I don't want to copy cyrilic text into my database - so,
I don't need
>nvarchar data type.
>I would like to convert cyrlic to latin and then insert
into varchar type.
>So, that is some kind of translation of data.
>Do you have any idea?
>lp,S
>"Peter The Spate" <anonymous@.discussions.microsoft.com>
wrote in message
>news:5a0c01c523d0$b46eb0d0$a401280a@.phx.gbl...
Unicode,
varchar
the
so
to
that
>
>.
>|||Hi Peter,
for example.
In russian database I have something like this:
-'
Now I would like to convert it to latin:
4y mozhete vy chytatypo-ukrayins'ky?
I won't have nVarchar type.
I would like to read from russian database and than convert it to latin (or
to unicode first like you suggest) and than insert into english database as
latin text into varchar column (I don't need nVarchar here because now I
have text in latin.)
But which function converts the text from cyrilic to unicode and than to
latin?
Regards,
Simon
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:5a4301c523d8$ea562770$a401280a@.phx.gbl...
> Hello,
> The reason I sugested nchar, nvarchar and ntext is that it
> is collation independant, basically its designed to what
> you want in converting to different collations.
> Have a look at 'Using Unicode Data' in BOL.
> So the plan was to convert it into Unicode, then convert
> than into Latin.
> Your numbers should remain the same regardless of which
> collation.
> Peter
> "There is no such thing as public opinion. There is only
> published opinion."
> Winston Churchill
>
>
> I don't need
> into varchar type.
> wrote in message
> Unicode,
> varchar
> the
> so
> to
> that