collation, encoding, code page, locale, sorting, comparison, LCID, T-SQL, TSQL, SQL Server 2018-12-13 15-0
         Collations Info
       Home       Concepts       Answers       Reference       Microsoft Connect       Contact 
collation, encoding, code page, locale, sorting, comparison, LCID, T-SQL, TSQL, SQL Server
— Microsoft Connect —



Bugs
  1. BIN2 collations do not come through SqlCompareOptions of SqlString
  2. SSMS 17.3 IntelliSense does not recognize CATALOG_DEFAULT as a valid collation
  3. SSMS 17.3 IntelliSense collation-related validations do not adjust for Contained Databases
  4. SSMS 17.3 IntelliSense validates temporary stored procedures using case-sensitive comparison even on a case-insensitive instance
  5. Contained Databases use TempDB Collation for Temporary Stored Procedure names instead of CATALOG_DEFAULT
  6. UTF-8 in SQL 2019: NVARCHAR to VARCHAR(MAX) can get Msg 8152 "String or binary data would be truncated"   – Fixed
  7. UTF-8 in SQL 2019: Binary UTF-8 Collations are missing
  8. UTF-8 in SQL 2019: Invalid UTF-8 bytes get (Msg 682, Level 22, State 148) Internal error. Buffer provided to read column value is too small.   – Fixed
  9. UTF-8 in SQL 2019: Inconsistent handling of invalid UTF-8 byte sequences
  10. UTF-8 in SQL 2019: Collation Precedence allows for Unicode character data loss concatenating UTF8 with higher precedence non-UTF8 VARCHAR
  11. UTF-8 in SQL 2019: An error occurred while executing batch. Error message is: Internal connection fatal error. Error state: 15, Token : 0   – Fixed
  12. UTF-8 in SQL 2019: Install fails with "Could not find the Database Engine startup handle." if a Unicode-only Collation is selected
  13. UTF-8 in SQL 2019: Collation Precedence allows for silent truncation (data loss) implicitly converting Extended ASCII characters into UTF8



Copyright © 2017-2018 Solomon Rutzky. All rights reserved.
collation, encoding, code page, locale, sorting, comparison, LCID, T-SQL, TSQL, SQL Server 2018-12-13 15-0