views:

9

answers:

0

Alright we are quite sure the Elmah has become too big. Apparently the database is sitting at 17GB because of this. Were were getting timeout errors accessing /elmah first and now there are errors inserting data into it - hence exceptions are being thrown by the application.

I just wanted to confirm can INSERT timeouts happen - or does Elmah try reading values while logging them too - which can explain the below error?

Will cleaning up the elamh log table help

Edit

 - The cleaning has been happening periodically
 - It makes me think if it is the fragmentation of the table

Will a Shrink and Rebuild index of the Database help?

Error Stack