Skip to content

unicode-compression-implementation.md

Latest commit

 

History

History
61 lines (47 loc) · 4.02 KB

unicode-compression-implementation.md

File metadata and controls

61 lines (47 loc) · 4.02 KB
title Unicode Compression Implementation | Microsoft Docs
description SQL Server uses the Standard Compression Scheme for Unicode algorithm to compress Unicode values that are stored in row or page compressed objects.
ms.custom
ms.date 03/14/2017
ms.service sql
ms.reviewer
ms.subservice performance
ms.topic conceptual
helpviewer_keywords
Unicode data compression
compression [SQL Server], Unicode data
ms.assetid 44e69e60-9b35-43fe-b9c7-8cf34eaea62a
author WilliamDAssafMSFT
ms.author wiassaf
monikerRange =azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

Unicode Compression Implementation

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance]

[!INCLUDEssNoVersion] uses an implementation of the Standard Compression Scheme for Unicode (SCSU) algorithm to compress Unicode values that are stored in row or page compressed objects. For these compressed objects, Unicode compression is automatic for nchar(n) and nvarchar(n) columns. The [!INCLUDEssDE] stores Unicode data as 2 bytes, regardless of locale. This is known as UCS-2 encoding. For some locales, the implementation of SCSU compression in SQL Server can save up to 50 percent in storage space.

Supported Data Types

Unicode compression supports the fixed-length nchar(n) and nvarchar(n) data types. Data values that are stored off row or in nvarchar(max) columns are not compressed.

Note

Unicode compression is not supported for nvarchar(max) data even if it is stored in row. However, this data type can still benefit from page compression.

Upgrading from Earlier Versions of SQL Server

When a [!INCLUDEssNoVersion] database is upgraded to [!INCLUDEssnoversion], Unicode compression-related changes are not made to any database object, compressed or uncompressed. After the database is upgraded, objects are affected as follows:

  • If the object is not compressed, no changes are made and the object continues to function as it did previously.

  • Row- or page-compressed objects continue to function as they did previously. Uncompressed data remains in uncompressed form until its value is updated.

  • New rows that are inserted into a row- or page-compressed table are compressed using Unicode compression.

    [!NOTE]
    To take full advantage of the benefits of Unicode compression, the object must be rebuilt with page or row compression.

How Unicode Compression Affects Data Storage

When an index is created or rebuilt or when a value is changed in a table that was compressed with row or page compression, the affected index or value is stored compressed only if its compressed size is less than its current size. This prevents rows in a table or index from increasing in size because of Unicode compression.

The storage space that compression saves depends on the characteristics of the data that is being compressed and the locale of the data. The following table lists the space savings that can be achieved for several locales.

Locale Compression percent
English 50%
German 50%
Hindi 50%
Turkish 48%
Vietnamese 39%
Japanese 15%

See Also

Data Compression
sp_estimate_data_compression_savings (Transact-SQL)
Page Compression Implementation
sys.dm_db_persisted_sku_features (Transact-SQL)