April 11, 2002 at 9:31 am
We are migrating a HelpDesk system(Remedy) from Oracle to SQL Sever. The Remedy Application only works when we change a setting in the Client Network Utility. We have to uncheck the "Automatic ANSI to OEM Conversion".
What affect will this have on the Server, Databases, other Applications ?
April 11, 2002 at 10:23 am
This question is better answered by Remedy but as far as I know it should not but as we use Oracle with out Remedy servers I have not had a chance to test and it will be a while before they get me a test server with Remedy/SQL.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 11, 2002 at 11:11 am
I was wonerding how this would affect SQL Server 2000 in general since the default is to have "Automatic ANSI to OEM Conversion" option checked/enabled.
April 11, 2002 at 11:47 am
Here this is from BOL and may explain what you are asking best.
Using the DB-Library Automatic ANSI to OEM Conversion Option
When enabled, the Automatic ANSI to OEM conversion option converts a character set when communicating from:
ANSI clients to OEM servers.
OEM clients to ANSI servers.
This option is enabled by default. When the option is disabled, conversion of characters is disabled for all connections.
If the client code page is different from the code page on the instance of SQL Server, then the character set should be converted. Microsoft Windows NT®, Microsoft Windows® 2000, Windows 95, and Windows 98 have both an ANSI and an OEM character set, which are set during installation. For U.S. English, Windows NT, Windows 2000, Windows 95, and Windows 98 use the default ANSI character set, code page 1252, and the default OEM character set, code page 437. Windows 3.x runs as an extension to MS-DOS, and has only the default ANSI character set of code page 1252. The Windows NT 4.0 and Windows 2000 Console is internally Unicode, which behaves like an OEM character set.
Any clients running Windows NT 4.0, Windows 2000, Windows 95, or Windows 98 are considered ANSI clients. Console-based applications, such as the isql utility, are considered OEM clients.
A server with the default code page of 12xx, such as 1252, is considered to be an ANSI server; with any other code page, it is considered to be an OEM server (for example, code page 850 or 437).
Although default code page values exist for both ANSI and OEM, the client's current operating system code page determines conversion values when characters are translated.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 12, 2002 at 8:18 am
read it.
But unsure how this will affect my SQL Server, other Apps.
April 12, 2002 at 8:47 am
Ok so the concern is that the clients other apps connecting to the same server may be adversly affected. But if I understand correctly, if all your clients are Windows U.S. English OS then all should be fine unless the other apps support another character set. If this is the case or the client are some other OEM install then you most likely will see failures. I suggest you test on one that fits the OEM category of using the nonANSI character sets.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply