Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bryan99y
Starting Member
42 Posts |
 Posted - 2002-04-11 : 11:17:21
|
| We are migrating a HelpDesk system(Remedy) from Oracle to SQL Sever 2000. 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 ? |
|
|
bryan99y
Starting Member
42 Posts |
Posted - 2002-04-12 : 09:53:22
|
| any ideas ??? |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-04-12 : 10:23:06
|
| It definitely won't affect your server -- as the name suggests, Client Netrwork Utility only affects client connectivity. As long as all of your applications use the same codepage, they will not be affected either. However, if you have applications that access the same data, but use different codepages, you may see some unexpected results when trying to manipulate the same piece of data from two different apps. The data may be sorted incorrectly, and/or could contain characters unavailable in the application's codepage. I am fairly sure the above information is accurate, but it is based strictly on my understanding of what this option does -- I have never needed to turn it off before...---------------Strong SQL Developer wanted in the Boston area. Please e-mail if interested.Edited by - izaltsman on 04/12/2002 10:25:34 |
|
|
|
bryan99y
Starting Member
42 Posts |
Posted - 2002-04-12 : 10:30:22
|
| Is there a Client Network Utility for EACH Instance on SQL Server 2000 Enterprise edition ?If this is the case I could set it at the Instance level. |
|
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-04-12 : 11:25:50
|
| DB-Library settings in the Client Network Utility will affect the way this client communicates to every instance of SQL Server.---------------Strong SQL Developer wanted in the Boston area. Please e-mail if interested. |
|
|
|
bryan99y
Starting Member
42 Posts |
Posted - 2002-04-12 : 12:47:21
|
| every Instance hey. I figured that."As long as all of your applications use the same codepage, they will not be affected either". Can you be specific here ? |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-04-12 : 13:38:03
|
| Code pages determine how bytes codes are interpreted by the computer. For example, capital A is ASCII byte code 65. Some code pages may treat 65 as a different character (they don't actually, 65 is capital A in all of them, but you get the idea) Some of the higher byte codes, like the accented characters, do not translate properly under different code pages (this is why unicode was developed, it uses 2 bytes for each character, and can represent every international character correctly, regardless of code page settings)Unless you are dealing with international characters that are NOT stored as unicode (nchar or nvarchar), you are probably safe from code page issues. |
|
|
|
|
|
|
|
|
Client Network Utility configuration