I'm already quite comfortable with using COMPRESS()
and DECOMPRESS()
in an internal forum software for our company (Currently in SQL Server 2017), but trying to make the database as efficient as possible, is there an advantage to adding _UTF-8
to my current collation as in Latin1_General_100_CI_AS_SC_UTF8
upon future migration to SQL Server 2019?
SQL Server 2019 – Benefits of UTF-8 Support
collationencodingsql serverutf-8
Related Question
- Sql-server – SQL Server Memory Determination
- SQL Server – Migrating SQL Server 2008 Databases to WSFC SQL2014 AlwaysOn AG
- Sql-server – Can AWS Data Migration Service be used to integrate non AWS SQL server with Redshift
- Sql-server – Regular data transfer from SQL Server to MySQL
- How to Determine Default Collation and Server Version Without Full Restore in SQL Server
- Sql-server – Azure SQL Elastic Pools – When to Create a new one versus upping the eDTU
Best Answer
Here's a list of recommended uses taken from here:
The UTF-8 encoding, being a variable-length encoding, can be a huge benefit in some scenarios, but it can also make things worse in others. Unfortunately, there is very little use for a “_UTF8” encoding given that Data Compression and Clustered Columnstore Indexes are available across all editions of SQL Server. The only scenario that truly benefits from a UTF-8 encoding is one in which all of the following conditions are true:
Storing HTML pages is a good example of a scenario that fits this description. UTF-8 is, of course, the preferred encoding for the interwebs precisely due to it using the minimal space for the most common characters while still allowing for the full range of Unicode characters.