Previous Topic

Book Contents

Book Index

Next Topic

MS SQL - Unicode Implementation Scenarios

New installations

Standard Valuemation database creation scripts create databases without Unicode support. The standard installation folder contains ready-to-use migration script which can be used to convert the database by changing the appropriate columns types.

The process for a new installation is:

  1. Install the standard database from scripts
  2. If Unicode is needed, execute the Unicode migration script included in the database installation folder (VM 4.4 and newer).

Existing Customers

Because an already existing installation most likely contains customer-specific columns and/or tables, it cannot be converted using a ready-to-use migration script. Instead, a customer-specific Unicode migration script needs to be created. The script is created by processing a series of SQL templates in the Valuemation Console.

The script created in this way can then be used to convert all appropriate columns in all appropriate tables in the database.

For detailed technical information on the migration script refer to the 'Unicode Support and Migration Procedure' document.

The process for an existing installation is:

  • If Unicode is needed, create a customer-specific Unicode migration script using the Valuemation Console._Note: USU offers creation of the customer-specific script. This can be done on site by a trained consultant or at USU supposing a new DB dump is provided (VM 4.3.HF28 and newer needed).

MS SQL Server – Hotfixes and upgrades

  • Hotfixes

    The database part of Valuemation hotfixes newly contains a Unicode version of SQL Server script where new char/varchar columns are replaced with nchar/nvarchar. Customers using an SQL Server with Unicode support must always use this Unicode version of SQL hotfix.

  • Upgrades

    A Unicode version of the upgrade script is also provided. Customers using an SQL Server with Unicode support must use the Unicode version of upgrade.

See Also

Databases Without Database Level Support

MS SQL - Index Length Limitations