Could not allocate space for object ... in database ... because the ... filegroup is full.

Hello,
I keep getting the following error from time to time:
"Could not allocate space for object ... in database ... because the
... filegroup is full."
The file group currently has a size of 2338 MB.
It is set to automatically grow by steps of 200 MB, I tried a grow by
10 percent but had the same problem.
My application is using ADO and ODBC.
My application succeeds when I relaunch it at a later time.
The version of the engine is SQL Server Entreprise Edition 8.00.760
(SP3).
The version of the ODBC Driver is 03.81.9041.
By the way I see in the trace of the SQL Server that it was doing a
backup of the transaction log just before the failure.
As a matter of fact I created a Database Management Plan that is making
backups of the transaction log periodically outside the period when my
application is scheduled and for some resaon my application was running
longer than expected.
Might this be the reason ?
Thanks in advance,
Eric.Eric
Do you have enough free space on the disk?
"Eric Paesmans" <Eric.Paesmans@.missioncriticalit.com> wrote in message
news:1164627437.187453.49910@.45g2000cws.googlegroups.com...
> Hello,
> I keep getting the following error from time to time:
> "Could not allocate space for object ... in database ... because the
> ... filegroup is full."
> The file group currently has a size of 2338 MB.
> It is set to automatically grow by steps of 200 MB, I tried a grow by
> 10 percent but had the same problem.
> My application is using ADO and ODBC.
> My application succeeds when I relaunch it at a later time.
> The version of the engine is SQL Server Entreprise Edition 8.00.760
> (SP3).
> The version of the ODBC Driver is 03.81.9041.
> By the way I see in the trace of the SQL Server that it was doing a
> backup of the transaction log just before the failure.
> As a matter of fact I created a Database Management Plan that is making
> backups of the transaction log periodically outside the period when my
> application is scheduled and for some resaon my application was running
> longer than expected.
> Might this be the reason ?
> Thanks in advance,
> Eric.
>|||Yes,
I got more than 12 GB on the disk where my DB files are located, almost
2 GB on my system disk and a bit more than 1 GB on the disk where the
software is installed.
Concerning the interference with the backup of the transaction log I
mentioned, I checked and the backup happened only on the production
server and not on the acceptance server while my application failed on
both servers.
It might have happened that the network was disturbed at that time.
Might this have an impact ?
Thanks in advance,
Eric.
> Eric
> Do you have enough free space on the disk?
> "Eric Paesmans" <Eric.Paesmans@.missioncriticalit.com> wrote in message
> news:1164627437.187453.49910@.45g2000cws.googlegroups.com...
>> Hello,
>> I keep getting the following error from time to time:
>> "Could not allocate space for object ... in database ... because the
>> ... filegroup is full."
>> The file group currently has a size of 2338 MB.
>> It is set to automatically grow by steps of 200 MB, I tried a grow by
>> 10 percent but had the same problem.
>> My application is using ADO and ODBC.
>> My application succeeds when I relaunch it at a later time.
>> The version of the engine is SQL Server Entreprise Edition 8.00.760
>> (SP3).
>> The version of the ODBC Driver is 03.81.9041.
>> By the way I see in the trace of the SQL Server that it was doing a
>> backup of the transaction log just before the failure.
>> As a matter of fact I created a Database Management Plan that is making
>> backups of the transaction log periodically outside the period when my
>> application is scheduled and for some resaon my application was running
>> longer than expected.
>> Might this be the reason ?
>> Thanks in advance,
>> Eric.
>|||One more thought.
Every evening I am shrinking the database (DBCC SHRINKDATABASE ...).
Might there be a side effect ?
Thanks in advance,
Eric.
> Yes,
> I got more than 12 GB on the disk where my DB files are located, almost
> 2 GB on my system disk and a bit more than 1 GB on the disk where the
> software is installed.
> Concerning the interference with the backup of the transaction log I
> mentioned, I checked and the backup happened only on the production
> server and not on the acceptance server while my application failed on
> both servers.
> It might have happened that the network was disturbed at that time.
> Might this have an impact ?
> Thanks in advance,
> Eric.
>> Eric
>> Do you have enough free space on the disk?
>> "Eric Paesmans" <Eric.Paesmans@.missioncriticalit.com> wrote in message
>> news:1164627437.187453.49910@.45g2000cws.googlegroups.com...
>> Hello,
>> I keep getting the following error from time to time:
>> "Could not allocate space for object ... in database ... because the
>> ... filegroup is full."
>> The file group currently has a size of 2338 MB.
>> It is set to automatically grow by steps of 200 MB, I tried a grow by
>> 10 percent but had the same problem.
>> My application is using ADO and ODBC.
>> My application succeeds when I relaunch it at a later time.
>> The version of the engine is SQL Server Entreprise Edition 8.00.760
>> (SP3).
>> The version of the ODBC Driver is 03.81.9041.
>> By the way I see in the trace of the SQL Server that it was doing a
>> backup of the transaction log just before the failure.
>> As a matter of fact I created a Database Management Plan that is making
>> backups of the transaction log periodically outside the period when my
>> application is scheduled and for some resaon my application was running
>> longer than expected.
>> Might this be the reason ?
>> Thanks in advance,
>> Eric.
>>|||> Every evening I am shrinking the database (DBCC SHRINKDATABASE ...).
> Might there be a side effect ?
Yes, you don't want to shrink regularly. There are plenty of reasons for this, see:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Sometime autogrow doesn't seem to work, because the allocation of new storage isn't "fast enough".
Short story is that autogrow should be seen as something you have so you don't get paged in the
middle of the night. For normal operations, make sure that the databases has some air, and monitor
and pre-allocate storage.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Eric Paesmans" <Eric.Paesmans@.missioncriticalit.com> wrote in message
news:456c2a5b$0$1284$6c56d894@.reader0.news.be.easynet.net...
> One more thought.
> Every evening I am shrinking the database (DBCC SHRINKDATABASE ...).
> Might there be a side effect ?
> Thanks in advance,
> Eric.
>> Yes,
>> I got more than 12 GB on the disk where my DB files are located, almost 2 GB on my system disk
>> and a bit more than 1 GB on the disk where the software is installed.
>> Concerning the interference with the backup of the transaction log I mentioned, I checked and the
>> backup happened only on the production server and not on the acceptance server while my
>> application failed on both servers.
>> It might have happened that the network was disturbed at that time.
>> Might this have an impact ?
>> Thanks in advance,
>> Eric.
>> Eric
>> Do you have enough free space on the disk?
>> "Eric Paesmans" <Eric.Paesmans@.missioncriticalit.com> wrote in message
>> news:1164627437.187453.49910@.45g2000cws.googlegroups.com...
>> Hello,
>> I keep getting the following error from time to time:
>> "Could not allocate space for object ... in database ... because the
>> ... filegroup is full."
>> The file group currently has a size of 2338 MB.
>> It is set to automatically grow by steps of 200 MB, I tried a grow by
>> 10 percent but had the same problem.
>> My application is using ADO and ODBC.
>> My application succeeds when I relaunch it at a later time.
>> The version of the engine is SQL Server Entreprise Edition 8.00.760
>> (SP3).
>> The version of the ODBC Driver is 03.81.9041.
>> By the way I see in the trace of the SQL Server that it was doing a
>> backup of the transaction log just before the failure.
>> As a matter of fact I created a Database Management Plan that is making
>> backups of the transaction log periodically outside the period when my
>> application is scheduled and for some resaon my application was running
>> longer than expected.
>> Might this be the reason ?
>> Thanks in advance,
>> Eric.
>>