7019787: Why Do The Setup Instructions For MS SQL Server Call For Latin1 Instead of UTF-8 As The Rest Of The Document Requires

This document (7019787) is provided subject to the disclaimer at the end of this document.


Retain 3.x

MS SQL Server


Why do the setup instructions for MS SQL Server call for Latin1 instead of UTF-8 as the rest of the setup document requires?


MS SQL Server does not have an option for UTF-8, directly. However it does support Unicode character encoding with its own implementation of UTF-16 called Latin1_General_CI_AS, which is MS SQL Server’s default encoding of Unicode. The CI indicates that the encoding is case insensitive. The AS indicates that the encoding is accent sensitive.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2426.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


Leave a Reply