I am stumped to see that the SQL Server table for ELMAH doesn't have a proper
clustering key...
Any particular reason for this? Having a clustering key on any SQL Server table
typically speeds up all operations - yes, all - including INSERT, UPDATE,
DELETE - so why *not* have it?
A "ElmahID BIGINT IDENTITY(1,1)" would be a good addition and a great candidate
for a clustering key - narrow, static, unique and ever increasing!
Original issue reported on code.google.com by mscheu...@gmail.com on 12 Jan 2012 at 6:26
Original issue reported on code.google.com by
mscheu...@gmail.com
on 12 Jan 2012 at 6:26