> Do you think that changing the index on this table to clustered from > nonclustered would provide us with performance improvements?
Well, queries that use a clustered index generally run significantly faster than queries that use a nonclustered index. If you only put one index on a table, it's usually a clustered index because of this. If you put more than one index on a table, you have to decide where to use your clustered index, as you can only have one clustered index per table - a clustered index matches the physical arrangement of table rows. So, yes. But, I don't know whether the performance improvements you'd get from faster queries would be counterbalanced by the degradation you might see with inserts and deletes. Those can end up slower than they would otherwise be. Finally, honestly, if you already have an index in place, that's probably good enough. It's unlikely that you have enough records in this table that dropping one index and creating another is going to make much of a difference. The best thing you can do to improve performance of Client variables is to disable global Client variable updates if you don't need them. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:354891 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
