Hi -
I am getting this exact same error that was outlined in this thread: Auditing Problem and have a similar setup where we are using SQL Express as the default installation database. The database is full at 4GB and we are getting error messages in the Windows Event Viewer indicating that the database can't be increased due to the 4GB limitation.
I followed the resolution that was in the previous discussion - in the Auditing tab I changed the default number of days from 36000 something to 85. This had no effect on the size of the database (it is using the exact same amount of space) and the error messages in the Auditing tab and the Windows event viewer are still occurring. This also has lead to the log file for the Audit database to grow to over 7GB. I tried adjusting the auditing to the minimum as well, and this too had no effect.
Basically it seems as though BI 4.0 is not deleting any data when I changed the number of days to keep. While I could adjust this smaller again, I don't believe it will resolve the issue.
What are the procedures for manually clearing data out of the Audit database tables when reducing the number of days of Auditing retained doesn't work?
These are the errors I am getting in the Auditing tab:
Warning: "No connection to Auditing Data Store from CMS <CMS Name>
WARNING: Auditing data may remain in server buffers
<CMS Name>.DashboardDesignCacheServer,<CMS Name2>.DashboardsCacheServer, <CMS Name3>.DashboardsCacheServer
And this is the one from the Windows Event Viewer:
Log Name: | Application |
Source: | MSSQL$BOE140 |
Date: | 4/2/2015 3:02:20 PM |
Event ID: | 1105 |
Task Category: Server
Level: | Error |
Keywords: | Classic |
User: | N/A |
Computer: | <CMS Name1>.ads.bshsi.com |
Description:
Could not allocate space for object 'dbo.ADS_EVENT'.'ADS_EVENT_7' in database 'BOE140_Audit' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
At least I know why I am getting the errors, but not sure what I can do about resolving them.