OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Support <strong>for</strong> Unicode<br />
<strong>Data</strong>base design issues<br />
Enabling Unicode support in the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> provides the following<br />
functionality:<br />
• Completes the connection between UTF-8 support in the <strong>OpenEdge</strong> Advanced Business<br />
Language (ABL) client and UCS-2 support in MS <strong>SQL</strong> <strong>Server</strong><br />
• Allows Unicode data to be passed to and from MS <strong>SQL</strong> <strong>Server</strong> data sources<br />
• Provides a migration path <strong>for</strong> Unicode character data type definitions in ABL to MS <strong>SQL</strong><br />
<strong>Server</strong>, and vice versa<br />
The result is that <strong>OpenEdge</strong> <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> applications can be developed and<br />
deployed without significant language or country restrictions.<br />
For general Unicode in<strong>for</strong>mation, see <strong>OpenEdge</strong> Development: Internationalizing<br />
Applications.<br />
Unicode support in the <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong> is enabled while migrating an <strong>OpenEdge</strong><br />
database to MS <strong>SQL</strong> <strong>Server</strong>. For details see Chapter 7, “The <strong>Data</strong><strong>Server</strong> Tutorial.”<br />
Configuration requirements<br />
In order to use Unicode in the <strong>OpenEdge</strong> <strong>Data</strong><strong>Server</strong> <strong>for</strong> MS <strong>SQL</strong> <strong>Server</strong>, you must use<br />
<strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong> 2005 or later, and the <strong>Data</strong>Direct Connect ODBC driver <strong>for</strong> MS <strong>SQL</strong><br />
<strong>Server</strong>, Version 5.1 or later. Additionally, you must per<strong>for</strong>m the following prerequisite tasks:<br />
• Prepare your Unicode Schema Holder — If you create a new <strong>OpenEdge</strong> application to<br />
be Unicode-enabled <strong>for</strong> migration to an ORACLE <strong>Data</strong><strong>Server</strong>, ensure that you create the<br />
database from a Unicode source. A copy of the empty <strong>OpenEdge</strong> UTF-8 database can be<br />
obtained from $DLC/prolang/utf/empty. If you use the Create <strong>Data</strong><strong>Server</strong> Schema<br />
ORACLE <strong>Data</strong><strong>Server</strong> utility to create a <strong>Data</strong><strong>Server</strong> schema and you plan to set the schema<br />
holder’s code page to UTF-8, the schema holder must also be derived from a copy of the<br />
empty UTF-8 database located at $DLC/prolang/utf/empty.<br />
Note: The migration process derives a schema holder this way automatically if you set<br />
the code page of your migration to UTF-8.<br />
The following command creates an empty <strong>OpenEdge</strong> database named “empty” that can be<br />
used to describe a Unicode-enabled <strong>for</strong>eign data source:<br />
Prodb $DLC/prolong/utf/empty<br />
Note: The best way to ensure that the database path is correct <strong>for</strong> utilities that create a<br />
Unicode-enabled database is to set the $DLCDB environment variable to<br />
$DLC/prolong/utf. This ensures that databases will be constructed with Unicode<br />
enablement. If you do not set $DLCDB, you will need to reference the<br />
$DLC/prolong/utf directory explicitly whenever you want to create a<br />
Unicode-enabled database.<br />
2–9
Change language