"PRIMARY" filegroup is full

Hello,
We have an SQL Server app written in ASP that suddenly has an error after 2
years of operation, and we're having trouble locating the problem. Here is
the error message below. The reference in the Knowledgebase for this error
doesn't seem to apply to us. There is plenty of space left on the drive. I
believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocat
e space for
object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
is full.
/Household.asp, line 298
a.. Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
a.. Page:
POST 700 bytes to /Household.asp
a.. POST Data:
submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&First
Name=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F
06%2F2006&EffectiveDate=10%2F17%2F2003&Las
. . .You say there is plenty of space left on the disk, but is there a max
size limit set on the file(s) contained in the PRIMARY filegroup? Can
you post the results of this (for your particular DB name that is):
USE <dbname>;
EXEC sp_helpfile;
*mike hodgson*
http://sqlnerd.blogspot.com
Dean J Garrett wrote:

>Hello,
>We have an SQL Server app written in ASP that suddenly has an error after 2
>years of operation, and we're having trouble locating the problem. Here is
>the error message below. The reference in the Knowledgebase for this error
>doesn't seem to apply to us. There is plenty of space left on the drive. I
>believe we're using SP3 of SQL Server 2000. Can anyone point us in the righ
t
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not alloca
te space for
>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>is full.
>/Household.asp, line 298
>a.. Browser Type:
>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>a.. Page:
>POST 700 bytes to /Household.asp
>a.. POST Data:
>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&Firs
tName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2
F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>.. . .
>
>|||I would also assume taht the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.|||Hi,
The database properties is set to "Unrestricted Growth" but for some reason
when the data file gets to 928MB, we get that error message even though ther
e is plenty of free space on the drive. Why would that happen?
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:Ocs8eJFLGHA.984@.t
k2msftngp13.phx.gbl...
You say there is plenty of space left on the disk, but is there a max size l
imit set on the file(s) contained in the PRIMARY filegroup? Can you post th
e results of this (for your particular DB name that is):
USE <dbname>;
EXEC sp_helpfile;
mike hodgson
http://sqlnerd.blogspot.com
Dean J Garrett wrote:
Hello,
We have an SQL Server app written in ASP that suddenly has an error after 2
years of operation, and we're having trouble locating the problem. Here is
the error message below. The reference in the Knowledgebase for this error
doesn't seem to apply to us. There is plenty of space left on the drive. I
believe we're using SP3 of SQL Server 2000. Can anyone point us in the right
direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocat
e space for
object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
is full.
/Household.asp, line 298
a.. Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
a.. Page:
POST 700 bytes to /Household.asp
a.. POST Data:
submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&First
Name=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F
06%2F2006&EffectiveDate=10%2F17%2F2003&Las
.. . .|||THe database is set up for automatic unrestricted growth, and there is
plenty of disk space on the drive. For some reason, whenever the data file
gets to 928MB, we get the error message and can't run the app until we
shrink the database to below 928MB. Why does that happen?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
>I would also assume taht the datafile in the filegroup are not setup
> for automatic growth.
> HTH, Jens Suessmeyer.
>|||"The database"? Which part of the database? Are you talking about the
log file(s)? One of the files in the PRIMARY filegroup? All of the
files in the PRIMARY filegroup? Files in some secondary filegroup?
Can you please post the results of:
EXEC sp_helpfile;
In the DB in question. It's not that we don't trust you, it's just that
we prefer to deal in black & white (this is a troubleshooting process).
*mike hodgson*
http://sqlnerd.blogspot.com
Dean J Garrett wrote:

>THe database is set up for automatic unrestricted growth, and there is
>plenty of disk space on the drive. For some reason, whenever the data file
>gets to 928MB, we get the error message and can't run the app until we
>shrink the database to below 928MB. Why does that happen?
>
>"Jens" <Jens@.sqlserver2005.de> wrote in message
>news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
>
>
>|||Here is the output from sp_helpfile. When I use Enterprise Mgr. and edit the
properties for the database "CAA" I see that the Checkbox for "Unrestricted
Growth" is checked. There is several GB on the drive, so we thought the dat
abase would continue to grow unrestricted until all the space is taken up. I
nstead we get the error once the CAA_Data.MDF file grows to around 928MB. Th
e only way we can get the ASP application running again is to delete records
thus reducing the size of the .MDF file.
CAA_Data
1 F:\MSSQL\Data\CAA_Data.MDF PRIMARY 950272 KB Unlimited 5% data only
CAA_Log
2 F:\MSSQL\Data\CAA_Log.MDF NULL 5120 KB Unlimited 5% log only
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:%23UNbpnQLGHA.394
4@.tk2msftngp13.phx.gbl...
"The database"? Which part of the database? Are you talking about the log
file(s)? One of the files in the PRIMARY filegroup? All of the files in th
e PRIMARY filegroup? Files in some secondary filegroup?
Can you please post the results of:
EXEC sp_helpfile;
In the DB in question. It's not that we don't trust you, it's just that we
prefer to deal in black & white (this is a troubleshooting process).
mike hodgson
http://sqlnerd.blogspot.com
Dean J Garrett wrote:
THe database is set up for automatic unrestricted growth, and there is
plenty of disk space on the drive. For some reason, whenever the data file
gets to 928MB, we get the error message and can't run the app until we
shrink the database to below 928MB. Why does that happen?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com...
I would also assume taht the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.|||I don't know either.
There are some funky things that Windows sometimes does in the way of
reserving disk space for virtual files, that could be involved.
Have you tried the simple expedient of rebooting the server?
Josh
On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
wrote:
>We have an SQL Server app written in ASP that suddenly has an error after 2
>years of operation, and we're having trouble locating the problem. Here is
>the error message below. The reference in the Knowledgebase for this error
>doesn't seem to apply to us. There is plenty of space left on the drive. I
>believe we're using SP3 of SQL Server 2000. Can anyone point us in the righ
t
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not alloca
te space for
>object 'tblTabl31' in database 'Database1' because the 'PRIMARY' filegroup
>is full.
>/Household.asp, line 298
>a.. Browser Type:
>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
>a.. Page:
>POST 700 bytes to /Household.asp
>a.. POST Data:
>submitAction=Save&InID=25449&SSN=531067163&FileClosedDate=&FileNumber=&Firs
tName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2
F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>. . .
>|||OH yes, we've tried everything. We keep trimming out records to allow the
app to keep running, but over time (usually just a few days), the MDF file
size grows to that magical limit of around 928MB and then we see the error
again. The drive has 17GB of available storage.
"JXStern" <JXSternChangeX2R@.gte.net> wrote in message
news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.
4ax.com...
>I don't know either.
> There are some funky things that Windows sometimes does in the way of
> reserving disk space for virtual files, that could be involved.
> Have you tried the simple expedient of rebooting the server?
>
> Josh
>
> On Tue, 7 Feb 2006 17:04:50 -0800, "Dean J Garrett" <info@.amuletc.com>
> wrote:
>|||Why would you notice this several times? If the file grow to this limit (and
the problem occurs),
then clearly you need a database size > that size. So just expand the databa
se size and monitor so
you have fr ee space. Autogrow has its issues and these things does happen (
files doesn't
autogrow -> error message), search the archives for old posts and technical
details. So, just expand
the file size manually and you will be fine. Oh, and don't shrink:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:unlvTmmLGHA.3144@.TK2MSFTNGP11.phx.
gbl...
> OH yes, we've tried everything. We keep trimming out records to allow the
app to keep running, but
> over time (usually just a few days), the MDF file size grows to that magic
al limit of around 928MB
> and then we see the error again. The drive has 17GB of available storage.
>
>
> "JXStern" <JXSternChangeX2R@.gte.net> wrote in message
> news:dk6nu1hcubrleht1nfc3u7mvcun8i0veoo@.
4ax.com...
>