SQL Server; change all "VARCHAR" columns to "NVARCHAR"

Existing finPOWER Connect SQL Server databases do not support Unicode characters. This is because text columns were stored as Varchar and not NVarchar.

Without Unicode support special characters like the e in Café are saved as their non-diacritical equivalent, i.e. Cafe. In New Zealand this is especially notable when using Maori names.

• All new Databases will use NVarchar text columns.

• During the upgrade to version 3.2, existing SQL Server and Azure databases will be partially upgraded to use NVarchar.

• A special process is necessary to fully convert your database, found under Tools, Database, Upgrade Database to Unicode.
• We only recommend you complete this action if you require unicode characters.
• It may take a long time to complete and increase the size of your database by 50 to 150%.
• It may also require additional temporary disk space of 4x the size of your current database.
• Therefore, you should carefully consider whether it is right for you, and if so, plan when is best to undertake.

Unicode characters require 2 bytes of storage, where non-Unicode characters require 1 byte. This mean all text columns double in size.

In addition, performance may be affected, however in our testing this was negligible.

Note, Access databases already support Unicode.