Open GoogleCodeExporter opened 8 years ago
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
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
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
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.
Original comment by jsm...@stayonline.com
on 28 Apr 2015 at 8:57
> 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
Original comment by azizatif
on 29 Apr 2015 at 4:25
This issue has been migrated to:
https://github.com/elmah/Elmah/issues/274
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
Original issue reported on code.google.com by
peteren...@yahoo.com
on 10 Feb 2012 at 7:40