By default, the MSSQL hibernate dialect creates char, varchar and text columns when defining a schema. These fields do not support Unicode characters. Instead, we need to user nchar, nvarchar and ntext columns.

What we want to do is create a hibernate dialect that can be used that creates the correct unicode column types.

----- Some background info:

In Microsoft SQL Server, these data types support Unicode data:

nchar

nvarchar

ntext

Note The n prefix for these data types comes from the SQL-92 standard for
National (Unicode) data types.

Use of nchar, nvarchar, and ntext is the same as char, varchar, and text,
respectively, except that:

Unicode supports a wider range of characters.

More space is needed to store Unicode characters.

The maximum size of nchar and nvarchar columns is 4,000 characters, not 8,000
characters like char and varchar.

Unicode constants are specified with a leading N: N'A Unicode string'.

All Unicode data uses the same Unicode code page. Collations do not control the
code page used for Unicode columns, only attributes such as comparison rules and
case sensitivity.
------------------------------