Geek Answers Handbook

SQL Server Clustered Indexes

I have an Oracle background, and using "indexed organized tables" (IOT) for each table sounds unreasonable in Oracle, and I have never seen this. In SQL Server, every database I worked on has a clustered index for each table, which is the same as IOT (conceptually).

Why? Is there any reason to use a clustered index worldwide? It seems to me that they would be good for only a few cases.

thank

+5
source share
4 answers

. , , , . , , , , .

, , , . , , , , , .

. , , uniqueidentifier, (. ).

, , , . , USERS, USER_ID, USER_ID . , .

, .

:

- varchar.

INT IDENTITY .

, .

UniqueIdentifiers

, . b- , . . , , - . , , , . , .

, , (, ).

+2

, . IOT IOT. SQL Server .

SQL Server, , . IOTs Oracle , , , .

, SQL Server pre 6.5 7.0 IIRC . , , . , SQL Server 6 , .

+6

, . , . ( , , !).

.

+1

We use Primary keys in relational databases and generally set these primary keys. Most people used the name of the first field as TableID and made it the primary key. When you join the other two tables in your query, you will get the fastest result if you use clustered indexes.

0
source

More articles:


All Articles