Re: cluster index and identity

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Andrew D. Newbould (newsgroups_at_NOzadSPANsoft.com)
Date: 11/26/04


Date: Fri, 26 Nov 2004 14:35:52 +0000

In message <2unifgF2c9ng0U1@uni-berlin.de>, rkusenet
<rkusenet@sympatico.ca> writes
>According to Brian Knight in "SQL Server 2000 for Experienced DBAs",
>
>"Avoid creating clustered indexes on identity columns.
> Clustered indexes perform better on range queries,
> such as a date. When you have a clustered index on
> an identity column, you risk your data receiving hot
> spots, which are caused by many people updating the
> same data page."
>
>I would like to know what is the consenus in this forum on this.
>

It really depends on your requirements and usage.

In an OLAP environment I would agree with his comment however in an OLTP
environment this would cause performance issues on large tables. What is
worse is you increase the risk of index fragmentation and therefore
require more frequent rebuilds.

If the table is used for linking purposes in an OLTP environment with
few inserts then again his statement would hold true.

It all depends ...

Kind Regards,

-- 
Andrew D. Newbould                  E-Mail:  newsgroups@NOSPAMzadsoft.com
ZAD Software Systems                Web   :  www.zadsoft.com


Relevant Pages

  • cluster index and identity
    ... "Avoid creating clustered indexes on identity columns. ... Clustered indexes perform better on range queries, ... you risk your data receiving hot ...
    (microsoft.public.sqlserver.server)
  • Re: cluster index and identity
    ... > "Avoid creating clustered indexes on identity columns. ... you risk your data receiving hot ...
    (microsoft.public.sqlserver.server)