Transact-SQL Syntax ConventionsSpecifies a set of options that can be applied to an index that is part of a constraint definition that is created by using ALTER TABLE.
Transact-SQL Syntax Conventions
{
PAD_INDEX = { ON | OFF }
| FILLFACTOR = fillfactor
| IGNORE_DUP_KEY = { ON | OFF }
| STATISTICS_NORECOMPUTE = { ON | OFF }
| ALLOW_ROW_LOCKS = { ON | OFF }
| ALLOW_PAGE_LOCKS = { ON | OFF }
| SORT_IN_TEMPDB = { ON | OFF }
| ONLINE = { ON | OFF }
| MAXDOP = max_degree_of_parallelism
| DATA_COMPRESSION = { NONE |ROW | PAGE | COLUMNSTORE | COLUMNSTORE_ARCHIVE }
[ ON PARTITIONS ( { <partition_number_expression> | <range> }
[ , ...n ] ) ]
| ONLINE = { ON [ ( <low_priority_lock_wait> ) ] | OFF }
}
<range> ::=
<partition_number_expression> TO <partition_number_expression>
<single_partition_rebuild__option> ::=
{
SORT_IN_TEMPDB = { ON | OFF }
| MAXDOP = max_degree_of_parallelism
| DATA_COMPRESSION = {NONE | ROW | PAGE | COLUMNSTORE | COLUMNSTORE_ARCHIVE } }
| ONLINE = { ON [ ( <low_priority_lock_wait> ) ] | OFF }
}
<low_priority_lock_wait>::=
{
WAIT_AT_LOW_PRIORITY ( MAX_DURATION = <time> [ MINUTES ] ,
ABORT_AFTER_WAIT = { NONE | SELF | BLOCKERS } )
} PAD_INDEX = { ON | OFF }
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies index padding. The default is OFF.
ON
The percentage of free space that is specified by FILLFACTOR is applied to the intermediate-level pages of the index.
OFF or fillfactor is not specified
The intermediate-level pages are filled to near capacity, leaving enough space for at least one row of the maximum size the index can have, given the set of keys on the intermediate pages.
FILLFACTOR =fillfactor
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies a percentage that indicates how full the Database Engine should make the leaf level of each index page during index creation or alteration. The value specified must be an integer value from 1 to 100. The default is 0.
[!NOTE]
Fill factor values 0 and 100 are identical in all respects.
IGNORE_DUP_KEY = { ON | OFF }
Specifies the response type when an insert operation attempts to insert duplicate key values into a unique index. The IGNORE_DUP_KEY option applies only to insert operations after the index is created or rebuilt. The option has no effect when executing CREATE INDEX, ALTER INDEX, or UPDATE. The default is OFF.
ON
A warning message occurs when duplicate key values are inserted into a unique index. Only the rows violating the uniqueness constraint fail.
OFF
An error message occurs when duplicate key values are inserted into a unique index. The entire INSERT operation is rolled back.
IGNORE_DUP_KEY cannot be set to ON for indexes created on a view, non-unique indexes, XML indexes, spatial indexes, and filtered indexes.
To view IGNORE_DUP_KEY, use sys.indexes.
In backward compatible syntax, WITH IGNORE_DUP_KEY is equivalent to WITH IGNORE_DUP_KEY = ON.
STATISTICS_NORECOMPUTE = { ON | OFF }
Specifies whether statistics are recomputed. The default is OFF.
ON
Out-of-date statistics are not automatically recomputed.
OFF
Automatic statistics updating are enabled.
ALLOW_ROW_LOCKS = { ON | OFF }
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies whether row locks are allowed. The default is ON.
ON
Row locks are allowed when accessing the index. The Database Engine determines when row locks are used.
OFF
Row locks are not used.
ALLOW_PAGE_LOCKS = { ON | OFF }
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies whether page locks are allowed. The default is ON.
ON
Page locks are allowed when accessing the index. The Database Engine determines when page locks are used.
OFF
Page locks are not used.
SORT_IN_TEMPDB = { ON | OFF }
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies whether to store sort results in tempdb. The default is OFF.
ON
The intermediate sort results that are used to build the index are stored in tempdb. This may reduce the time required to create an index if tempdb is on a different set of disks than the user database. However, this increases the amount of disk space that is used during the index build.
OFF
The intermediate sort results are stored in the same database as the index.
ONLINE = { ON | OFF }
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies whether underlying tables and associated indexes are available for queries and data modification during the index operation. The default is OFF. REBUILD can be performed as an ONLINE operation.
[!NOTE]
Unique nonclustered indexes cannot be created online. This includes indexes that are created due to a UNIQUE or PRIMARY KEY constraint.
ON
Long-term table locks are not held for the duration of the index operation. During the main phase of the index operation, only an Intent Share (IS) lock is held on the source table. This enables queries or updates to the underlying table and indexes to proceed. At the start of the operation, a Shared (S) lock is held on the source object for a very short period of time. At the end of the operation, for a short period of time, an S (Shared) lock is acquired on the source if a nonclustered index is being created; or an SCH-M (Schema Modification) lock is acquired when a clustered index is created or dropped online and when a clustered or nonclustered index is being rebuilt. Although the online index locks are short metadata locks, especially the Sch-M lock must wait for all blocking transactions to be completed on this table. During the wait time the Sch-M lock blocks all other transactions that wait behind this lock when accessing the same table. ONLINE cannot be set to ON when an index is being created on a local temporary table.
[!NOTE]
Online index rebuild can set the low_priority_lock_wait options described later in this section. low_priority_lock_wait manages S and Sch-M lock priority during online index rebuild.
OFF
Table locks are applied for the duration of the index operation. This prevents all user access to the underlying table for the duration of the operation. An offline index operation that creates, rebuilds, or drops a clustered index, or rebuilds or drops a nonclustered index, acquires a Schema modification (Sch-M) lock on the table. This prevents all user access to the underlying table for the duration of the operation. An offline index operation that creates a nonclustered index acquires a Shared (S) lock on the table. This prevents updates to the underlying table but allows read operations, such as SELECT statements.
For more information, see How Online Index Operations Work.
[!NOTE]
Online index operations are not available in every edition of Microsoft ssNoVersion]. For a list of features that are supported by the editions of Microsoft SQL Server see Features Supported by the Editions of SQL Server 2016.
MAXDOP =max_degree_of_parallelism
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Overrides the max degree of parallelism configuration option for the duration of the index operation. For more information, see Configure the max degree of parallelism Server Configuration Option. Use MAXDOP to limit the number of processors used in a parallel plan execution. The maximum is 64 processors.
max_degree_of_parallelism can be:
For more information, see Configure Parallel Index Operations.
[!NOTE]
Parallel index operations are not available in every edition of Microsoft ssNoVersion]. For a list of features that are supported by the editions of Microsoft SQL Server see Features Supported by the Editions of SQL Server 2016.
DATA_COMPRESSION
Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies the data compression option for the specified table, partition number, or range of partitions. The options are as follows:
NONE
Table or specified partitions are not compressed. Applies only to rowstore tables; does not apply to columnstore tables.
ROW
Table or specified partitions are compressed by using row compression. Applies only to rowstore tables; does not apply to columnstore tables.
PAGE
Table or specified partitions are compressed by using page compression. Applies only to rowstore tables; does not apply to columnstore tables.
COLUMNSTORE
Applies to: SQL Server 2014 (12.x) through SQL Server 2014 (12.x) SQL Server 2017
Applies only to columnstore tables. COLUMNSTORE specifies to decompress a partition that was compressed with the COLUMNSTORE_ARCHIVE option. When the data is restored, the COLUMNSTORE index continues to be compressed with the columnstore compression that is used for all columnstore tables.
COLUMNSTORE_ARCHIVE
Applies to: SQL Server 2014 (12.x) through SQL Server 2014 (12.x) SQL Server 2017
Applies only to columnstore tables, which are tables stored with a clustered columnstore index. COLUMNSTORE_ARCHIVE further compresses the specified partition to a smaller size. This can be used for archival, or for other situations that require less storage and can afford more time for storage and retrieval
For more information about compression, see Data Compression.
ON PARTITIONS ( { <partition_number_expression> | <range> } [ ,…n ] ) Applies to: SQL Server 2008 through SQL Server 2008 SQL Server 2017
Specifies the partitions to which the DATA_COMPRESSION setting applies. If the table is not partitioned, the ON PARTITIONS argument generates an error. If the ON PARTITIONS clause is not provided, the DATA_COMPRESSION option applies to all partitions of a partitioned table.
<partition_number_expression> can be specified in the following ways:
<range> can be specified as partition numbers separated by the word TO, for example: ON PARTITIONS (6 TO 8).
To set different types of data compression for different partitions, specify the DATA_COMPRESSION option more than once, for example:
--For rowstore tables
REBUILD WITH
(
DATA_COMPRESSION = NONE ON PARTITIONS (1),
DATA_COMPRESSION = ROW ON PARTITIONS (2, 4, 6 TO 8),
DATA_COMPRESSION = PAGE ON PARTITIONS (3, 5)
)
--For columnstore tables
REBUILD WITH
(
DATA_COMPRESSION = COLUMNSTORE ON PARTITIONS (1, 3, 5),
DATA_COMPRESSION = COLUMNSTORE_ARCHIVE ON PARTITIONS (2, 4, 6 TO 8)
) <single_partition_rebuild__option>
In most cases, rebuilding an index rebuilds all partitions of a partitioned index. The following options, when applied to a single partition, do not rebuild all partitions.
low_priority_lock_wait
Applies to: SQL Server 2014 (12.x) through SQL Server 2014 (12.x) SQL Server 2017
A SWITCH or online index rebuild completes as soon as there are no blocking operations for this table. WAIT_AT_LOW_PRIORITY indicates that if the SWITCH or online index rebuild operation cannot be completed immediately, it waits. The operation holds low priority locks, allowing other operations that hold locks conflicting with the DDL statement to proceed. Omitting the WAIT AT LOW PRIORITY option is equivalent to WAIT_AT_LOW_PRIORITY ( MAX_DURATION = 0 minutes, ABORT_AFTER_WAIT = NONE).
MAX_DURATION = time [MINUTES ]
The wait time (an integer value specified in minutes) that the SWITCH or online index rebuild lock that must be acquired, waits when executing the DDL command. The SWITCH or online index rebuild operation attempts to complete immediately. If the operation is blocked for the MAX_DURATION time, one of the ABORT_AFTER_WAIT actions is executed. MAX_DURATION time is always in minutes, and the word MINUTES can be omitted.
ABORT_AFTER_WAIT = [NONE | SELF | BLOCKERS } ]
NONE
Continues the SWITCH or online index rebuild operation without changing the lock priority (using regular priority).
SELF
Exits the SWITCH or online index rebuild DDL operation currently being executed without taking any action.
BLOCKERS
Kills all user transactions that block currently the SWITCH or online index rebuild DDL operation so that the operation can continue.
BLOCKERS requires the ALTER ANY CONNECTION permission.
For a complete description of index options, see CREATE INDEX (Transact-SQL).
ALTER TABLE (Transact-SQL)
column_constraint (Transact-SQL)
computed_column_definition (Transact-SQL)
table_constraint (Transact-SQL)