Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ELMAH not compatible with SQL 2012 #274

Open
atifaziz opened this issue Aug 25, 2015 · 6 comments
Open

ELMAH not compatible with SQL 2012 #274

atifaziz opened this issue Aug 25, 2015 · 6 comments

Comments

@atifaziz
Copy link
Member

Originally reported on Google Code with ID 274

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.

Reported by [email protected] on 2012-02-10 07:40:43

@atifaziz
Copy link
Member Author

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.

Reported by azizatif on 2012-02-10 08:51:50

  • Status changed: Accepted
  • Labels added: Type-Defect, Component-Persistence
  • Labels removed: Type-Enhancement

@atifaziz
Copy link
Member Author

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

Reported by [email protected] on 2012-02-10 18:17:34

@atifaziz
Copy link
Member Author

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.

Reported by [email protected] on 2014-03-14 15:15:14

@atifaziz
Copy link
Member Author

I just encountered this on a new 2012 DB that is intended to be Elmah only. I would
be happy to rewrite/upgrade the script using a later version than 2000 (2008?), so
the warning could be altered as well, but I don't know what it would take to test it.
Please let me know if I can help. 

Reported by [email protected] on 2015-04-28 20:57:02

@atifaziz
Copy link
Member Author

> I would be happy to rewrite/upgrade
> the script using a later version than 2000 (2008?)

When you do that, feel free to share it back here as an attachment to a comment, or
better yet, post it as a Gist (https://gist.github.com) and drop a pointer here.

>  I don't know what it would take to test it

Dog-food[1] it like no tomorrow. :)

[1] http://en.wikipedia.org/wiki/Eating_your_own_dog_food

Reported by azizatif on 2015-04-29 16:25:11

@pablosguajardo
Copy link

hello, you could update the SQL script with support for SQL Server 2012?

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

No branches or pull requests

2 participants