MSSQL DB backend, MESD transaction log fills HDD
Over the last few weeks we have noticed strange behavior with the transaction logs for MESD.
We are using MSSQL 2008 for the DB backend.
This was originally configured back in November, and has been working fine until recently.
Not sure what changed, but it is now to the point where we need to truncate the log file a few time a day.
We've seen the transaction log file reach 65GB on a slow day, which makes no sense.
When this happens, the service desk all but dies - it loads up fine but no one can log into it.
Setting the recovery method from FULL to Simple seems to fix it, however this causes major issues with Backup Exec which is setup to backup our SQL DB's, so this is not ideal.
When it is on Full, and we restrict the DB transaction log to say 5GB, once the transaction log reaches that limit, Service Desk stops functioning properly. It appears that it requires the DB transaction log to be unrestricted.
I believe we are using build 8124.
Any idea as to what could be causing this issue and how to fix it?
Senior Client Technology Support Analyst
Bird Construction Inc
http://www.bird.ca
http://ca.linkedin.com/pub/carlo-piva/31/267/a5b
We are using MSSQL 2008 for the DB backend.
This was originally configured back in November, and has been working fine until recently.
Not sure what changed, but it is now to the point where we need to truncate the log file a few time a day.
We've seen the transaction log file reach 65GB on a slow day, which makes no sense.
When this happens, the service desk all but dies - it loads up fine but no one can log into it.
Setting the recovery method from FULL to Simple seems to fix it, however this causes major issues with Backup Exec which is setup to backup our SQL DB's, so this is not ideal.
When it is on Full, and we restrict the DB transaction log to say 5GB, once the transaction log reaches that limit, Service Desk stops functioning properly. It appears that it requires the DB transaction log to be unrestricted.
I believe we are using build 8124.
Any idea as to what could be causing this issue and how to fix it?
Senior Client Technology Support Analyst
Bird Construction Inc
http://www.bird.ca
http://ca.linkedin.com/pub/carlo-piva/31/267/a5b