Could not allocate space for object (ObjectName) in database (DatabaseName)

Netwrix Auditor SQL Databases
6.5 and older
7.0-8.5
9.0-9.7
9.8
https://kb.netwrix.com/1093
Copy Article URL Copied

Scenario

Error in reports stating Could not allocate space for object ‘*’ in database ‘*’ 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.

Cause

The Monitoring Plan Audit Database is full and the SQL Server doesn’t allow any further writing to it. This can be due to two reasons:

Solution

The Long Term Solution

If you are using SQL Express and the database has reached 10GB, please consider the following options:

  1. Upgrade SQL Server edition from Express to Standard or Enterprise
  2. Change database retention to a smaller value via the Netwrix Auditor UI.
  3. Narrow down the auditing scope by unchecking heavy auditing options (like Successful Reads for File Servers)
  4. Split your Monitoring Plan (Managed Object in Netwrix Auditor 8.5 and older) into several plans, each with its own database

The Short Term Solution

In order to immediately relieve this issue:

  • Upgrade SQL to the licensed version. Then SQL server again allows connection to the DB and Netwrix will be able to restore the full functionality.
  • OR Recreate the 10 GB database. Since all data is duplicated to the Long-Term Archive, you should not expect any data losses. Rebuilding the database will cause the contained data to no longer be available for Searching and Reporting. To Search or Report on this data, you will need to use Investigations feature.

To recreate the database, follow these steps:

  1. Open SQL Server Management Studio -> Connect to the instance -> Expand the instance name -> expand databases -> right click on the database -> Delete
  2. Make sure to check the box “Close existing connections” and confirm the deletion
  3. Restart Netwrix Auditor Management Service
  4. Check that the database with the same name was recreated
  5. Update the database statistics in the Netwrix Health Status dashboard and check the status of the new DB
Go Up