quote:

---

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

---

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 79

error.

---

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

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.