Re: SQLServer2k to Oracle 9i, Character Set Conflict

Hi Sybrand,
Thanks for your reply.

> WE8MSWIN1252, sorry. And as the new characterset is not a superset of
> the old, recreating the database is the only way.

Can I do just ALTER DATABASE CHARACTER SET WE8MSWIN1252;

There is nothing yet in the database except for Scott's data. What is the bad thing of doing just ALTER DATABASE ... instead of recreating the database ?

Thank you for your help,
Krist

Sybrand Bakker <sybrandb_at_hccnet.nl> wrote in message news:<bnsue0133a070bjsorql4es8v19h1834ro_at_4ax.com>...
> On 9 Jul 2004 20:42:27 -0700, xtanto_at_hotmail.com (Krist) wrote:
>
> >> MSWIN1252
> >Is it MSWIN1252 ot WE8MSWIN1252 ?
> >So what should I do with the oracle ? Is recreating the database is the only way ?
> >Can I just change the NLS_LANG in the client or in INIT.Ora ?
> >
> >On other table, SQL Server CHAR(50) must be changed to CHAR(100) in Oracle,
> >But in this column ALL are English standard character, No Special character.
> >is this also because of character set issue or other issue ?
> >
> >Thanks for your help,
> >Krist
>
>
> WE8MSWIN1252, sorry. And as the new characterset is not a superset of
> the old, recreating the database is the only way.
> The CHAR datatype in Oracle is *fixed* length. VARCHAR2 is variable
> length.
> As your characterset is not a 2-byte characterset is wouldn't know why
> you would want to double the length.
Received on Sat Jul 10 2004 - 06:40:19 CDT