A clustered index on a GUID is generally a bad idea, because it forces table fragmentation. Clustered indexes on tables with lots of inserts should generally be something sequential, like an ID or a timestamp.
If the table has no clustered index, it also has no base sort order, and fragmentation is pretty much meaningless. If it's not hurting the performance on the database, don't worry about it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon