Tạo index trong sql server

  -  

In this article

Applies to:

*
SQL vps (all supported versions)
*
Azure SQL Database
*
Azure SQL Managed Instance
*
Azure Synapse Analytics
*
Analytics Platform System (PDW)

Creates a relational index on a table or view. Also called a rowstore index because it is either a clustered or nonclustered B-tree index. You can create a rowstore index before there is data in the table. Use a rowstore index to improve query performance, especially when the queries select from specific columns or require values to be sorted in a particular order.

Bạn đang xem: Tạo index trong sql server


Note

SQL vps documentation uses the term B-tree generally in reference khổng lồ indexes. In rowstore indexes, SQL server implements a B+ tree. This does not apply to lớn columnstore indexes or in-memory data stores. Review SQL server Index Architecture and Design Guide for details.


Azure Synapse Analytics và Analytics Platform System (PDW) currently don"t support unique constraints. Any examples referencing quality constraints are only applicable to lớn SQL Server và SQL Database.

For information on index thiết kế guidelines, refer to lớn the SQL vps Index kiến thiết Guide.

Examples:

Create a nonclustered index on a table or view

CREATE INDEX index1 ON schema1.table1 (column1);Create a clustered index on a table và use a 3-part name for the table

CREATE CLUSTERED INDEX index1 ON database1.schema1.table1 (column1);Create a nonclustered index with a quality constraint and specify the sort order

CREATE unique INDEX index1 ON schema1.table1 (column1 DESC, column2 ASC, column3 DESC);Key scenario:

Starting with SQL Server 2016 (13.x) & SQL Database, you can use a nonclustered index on a columnstore index to improve data warehousing query performance. For more information, see Columnstore Indexes - Data Warehouse.

For additional types of indexes, see:

*
Transact-SQL Syntax Conventions

Syntax

Syntax for SQL Server, Azure SQL Database, Azure SQL Managed Instance

CREATE < chất lượng > < CLUSTERED | NONCLUSTERED > INDEX index_name ON ( column < ASC | DESC > < ,...n > ) < INCLUDE ( column_name < ,...n > ) > < WHERE > < WITH ( < ,...n > ) > < ON partition_scheme_name ( column_name ) > < FILESTREAM_ON "NULL" >< ; > ::= database_name.schema_name.table_or_view_name ::= OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF ::= < & > < ...n > ::= | ::= column_name IN (constant ,...n) ::= column_name constant ::= { IS | IS NOT | = | | != | > | >= | !> | ::= WAIT_AT_LOW_PRIORITY ( MAX_DURATION = < MINUTES > , ABORT_AFTER_WAIT = SELF ) ::= lớn

Backward compatible relational index


Important

The backward compatible relational index syntax structure will be removed in a future version of SQL Server.Avoid using this syntax structure in new development work, and plan to modify applications that currently use the feature.Use the syntax structure specified in instead.


CREATE < unique > < CLUSTERED | NONCLUSTERED > INDEX index_name ON ( column_name < ASC | DESC > < ,...n > ) < WITH < ,...n > > < ON "default" > ::= < database_name. < owner_name > . ::= STATISTICS_NORECOMPUTE

Syntax for Azure Synapse Analytics and Parallel Data Warehouse

CREATE CLUSTERED COLUMNSTORE INDEX index_name ON < database_name . < schema > . | schema . > table_name )> <;>CREATE < CLUSTERED | NONCLUSTERED > INDEX index_name ON < database_name . < schema > . | schema . > table_name ( column < ASC < ,...n > ) WITH ( DROP_EXISTING = OFF )<;>
Note

To view Transact-SQL syntax for SQL Server năm trước and earlier, see Previous versions documentation.


Arguments

UNIQUE

Creates a unique index on a table or view. A chất lượng index is one in which no two rows are permitted khổng lồ have the same index key value. A clustered index on a view must be unique.

The Database Engine doesn"t allow creating a chất lượng index on columns that already include duplicate values, whether or not IGNORE_DUP_KEY is set to ON. If this is tried, the Database Engine displays an error message. Duplicate values must be removed before a unique index can be created on the column or columns. Columns that are used in a quality index should be set to NOT NULL, because multiple null values are considered duplicates when a chất lượng index is created.

CLUSTERED

Creates an index in which the logical order of the key values determines the physical order of the corresponding rows in a table. The bottom, or leaf, màn chơi of the clustered index contains the actual data rows of the table. A table or view is allowed one clustered index at a time.

A view with a unique clustered index is called an indexed view. Creating a unique clustered index on a view physically materializes the view. A chất lượng clustered index must be created on a view before any other indexes can be defined on the same view. For more information, see Create Indexed Views.

Create the clustered index before creating any nonclustered indexes. Existing nonclustered indexes on tables are rebuilt when a clustered index is created.

If CLUSTERED isn"t specified, a nonclustered index is created.


Note

Because the leaf cấp độ of a clustered index and the data pages are the same by definition, creating a clustered index và using the ON partition_scheme_name or ON filegroup_name clause effectively moves a table from the filegroup on which the table was created to the new partition scheme or filegroup. Before creating tables or indexes on specific filegroups, verify which filegroups are available & that they have enough empty space for the index.


In some cases creating a clustered index can enable previously disabled indexes. For more information, see Enable Indexes & Constraints and Disable Indexes và Constraints.

NONCLUSTERED

Creates an index that specifies the logical ordering of a table. With a nonclustered index, the physical order of the data rows is independent of their indexed order.

Each table can have up lớn 999 nonclustered indexes, regardless of how the indexes are created: either implicitly with PRIMARY KEY & UNIQUE constraints, or explicitly with CREATE INDEX.

Xem thêm: Quy Luật Lượng Và Chất Cái Gì Biến Đổi Trước, Quy Luật Lượng

For indexed views, nonclustered indexes can be created only on a view that has a chất lượng clustered index already defined.

If not otherwise specified, the mặc định index type is nonclustered.

index_name

The name of the index. Index names must be chất lượng within a table or view, but don"t have to lớn be chất lượng within a database. Index names must follow the rules of identifiers.

column

The column or columns on which the index is based. Specify two or more column names lớn create a composite index on the combined values in the specified columns. List the columns to lớn be included in the composite index, in sort-priority order, inside the parentheses after table_or_view_name.

Up khổng lồ 32 columns can be combined into a single composite index key. All the columns in a composite index key must be in the same table or view. The maximum allowable kích thước of the combined index values is 900 bytes for a clustered index, or 1,700 for a nonclustered index. The limits are 16 columns and 900 bytes for versions before SQL Database & SQL Server năm nhâm thìn (13.x).

Columns that are of the large object (LOB) data types ntext, text, varchar(max), nvarchar(max), varbinary(max), xml, or image can"t be specified as key columns for an index. Also, a view definition can"t include ntext, text, or image columns, even if they are not referenced in the CREATE INDEX statement.

You can create indexes on CLR user-defined type columns if the type supports binary ordering. You can also create indexes on computed columns that are defined as method invocations off a user-defined type column, as long as the methods are marked deterministic and don"t perform data access operations. For more information about indexing CLR user-defined type columns, see CLR User-defined Types.

< ASC | DESC >

Determines the ascending or descending sort direction for the particular index column. The default is ASC.

INCLUDE (column < ,... n > )

Specifies the non-key columns lớn be added to the leaf level of the nonclustered index. The nonclustered index can be quality or non-unique.

Column names can"t be repeated in the INCLUDE list & can"t be used simultaneously as both key and non-key columns. Nonclustered indexes always contain the clustered index columns if a clustered index is defined on the table. For more information, see Create Indexes with Included Columns.

All data types are allowed except text, ntext, and image. Starting with SQL vps 2012 (11.x) & Azure SQL Database, if any one of the specified non-key columns are varchar(max), nvarchar(max), or varbinary(max) data types, the index can be built or rebuilt using the ONLINE option.

Computed columns that are deterministic & either precise or imprecise can be included columns. Computed columns derived from image, ntext, text, varchar(max), nvarchar(max), varbinary(max), and xml data types can be included in non-key columns as long as the computed column data types is allowable as an included column. For more information, see Indexes on Computed Columns.

For information on creating an XML index, see CREATE XML INDEX.

WHERE

Creates a filtered index by specifying which rows lớn include in the index. The filtered index must be a nonclustered index on a table. Creates filtered statistics for the data rows in the filtered index.

The filter predicate uses simple comparison súc tích and can"t reference a computed column, a UDT column, a spatial data type column, or a hierarchyID data type column. Comparisons using NULL literals are not allowed with the comparison operators. Use the IS NULL & IS NOT NULL operators instead.

Here are some examples of filter predicates for the Production.BillOfMaterials table:

WHERE StartDate > "20000101" and EndDate Filtered indexes don"t apply khổng lồ XML indexes and full-text indexes. For quality indexes, only the selected rows must have quality index values. Filtered indexes don"t allow the IGNORE_DUP_KEY option.

Xem thêm: Công Xã Paris Tồn Tại Trong Bao Nhiêu Ngày ? Please Wait

ON partition_scheme_name ( column_name )

Specifies the partition scheme that defines the filegroups onto which the partitions of a partitioned index will be mapped. The partition scheme must exist within the database by executing either CREATE PARTITION SCHEME or ALTER PARTITION SCHEME. column_name specifies the column against which a partitioned index will be partitioned. This column must match the data type, length, and precision of the argument of the partition function that partition_scheme_name is using. column_name isn"t restricted to the columns in the index definition. Any column in the base table can be specified, except when partitioning a unique index, column_name must be chosen from among those used as the unique key. This restriction allows the Database Engine lớn verify uniqueness of key values within a single partition only.