Follow

Could not Allocate Space for object in database because filegroup is full

PROBLEM:

I get a message stating 'Could not allocation Space for object in database because file-group is full'

 

SOLUTION:

Step 1: I checked if my Hard Drive has more space available.

If your Hard Drive is full, please empty out any unnecessary stuff. This may not directly fix your problem, but it is a necessary exercise to do before you do Step 2.

Step 2: Delete unnecessary object from your file group.

If your primary filegroup (in most cases) or filegroup which has generated this error is restricted to fix size, you may get this error. You have two workarounds here.

Step 2a: Drop some of the following tables

  1. ntEventLogYYYYMMDD
  2. MonitorCounterLogYYYYMMDD
  3. MonitorProcessLogYYYYMMDD
  4. MonitorSNMPLogYYYYMMDD
  5. ErrorLogYYYYMMDD

example SQL command to drop table:

drop table ntEventLog19011220

WARNING: DO NOT DROP ANY TABLES OUTSIDE OF THE ONES SPECIFIED ABOVE.

**There is no way to recover the data once the table has been dropped**

**Do a full database backup prior to dropping any table**

**Kaseya is not responsible for any data loss if the instructions above are not followed**

**Do not use steps for any situation aside from the situation specified above**

Step 2b: Check AutoGrowth

2-24-2015_3-02-44_PM.jpg

Make sure that AutoGrowth is not set. Change it from the 'Limited' option to be 'Unlimited' so that the Kaseya database can grow as necessary.

The following query will show you the autogrowth functionality for the databases on your system.

select
Name as 'FileName', physical_name as 'Path',
case TYPE when 1 then 'TransLog'
when 0 then 'Database'
else 'Other' END as 'Type',
state_desc as 'State',
(size*8) as 'Disk File Size KB',
case max_size when 0 then 'No Growth'
else 'Until disk is full' END as 'Growth',
case growth when 0 then 'No Growth'
else
(case is_percent_growth when 0 then (growth*8)
else growth END)
END as 'Automatically Growth',
case is_percent_growth when 0 then 'MB' else 'in %' END as 'Growth Type'
from sys.database_files

After you perform the steps above, you will need to run a database shrink to bring the database size back down.

Here is the command to run a database shrink

DBCC SHRINKDATABASE('KSUBSCRIBERS')
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.