QAID # 9089 Published
Question / Problem:
How do I resolve the error:
"KdoLib: Error executing SQL command. Could not allocate space for object 'StatsModuleLaunch' in database 'ACSystem' because the 'PRIMARY' filegroup is full (1105)"
Answer / Solution:
This error is occurring because the database LOG file is either too large for what has been allocated, or the SQL Server disk is full.
To resolve this issue:
- It is important to set up the database to automatically shrink itself. This is done in SQL Enterprise Manager by finding the database of interest, clicking with the right mouse button, then selecting properties. Under the Options folder make sure you have selected "Truncate Log on CheckPoint", "Select into/bulk copy", and "Auto Shrink". These options will significantly help control the size of the database and log file. This will also compact the database on a daily basis. The appropriate options are shown below. Note that you may not be able to make these changes if your database is with a Web hosting provider. In this case, ask them to make the change.
Note: After making these changes, it may take minutes and possibly more than 1 hour for the server to recover from the problem and shrink the database.
- Set up a routine maintenance plan to back up the database and log file. At minimum, the database and log file should be backed up weekly. On high traffic sites this should be done daily. Normally the LOG file will not shrink until it has been backed up at which time SQL truncates the log and shrinks the file.
- If number 1 is not the cause of the problem, also check that the hard drive holding the databases on the SQL Server is not full. A full hard drive has also been known to cause this problem. If this is the cause of the problem, consider moving the database to another larger drive.