ELMAH not compatible with SQL 2012

[GoogleCodeExporter]

What new or enhanced feature are you proposing?
It should work.

What goal would this enhancement help you achieve?

Directed to set compatability level = 80 in docs
Using MVC4
SQL Server 2012 RC0 as the logging database - create new
Run script

Error report:

Msg 15048, Level 16, State 1, Line 1
Valid values of the database compatibility level are 90, 100, or 110.

Original issue reported on code.google.com by peteren...@yahoo.com on 10 Feb 2012 at 7:40

[GoogleCodeExporter]

I would take the compatibility level setting as a guidance and a safety 
measure. It's also only applicable when you're hosting ELMAH database objects 
in their own database. If you're hosting them in the application database then 
you probably cannot afford to set the compatibility level.

What would be helpful is if you can provide feedback (based on field usage) on 
whether or not there are any compatibility issues with SQL Server 2012 if the 
script is applied as-is and without the compatibility setting.

Original comment by azizatif on 10 Feb 2012 at 8:51

• Changed state: Accepted
• Added labels: Type-Defect, Component-Persistence
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

OK. I am running tests now. I will use a separate 2012 database for ELMAH. No 
compatibility commands. Just run the script in the db. Then see what happens 
with the application on my local test box. If this all works out I plan to put 
it up on Azure for another test run. I will provide feedback here.
Thanks,
Peter

Original comment by peteren...@resourcedevelopment.net on 10 Feb 2012 at 6:17

[GoogleCodeExporter]

We have been running ELMAH on SQL 2012 in production for nearly a year without 
any 2012-specific issues.  I suggest this issue be closed.

Original comment by b...@saberin.com on 14 Mar 2014 at 3:15