On this thread I read a discussion about heap tables: http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=9684 I have a table that has quite a few inserts and updates, but also quite a few reads. I'm using a guid for primary key. Should I make this a heap table in order to avoid page splits? If so, what penalty do I pay when doing selects? In general, if you use a guid for primary key, would you suggest to make the table a heap (unless you have a suitable candidate key)? Thanks for any help.