January 27, 2016 at 2:35 pm
We've been on SQL2012 sp3 since early December 2015.
since then, we've been noticing an increase in system-type errors, particularly lock timeouts. This is even happening on small-scale jobs, e.g. rebuilding an index on a table in the ReportServer db with about 60k rows.
We have the default setting for lock timeouts.
The usual 'solution' to this problem is restarting the server (when in doubt, reboot), and we're having to do that more often with sp3.
I haven't seen any other noise about this particular issue on the web.
thanks for any feedback!
January 27, 2016 at 2:50 pm
Did you observe this same behavior when you tested the SP3 upgrade BEFORE you rolled it into production? You did DO that, right?!? 🙂
Did you review the complete fix list for the SP to see if anything looked suspicious?
Did you compare your current settings of everything against your known-good-master-copy of all settings and configurations you keep in source control?!? 🙂
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
January 27, 2016 at 8:03 pm
Uh oh. I haven't heard of anything quirky with SQL 2012 SP3 yet, but would be very interested if anything comes up. I haven't installed it yet and won't until after it's been out for a while. The reasons I don't install them quickly are threefold: forget 2000 SP3, 2005 SP4 and 2014 SP1 (the first release).
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply