You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `hardware offload enabled` configuration option allows integrated offloading and acceleration with validated solutions from partners. For more information, see [Integrated offloading and acceleration](../../relational-databases/integrated-acceleration/overview.md).
24
+
25
+
This is an advanced option.
26
+
27
+
Changing option requires a restart.
28
+
29
+
## Example
30
+
31
+
Set the server configuration option `hardware offload enabled` to `1`. By default, this setting is `0`. This setting is an advanced configuration option. To set this setting, run the following commands:
32
+
33
+
```sql
34
+
sp_configure 'show advanced options', 1
35
+
GO
36
+
RECONFIGURE
37
+
GO
38
+
sp_configure 'hardware offload enabled', 1
39
+
GO
40
+
RECONFIGURE
41
+
GO
42
+
```
43
+
44
+
> [!NOTE]
45
+
> If `hardware offload enabled` is disabled (`0`), all offloading and acceleration solutions are disabled.
Copy file name to clipboardExpand all lines: docs/relational-databases/backup-restore/backup-compression-sql-server.md
+20-14Lines changed: 20 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
-
title: "Backup Compression (SQL Server) | Microsoft Docs"
2
+
title: "Backup compression (SQL Server) | Microsoft Docs"
3
3
description: Learn about compression of SQL Server backups, including restrictions, performance trade-offs, Configuring backup compression, and the compression ratio.
This topic describes the compression of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backups, including restrictions, performance trade-off of compressing backups, the configuration of backup compression, and the compression ratio. Backup compression is supported on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] editions: Enterprise, Standard, and Developer. Every edition of [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later can restore a compressed backup.
This article describes the compression of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backups, including restrictions, performance trade-off of compressing backups, the configuration of backup compression, and the compression ratio. Backup compression is supported on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] editions: Enterprise, Standard, and Developer. Every edition of [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later can restore a compressed backup.
25
26
26
27
27
28
## <aname="Benefits"></a> Benefits
28
29
29
30
- Because a compressed backup is smaller than an uncompressed backup of the same data, compressing a backup typically requires less device I/O and therefore usually increases backup speed significantly.
30
31
31
-
For more information, see [Performance Impact of Compressing Backups](#PerfImpact), later in this topic.
32
+
For more information, see [Performance Impact of Compressing Backups](#PerfImpact), later in this article.
32
33
33
34
34
35
## <aname="Restrictions"></a> Restrictions
36
+
35
37
The following restrictions apply to compressed backups:
36
38
37
39
- Compressed and uncompressed backups cannot co-exist in a media set.
@@ -41,10 +43,13 @@ ms.author: mathoma
41
43
- NTbackups cannot share a tape with compressed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backups.
42
44
43
45
44
-
## <aname="PerfImpact"></a> Performance Impact of Compressing Backups
45
-
By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely impact concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by[Resource Governor](../../relational-databases/resource-governor/resource-governor.md). For more information, see [Use Resource Governor to Limit CPU Usage by Backup Compression (Transact-SQL)](../../relational-databases/backup-restore/use-resource-governor-to-limit-cpu-usage-by-backup-compression-transact-sql.md).
46
+
## <aname="PerfImpact"></a> Performance impact of compressing backups
47
+
48
+
By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely impact concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by [Resource Governor](../../relational-databases/resource-governor/resource-governor.md). For more information, see [Use Resource Governor to Limit CPU Usage by Backup Compression (Transact-SQL)](../../relational-databases/backup-restore/use-resource-governor-to-limit-cpu-usage-by-backup-compression-transact-sql.md).
49
+
50
+
Beginning with [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], you can use [Integrated offloading & acceleration](../integrated-acceleration/overview.md) to compress backups and offload the CPU resources for the backup.
46
51
47
-
To obtain a good picture of your backup I/O performance, you can isolate the backup I/O to or from devices by evaluating the following sorts of performance counters:
52
+
To obtain a good picture of your backup I/O performance, you can isolate the backup I/O to or from devices by evaluating the following sorts of performance counters:
48
53
49
54
- Windows I/O performance counters, such as the physical-disk counters
50
55
@@ -55,7 +60,7 @@ ms.author: mathoma
55
60
For information about Windows counters, see Windows help. For information about how to work with SQL Server counters, see [Use SQL Server Objects](../../relational-databases/performance-monitor/use-sql-server-objects.md).
56
61
57
62
58
-
## <aname="CompressionRatio"></a> Calculate the Compression Ratio of a Compressed Backup
63
+
## <aname="CompressionRatio"></a> Calculate the compression ratio of a compressed backup
59
64
To calculate the compression ratio of a backup, use the values for the backup in the **backup_size** and **compressed_backup_size** columns of the [backupset](../../relational-databases/system-tables/backupset-transact-sql.md) history table, as follows:
60
65
61
66
**backup_size**:**compressed_backup_size**
@@ -94,12 +99,13 @@ Starting with [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)] CU5, set
94
99
95
100
For more information, see [BACKUP (Transact-SQL)](../../t-sql/statements/backup-transact-sql.md).
96
101
97
-
## <aname="Allocation"></a> Allocation of Space for the Backup File
102
+
## <aname="Allocation"></a> Allocation of space for the backup file
103
+
98
104
For compressed backups, the size of the final backup file depends on how compressible the data is, and this is unknown before the backup operation finishes. Therefore, by default, when backing up a database using compression, the Database Engine uses a pre-allocation algorithm for the backup file. This algorithm pre-allocates a predefined percentage of the size of the database for the backup file. If more space is needed during the backup operation, the Database Engine grows the file. If the final size is less than the allocated space, at the end of the backup operation, the Database Engine shrinks the file to the actual final size of the backup.
99
105
100
106
To allow the backup file to grow only as needed to reach its final size, use trace flag 3042. Trace flag 3042 causes the backup operation to bypass the default backup compression pre-allocation algorithm. This trace flag is useful if you need to save on space by allocating only the actual size required for the compressed backup. However, using this trace flag might cause a slight performance penalty (a possible increase in the duration of the backup operation).
At installation, backup compression is off by default. The default behavior for backup compression is defined by the **backup compression default** Option server-level configuration option. However, you can override the server-level default when creating a single backup or scheduling a series of routine backups. To change the server-level default, see [View or Configure the backup compression default Server Configuration Option](../../database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option.md).
18
+
19
+
## Use integrated acceleration and offloading
20
+
21
+
Beginning with [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], use [Integrated offloading and acceleration](../integrated-acceleration/overview.md) to compress backups with Intel QuickAssist Technology.
18
22
19
23
## Override the Backup Compression Default
20
24
You can change the backup compression behavior for an individual backup, backup job, or log shipping configuration.
0 commit comments