| title | UTF-16 Support |
|---|---|
| description | Learn about support for UTF-16 in a fixed-length buffer in SQL Server Native Client, beginning with SQL Server 2012. |
| ms.custom | |
| ms.date | 03/14/2017 |
| ms.prod | sql |
| ms.reviewer | |
| ms.technology | native-client |
| ms.topic | reference |
| ms.assetid | f2520424-8ef4-409f-8147-d83da5076e96 |
| author | markingmyname |
| ms.author | maghan |
| monikerRange | >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDE SQL Server]
Beginning in [!INCLUDEssSQL11], if you supply a fixed-length buffer when binding a column result or output parameter and if the wchar character written into the buffer before the terminating character is a high surrogate code point of a surrogate pair, and if the next wchar character is a low surrogate code point, [!INCLUDEssNoVersion] Native Client will not add the high surrogate code point to the buffer.