ATG products do not support Unicode for MS SQL Server databases. To use Microsoft SQL Server with ATG products, be sure the useSetUnicodeStream property of all SQL repository components is set to false (default). To ensure that no ATG components are configured to use useSetUnicodeStream, you can set this property in your localconfig/ file:


If you are creating localized content, set the useSetAsciiStream property to false in your localconfig/ file:


If you are using the Microsoft SQL Server 2005 JDBC driver, you must set sendStringParametersAsUnicode to false in your URL connection string. For example:


The sendStringParametersAsUnicode=false setting avoids Unicode character conversion and enables MS SQL Server to use indexes in queries.

In addition, for better performance, turn READ_COMMITTED_SNAPSHOT on. For example:

Using iNet (Merlia) Drivers

If you are using iNet drivers on JBoss, bear in mind that this driver does not allow for passing information by URL; therefore, some additional information must be set in the property fields, as shown in this example:

  <xa-datasource-property name="ServerName">server_name</xa-datasource-property>
  <xa-datasource-property name="DatabaseName">database_name</xa-datasource-
  <xa-datasource-property name="User">database_username</xa-datasource-property>
  <xa-datasource-property name="Password">database_password</xa-datasource-
 <xa-datasource-property name="Mode">71</xa-datasource-property>
  <!-- sql to call when connection is created -->
  <new-connection-sql>select 1</new-connection-sql>
  <!-- sql to call on an existing pooled connection when it is obtained from
pool -->
  <check-valid-connection-sql>select 1</check-valid-connection-sql>

  <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml -->
    <type-mapping>MS SQLSERVER2000</type-mapping>

If you are using iNet drivers with WebLogic, when you create your data source, use the following settings:

loading table of contents...