Skip to main content

Non-clustered index in SQL Server

Non-clustered index
A non-clustered index has a structure separate from data row, it means non-clustered order of the row does not match the physical order of the actual data. If we talk about the B-TREE structure, in the non-clustered index, the leaf pages of the index do not contain any actual data, but instead, contain pointers to the actual data. These pointers would point to the clustered index data page where the actual data exists (or the heap page if no clustered index exists on the table).

Non-clustered indexes (also called “indexes”) are the normal indexes that are created on your tables. SQL Server supports 999 non-clustered indexes per table.

Each non-clustered index can contain up to 1023 included columns. Columns of the TEXT, NTEXT and IMAGE data types cannot be included either.

There are more things that could be put in here, but this will get you a good start. If you think of anything that I’ve missed please feel free to post them below.

Benefits of non-clustered index
A non-clustered index on a table provides fast access to data. If a table has a non-clustered index then the index allows the database engine to locate data quickly without having to scan through the entire table.

How to create a non-clustered index
A non-clustered index can create as like clustered index created in the previous article. Please see the following script which will help you to create a no-clustered index.

-- Adding non-clustered index on a table Employee
dbo.Employee(EmpLastName ASC,EmpFirstName ASC);

CREATE INDEX IX_Employee_EmpFirstName ON dbo.Employee (EmpFirstName ASC);

Popular posts from this blog

Check for changes to an SQL Server table?

Problem: Suppose your team is working on the under-development project so it might be possible continuous work on the database and perform changes in Table, Stored procedure as per requirement, and daily you have to update the testing server database as per changes are done in developing server database then how it is possible to trace those changes. There are a lot of solutions for this problem which is listed below Solution 1: For SQL Server 2000, 2005 and above use the CHECKSUM command SELECTCHECKSUM_AGG(BINARY_CHECKSUM(*))FROMYour_Table_NameWITH (NOLOCK); That will return the same number each time its run as long as the table contents haven't changed. Unfortunately CHECKSUM does not work always properly to detect changes. It is only a primitive checksum and no CRC calculation. Therefore you can't use it to detect all changes, e. g. symmetrical changes result in the same CHECKSUM! Solution 2: 1.Run the following query. Before executing query replace DB_Name with your database name…

Merge and Merge join transformation in SSIS

How to drop multiple tables with common prefix in one query?

Problem: Suppose we have a situation where we need to drop those tables that have some prefixes string, so it is possible to drop those tables with a common prefix in a single query.
Solution: yes it is possible to drop all those tables that have the common prefix in a single query. Using following query you can delete all those tables that begin with a certain prefix string. In where condition just put the common prefix string in where condition (Like ‘prefix%’)
SELECT@query+=' DROP TABLE ' +QUOTENAME( +'.'+QUOTENAME(';' FROMsys.tablesASt INNERJOINsys.schemasASs ONt.[schema_id]=s.[schema_id] WHEREt.nameLIKE'MX_100%';
This query may create an issue, if a table has a foreign key relationship, you'll either need to drop them first or arrange the output to drop the tables in a certain order. If you want to monitor exactly what goes on when the query is running then use the following que…