Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The topics in this section explain how to preserve the integrity of character data when you program client-side database applications.
In This Section
| Topic | Description |
|---|---|
Explains the implications of preserving character data integrity when neither the server nor the client is Unicode-aware. |
|
Managing Data Conversion Between a Unicode Server and a Non-Unicode Client |
Explains how to preserve character data integrity when server-side data storage is in Unicode, but the client-side application uses a specific code page. |
Explains how to preserve character data integrity when both the server and client are Unicode-enabled, but the encoding scheme used to process Unicode on the client differs from the UCS-2 scheme used by SQL Server 2005. |