We are struggling with multiple issues with SQL 2005 Ent (retail) over the past couple years. Aboutl a month ago it started to impact users and causing the server to crash. Currently, we only use SQL for Sharepoint. We plan to migrate over to Sharepoint 2013/SQL 2012 in the 2nd QTR of this year, but in the meantime, we are holding up SQL 2005 with 'tape and shoestring'.
We currently have SP 2013 / SQL 2012 running in a production environment as a reporting server for a Business Intelligence project we are workign on.
The main issue we're experiencing are minidump errors which is eating up about 40GB of disk space every two hours. The logs are written constantly, multiple times per second. I must clean out the log folder every 2 hours to maintain server uptime. After work hours, I cannot do this around the clock (I am the sole server/network/infrastructure support person for our business), so eventually the server crashes due to lack of disk space. SQL 2005 is installed on Win Server 2008 R2 Ent.
I found that every single log file points to this error:
Exception Address = 01105772 Module(sqlservr+00105772)
Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
After some research, a few articles pointed out that this particular error points to a bug in SQL 2005 Ent (retail) that requires installing SP1 or later to resolve the issue. Since the error began, we have had SP3 installed, so now the issue appears unrelated to the 'fix' posted on various articles.
We had a contractor look at our output logs from both SQL and windows debugger output for them to further look into the problem. Their final suggestion was to upgrade SQL to 2008 R2 or newer to resolve the issue. Reasoning for this was due to MS no longer supporting SQL 2005. My issue with this is that we have already purchased SQL 2012 which is in production on another server, and we plan to eventually migrate to that server in several months, so a $25K band-aid is crazy...small business, small budget.
My question to all of you is if (1) I can somehow disable the log folder from being written to? Or, (2) can I limit the amount of space it can write to? Right now it's pretty much unlimited and it will continue writing on our C: until there is no longer any space. This happens every single night. OR, (3) can I simply change the location of where the log files are written? Such as a external hard drive. That way, when it runs out of space, it simply stops writing? OR, (4) can I slow down the minidump writes? If I only had to clear out the folder every 4 or 5 days, this would be manageable and would provide 24hr uptime of services, as long as I maintain the folder cleaning.
Any help or suggestions at all would be greatly appreciated. This is impacting critical functions of our business, as well as many of our users. My main concern is to have the server stop crashing every day until we can work on the migration, which is in 2-3 months. I would rather have a temporary fix or work around, rather than having to re-install SQL completely and restore all of the data and reconfigure everything.
Thank you for taking the time to read this, and I dearly hope that someone has an answer for me.