search

DebugOfTheRoad / elmah

Automatically exported from code.google.com/p/elmah
Apache License 2.0
0 stars 0 forks source link

SQL Server table ought to have a proper clustering key #268

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
This issue has been migrated to:
https://github.com/elmah/Elmah/issues/268
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:22