Skip to content

clustered index on ELMAH_Error #376

Open

Description

@GoogleCodeExporter
What new or enhanced feature are you proposing?
Currently, there is no clustered index on ELMAH_Error. From what I understand, 
this was changed back in r131 as a performance issue. However, this changed the 
nature of the table to a heap.

I would propose that if ErrorId is not appropriate for a clustered index (it is 
currently set as the primary key, but non-clustered) then place Sequence as the 
clustered index with ErrorId remaining as a non-clustered unique index on the 
table. 
Previous suggestion (issue 222) was:
CREATE UNIQUE CLUSTERED INDEX [PK_Sequence] ON [dbo].[ELMAH_Error] 
(
    [Sequence] ASC
)

CREATE UNIQUE NONCLUSTERED INDEX [IX_ErrorId] ON [dbo].[ELMAH_Error] 
(
    [ErrorId] ASC
)

What goal would this enhancement help you achieve?
Better, more consistent performance and adherence with generally recognized 
best practices. (see http://msdn.microsoft.com/en-us/library/hh213609.aspx)

Original issue reported on code.google.com by elsi...@gmail.com on 26 Oct 2014 at 2:17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions