SQLServerCentral / Discuss Content Posted by Christoffer Hedgate / Article Discussions / Article Discussions by Author / Cluster That Index! Part Two / Latest Posts

RE: Cluster That Index! Part Two

Vic Kirkpatrick — Thu, 12 Aug 2004 12:57:00 GMT

Depending (of course) on the business need. Here, we have plenty of tables in which we only query them via the identity column (PK). There are no columns that require searching through ranges of data on these tables, so in these cases Kyle's comment holds water.

RE: Cluster That Index! Part Two

chrismj — Thu, 12 Aug 2004 01:54:00 GMT

True, but that kind of defeats the purpose of the clustered index, as you are not likely to do searches on the ID, specially not range searches. You should cluster on other incrementing values that are carrying information, like creation date.

RE: Cluster That Index! Part Two

Chris Hedgate — Tue, 12 Aug 2003 12:26:00 GMT

quote:
Great Article. One addition comment about page splitting from your example. If your are worried about page slitting because of heavy inserts to a table put the clustered index on the identity column. Since the clustered index will be order by the data, if you put a clustered index on an identity column then the new row will be added to the end of the data pages and page splits won't occur.

Thanks Kyle, great comment. That should have been in the article as well, but I guess there'll be a part 3 some time. --Chris Hedgate @ Apptus Technologies (http://www.apptus.se)http://www.sql.nu

RE: Cluster That Index! Part Two

Chris Hedgate — Tue, 12 Aug 2003 12:24:00 GMT

quote:
this is no comment on your article, but on your homepage.The link to your discussion forum yields a Fatal error: Call to undefined function: pg_connect() in /var/www-sql.nu/phpBB/db/postgres7.php on line 79error.

Ah, you mean at sql.nu. Yes, a while back we had a major crash and haven't brought our database online again (since the forums wheren't really used). We're a bit ashamed, but since we're soon moving to an entirely different server and environment we don't want to spend time fixing it now. Thnaks for the heads up though.--Chris Hedgate @ Apptus Technologies (http://www.apptus.se)http://www.sql.nu

RE: Cluster That Index! Part Two

kyleburke — Tue, 12 Aug 2003 06:31:00 GMT

Great Article. One addition comment about page splitting from your example. If your are worried about page slitting because of heavy inserts to a table put the clustered index on the identity column. Since the clustered index will be order by the data, if you put a clustered index on an identity column then the new row will be added to the end of the data pages and page splits won't occur.

RE: Cluster That Index! Part Two

Frank Kalis — Mon, 21 Jul 2003 00:43:00 GMT

Hi Chris,

quote:
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/chedgate/clusterthatindexparttwo.asp

this is no comment on your article, but on your homepage.The link to your discussion forum yields a Fatal error: Call to undefined function: pg_connect() in /var/www-sql.nu/phpBB/db/postgres7.php on line 79error.Cheers,Frank

Cluster That Index! Part Two

Chris Hedgate — Sat, 19 Jul 2003 00:00:00 GMT

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/chedgate/clusterthatindexparttwo.asp