September 2, 2002 at 10:47 am
Hi - I got this support issue in from a user of AdminLog for SQL. It relates to some SQL Issues that I don't know anything about - namely code page translations. Might be good grist for your discussion forums.
=====================================
I have a number of Databases (23) on my production Server W2K AS with SQL2K
EE, the Server is configured for the following Collation Settings:-
SQL_Latin1_General_CP850_CI_AI
Latin1-General, case-insensitive, accent-insensitive, kanatype-insensitive,
width-insensitive for Unicode Data,
SQL Server Sort Order 44 on Code Page 850 for non-Unicode Data
I recieve the error as listed below when attempting to write Text
information into the Database
"Code page translations are not supported for the text data type. From: 1252 To: 850."
I will not be able to change the CodePage for the Overall server, but if
needed can change the CodePage of the AdminLog DB using the COLLATE setting
when creating that Database, however this is a limitation and would prefer to keep the CodePage @ 850 and not use 1252 if possible.
Brian Lockwood
President
LockwoodTech Software
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
September 3, 2002 at 4:09 am
Is there a particular reason you app cannot support alternate code pages. The reason for your error is the difference in the character set availble in those code pages. I believe if I remember corretly that 1252 is the American standard set and 850 the last 100+ characters are changed to a set compatible with Western European countries. So why not just fix so your app supports whatever code page is defined for server default?
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
September 3, 2002 at 6:45 am
quote:
Is there a particular reason you app cannot support alternate code pages. The reason for your error is the difference in the character set availble in those code pages. I believe if I remember corretly that 1252 is the American standard set and 850 the last 100+ characters are changed to a set compatible with Western European countries. So why not just fix so your app supports whatever code page is defined for server default?"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
let me find this out. thanks for reply.
Brian Lockwood
President
LockwoodTech Software
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
September 3, 2002 at 8:21 am
more info from user who has solved his issue:
"I have Found the answer (well it works for me)
I'm using the Unicode nchar, nvarchar, and ntext data types instead of the
char, varchar, text data types.
and have updated the Ins Sprocs to use these as well"
Brian Lockwood
President
LockwoodTech Software
Brian Lockwood
President
ApexSQL - SQL Developer Essentials
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply