CLIENT AREACall Us 1-800-383-5193


Call Us 1-800-383-5193


Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

SQL error “could not allocate space for object” – How we troubleshoot it

by | Feb 8, 2021

Having a tough time fixing the error SQL error ‘Could not allocate space for object’? We can help you fix it.

Generally, the database stores the website details. SQL Server Management Studio is used to manage the MSSQL database. Also, the SQL Server Management Studio has set a default size limit for each database.

When we reach this limit the error message ‘Could not allocate space for object’ occurs on the website.

There is multiple maintenance job that is running at the background in SQL server by default. The details are logged in tables which makes the database size to increase. Another reason is that the database utilizes the maximum size by adding contents in the database.

Here at Bobcares, we often receive requests to fix database-related errors as part of our Server Management Services.

Today, let’s see how to fix this error message.


How we resolve the SQL error “Could not allocate space for object”

Here are the steps our Support Engineers follow to resolve the error.


1. Increasing the size limit of the database

First, we analyze the size of the database. After determining it from SQL Server Management Studio we increase the size of the database. The Plesk user manages the database from mylittleadmin. The option to increase the size is not available in mylittleadmin.

There is a restriction when increasing the database size for SQL server express edition. While, Microsoft SQL Server 2008 express the database size can be increased up to 4GB. The version from Microsoft SQL Server 2008 R2 express and above let us to increase the database size to 10GB.


2. Decreasing the size of the database

If the current database size has reached its limit, we will decrease the size of the database.

We will truncate the log tables to decrease the size of the database. There can be multiple log tables in the database. We find out the log tables that are consuming high disk space and truncate the table.

Here is the SQL query we use to truncate the log files.

truncate table tablename;

Truncating the non-log tables will crash the database. As a precaution, we always take the database backup before performing such tasks.

[Still not able to fix the error? We’re available if any assistance is required]



In short, “Could not allocate space for object” will occur due to insufficient space in the database. Today we’ve discussed the reasons for the error and how our Support Engineers resolve this error.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *