sql error: operation

Showing posts with label operation. Show all posts

Thursday, March 8, 2012

"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 allocate 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&FileClo sedDate=&FileNumber=&FirstName=MARY&MiddleInitial= &DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02% 2F06%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 right
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate 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&FileCl osedDate=&FileNumber=&FirstName=MARY&MiddleInitial =&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02 %2F06%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 there is plenty of free space on the drive. Why would that happen?
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:Ocs8eJFLGHA.984@.tk2msftngp13.phx.gbl...
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 right
direction? Thanks!!
a.. Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate 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&FileClo sedDate=&FileNumber=&FirstName=MARY&MiddleInitial= &DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02% 2F06%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.googlegr oups.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.googleg roups.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 database would continue to grow unrestricted until all the space is taken up. Instead we get the error once the CAA_Data.MDF file grows to around 928MB. The 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.3944@.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 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.googlegr oups.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 right
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate 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&FileCl osedDate=&FileNumber=&FirstName=MARY&MiddleInitial =&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02 %2F06%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 database 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 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...
>

"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...
>

"PRIMARY" filegroup is full

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 there is plenty of free space on the drive. Why =would that happen?
"Mike Hodgson" 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 =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 =; EXEC sp_helpfile;
--mike =hodgsonhttp://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 allocate 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=3DSave&InID=3D25449&SSN=3D531067163&FileClosedDa=te=3D&FileNumber=3D&FirstName=3DMARY&MiddleInitial=3D&DAP==3D1&LastName=3DTARDIN&SAT=3D101&ApplicationDate=3D02%2F06%2F=2006&EffectiveDate=3D10%2F17%2F2003&Las .. . .

--=_NextPart_000_0007_01C62CB5.99712670--|||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.
>|||This is a multi-part message in MIME format.
--030903070503060406070405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
"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...
>
>>I would also assume taht the datafile in the filegroup are not setup
>>for automatic growth.
>>HTH, Jens Suessmeyer.
>>
>
>
--030903070503060406070405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>"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: 
</tt><tt> 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).</tt> 
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
-- 
 mike
hodgson 
<a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a>

</div>
 
 
Dean J Garrett wrote:
<blockquote cite="midO3v5omPLGHA.2300@.TK2MSFTNGP15.phx.gbl" type="cite">
<pre wrap="">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" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:Jens@.sqlserver2005.de"><Jens@.sqlserver2005.de></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com">news:1139382110.154689.191800@.o13g2000cwo.googlegroups.com</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I would also assume taht the datafile in the filegroup are not setup
for automatic growth.
HTH, Jens Suessmeyer.
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--030903070503060406070405--|||This is a multi-part message in MIME format.
--=_NextPart_000_0007_01C62CD1.B9030E10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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 database would continue to grow unrestricted until all =the space is taken up. Instead we get the error once the CAA_Data.MDF =file grows to around 928MB. The 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.3944@.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 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=20
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.

--=_NextPart_000_0007_01C62CD1.B9030E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

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 database would continue to grow unrestricted until all =the space is taken up. Instead we get the error once the CAA_Data.MDF file =grows to around 928MB. The 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" wrote =in message news:%23UNbpnQLGHA.=3944@.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 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 =hodgsonhttp://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" =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.
--=_NextPart_000_0007_01C62CD1.B9030E10--|||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 right
>direction? Thanks!!
>
>a.. Error Type:
>Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%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:
>>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 allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>|||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 database 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 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:
>>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 allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>|||We tried to expand the size, but it won't let us type in a value larger than
1200MB for some reason. I have no idea why since the drive has 17GB is free
space. So our problem is that we must keep deleting records in the database
so the MDF file won't exceed this "magical" limit.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
> 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 database 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 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:
>>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 allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||Additionally, when we try to manually increase the size, we get the error
message:
Error 5149: MODIFY FILE encountered operating system error 112 (There is not
enough space on the disk) while attempting to expand the physical file. When
we look at the drive, there is 17GB of free space as reported by Windows.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
> 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 database 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 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:
>>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 allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||> We tried to expand the size, but it won't let us type in a value larger
> than 1200MB for some reason.
What is 'it' referring to? Enterprise Manager? What happens if you run a
statement like this one:
ALTER DATABASE <db_name>
MODIFY FILE
(NAME = <logical_datafile_name>,
SIZE = 5GB);
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:eTxxNspLGHA.3960@.TK2MSFTNGP09.phx.gbl...
> We tried to expand the size, but it won't let us type in a value larger
> than 1200MB for some reason. I have no idea why since the drive has 17GB
> is free space. So our problem is that we must keep deleting records in the
> database so the MDF file won't exceed this "magical" limit.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
>> 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 database 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 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:
>>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 allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||This is an error thrown from the OS to SQL Server, so you need to investigate why the OS doesn't
think there is more space or allow SQL Server to use more space. Perhaps there's some kind of user
quota (the user being the SQL Server service account)? Or database files being compressed (not
supported)?
--
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:OROqI0pLGHA.1532@.TK2MSFTNGP12.phx.gbl...
> Additionally, when we try to manually increase the size, we get the error message:
> Error 5149: MODIFY FILE encountered operating system error 112 (There is not enough space on the
> disk) while attempting to expand the physical file. When we look at the drive, there is 17GB of
> free space as reported by Windows.
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
>> 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 database 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 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:
>>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 allocate 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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>|||If you have enough disk space my guess is you are possibly using another
file system other than NTFS ?
I had a client a while ago that hit this same issue they were using FAT32
and were hitting the max file size limit due to the file system maximum
which in there case i think was 4GB if i remember correctly...
Are you using NTFS?
possibly maybe also some form of disk quota for the user account ?
my 2 cents
HTH
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:usAL8etLGHA.1048@.TK2MSFTNGP10.phx.gbl...
> This is an error thrown from the OS to SQL Server, so you need to
> investigate why the OS doesn't think there is more space or allow SQL
> Server to use more space. Perhaps there's some kind of user quota (the
> user being the SQL Server service account)? Or database files being
> compressed (not supported)?
> --
> 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:OROqI0pLGHA.1532@.TK2MSFTNGP12.phx.gbl...
>> Additionally, when we try to manually increase the size, we get the error
>> message:
>> Error 5149: MODIFY FILE encountered operating system error 112 (There is
>> not enough space on the disk) while attempting to expand the physical
>> file. When we look at the drive, there is 17GB of free space as reported
>> by Windows.
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23f2krjnLGHA.2124@.TK2MSFTNGP14.phx.gbl...
>> 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 database 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 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:
>>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 allocate
>>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=&FirstName=MARY&MiddleInitial=&DAP=1&LastName=TARDIN&SAT=101&ApplicationDate=02%2F06%2F2006&EffectiveDate=10%2F17%2F2003&Las
>>. . .
>>
>>
>>
>

Tuesday, March 6, 2012

"Not enough Storage"

When I tried to save a stored proedure (in SQL Server 2005 Express), I got a
n
error saying "The operation could not be completed. Not enough storage is
available to complete this operation."
Any idea what is causing this error to pop up? I still have about 4GB disk
space left.
Thanks.SQL Express has a 4GB limit on the database size so if you're at that limit
you are out of space no matter how much disk space is left.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Swami" <Swami@.discussions.microsoft.com> wrote in message
news:E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
> When I tried to save a stored proedure (in SQL Server 2005 Express), I got
> an
> error saying "The operation could not be completed. Not enough storage is
> available to complete this operation."
> Any idea what is causing this error to pop up? I still have about 4GB
> disk
> space left.
> Thanks.|||My whole MSSQL folder is only 148 MB and my particular database in question
is only 2MB in size. I actually have very little data...about 7-8 tables
which are mostly empty and about 25 stored procedures, each of them quite
short. Any ideas?
Thanks.
"Roger Wolter[MSFT]" wrote:

> SQL Express has a 4GB limit on the database size so if you're at that limi
t
> you are out of space no matter how much disk space is left.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Swami" <Swami@.discussions.microsoft.com> wrote in message
> news:E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
>
>|||Well, one guess is you might have choosen the option
Do not autogrow
right click on database -> properties -> datafiles
check - Automatically grow file.
and also
maximum file size -> unrestricted file growth.
Do the same in log files. And see.
Hope this helps.
And I believe this is your test database. (and not production :)|||What tool are you using to create the stored procedure? You might try
saving the proc script to a file and creating with the SQLCMD.EXE
command-line utility.
Hope this helps.
Dan Guzman
SQL Server MVP
"Swami" <Swami@.discussions.microsoft.com> wrote in message
news:E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
> When I tried to save a stored proedure (in SQL Server 2005 Express), I got
> an
> error saying "The operation could not be completed. Not enough storage is
> available to complete this operation."
> Any idea what is causing this error to pop up? I still have about 4GB
> disk
> space left.
> Thanks.|||this message indicated a bug referenced in sql server 2000 if you are using
lookups...
try your error message with google
Nicolas Guinet
"Swami" <Swami@.discussions.microsoft.com> a crit dans le message de news:
E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
> When I tried to save a stored proedure (in SQL Server 2005 Express), I got
> an
> error saying "The operation could not be completed. Not enough storage is
> available to complete this operation."
> Any idea what is causing this error to pop up? I still have about 4GB
> disk
> space left.
> Thanks.|||You may want to check out this link too.
http://support.microsoft.com/defaul...;166840&sd=tech

Saturday, February 25, 2012

"Multiple-Step operation cannot be generated Check each status value" Error

Hi All,

I have a field 'Rowguid' of type uniqueidentifier in a table. This field is the last field in the table. In this case if I update a record through the application I don't get any error. Suppose if there are additional fields after the field Rowguid I get the error "Multiple-Step operation cannot be generated Check each status value"

For your reference I have used the following statement to add the RowGuid field

Alter table <tablename>
Add RowGuid uniqueidentifier ROWGUIDCOL NOT NULL Default (newid())

Can anyone please help me.

Thanks

SatheshPost your update statement, and any trigger code on this table.|||Where's Brett when we need him?

Logically, columns don't have any order within a table. It so happens that the current implementation of Microsoft SQL Server has a physical order, but that's implementation dependant. Relying on a column order (logical or physical) is a bug waiting to happen!

The problem is that you are not specifying a column list for your INSERT statement, you are relying on an implied order. Once you add columns so that the rowid is no longer the last column, your assumed order bytes you. If you specify the columns via a column list, this won't be a problem.DROP TABLE BadExample
GO
CREATE TABLE BadExample (
comment NVARCHAR(25)
)
GO

INSERT INTO BadExample
SELECT 'Simple case'

SELECT * FROM BadExample
GO

ALTER TABLE BadExample
ADD RowGuid uniqueidentifier ROWGUIDCOL NOT NULL
DEFAULT (newid())

INSERT INTO BadExample (comment)
SELECT 'Not as simple example'

SELECT * FROM BadExample
GO

ALTER TABLE BadExample
ADD myDate DATETIME NOT NULL
DEFAULT GetDate()
GO

INSERT INTO BadExample (comment, myDate)
SELECT 'This works!', '1950-01-02'

SELECT * FROM BadExample
GO

INSERT INTO BadExample
SELECT 'This fails', '1960-03-04'

SELECT * FROM BadExample-PatP|||The problem is that you are not specifying a column list for your INSERT statement, you are relying on an implied order.How did you come up with that from his post!?

Thursday, February 9, 2012

"cannot resolve collation conflict for equal to operation" when running view

Get the message "cannot resolve collation conflict for equal to
operation" in a view when a have restored a database on an other
computer. In this view I compare fields from myDB and master. Have
changed so I have the same collation for all my databases om SQL
Server, but still get this problem. Anyone has a suggestion?
//di6pejo
Have you checked that the columns you are comparing actually have the same
collation. Changing the collation of the database does _not_ change the
collation of the columns that exist already in the database, it only
provides a default collation for newly created columns.
Jacco Schalkwijk
SQL Server MVP
"Peter" <ingeskrap@.tjohoo.se> wrote in message
news:3aa71bd7.0407140151.4b78d2d0@.posting.google.c om...
> Get the message "cannot resolve collation conflict for equal to
> operation" in a view when a have restored a database on an other
> computer. In this view I compare fields from myDB and master. Have
> changed so I have the same collation for all my databases om SQL
> Server, but still get this problem. Anyone has a suggestion?
> //di6pejo
|||Big thanks, seem like it worked to change one of the fields is a table.
One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
does "CP1" stands for?
//Peter
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||CP1 stands for codepage 1, which isn't actually codepage 1, but codepage
1252. It is the ANSI standard codepage (loosely translated as character
set), and is used by English and most other Western European languages. For
more information look up "code page" in BOL.
Jacco Schalkwijk
SQL Server MVP
"Pejo" <ingeskrap@.tjohoo.se> wrote in message
news:OuFu3TZaEHA.2520@.TK2MSFTNGP12.phx.gbl...
> Big thanks, seem like it worked to change one of the fields is a table.
> One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
> does "CP1" stands for?
> //Peter
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

"cannot resolve collation conflict for equal to operation" when running view

Get the message "cannot resolve collation conflict for equal to
operation" in a view when a have restored a database on an other
computer. In this view I compare fields from myDB and master. Have
changed so I have the same collation for all my databases om SQL
Server, but still get this problem. Anyone has a suggestion?
//di6pejoHave you checked that the columns you are comparing actually have the same
collation. Changing the collation of the database does _not_ change the
collation of the columns that exist already in the database, it only
provides a default collation for newly created columns.
Jacco Schalkwijk
SQL Server MVP
"Peter" <ingeskrap@.tjohoo.se> wrote in message
news:3aa71bd7.0407140151.4b78d2d0@.posting.google.com...
> Get the message "cannot resolve collation conflict for equal to
> operation" in a view when a have restored a database on an other
> computer. In this view I compare fields from myDB and master. Have
> changed so I have the same collation for all my databases om SQL
> Server, but still get this problem. Anyone has a suggestion?
> //di6pejo|||Big thanks, seem like it worked to change one of the fields is a table.
One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
does "CP1" stands for'
//Peter
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||CP1 stands for codepage 1, which isn't actually codepage 1, but codepage
1252. It is the ANSI standard codepage (loosely translated as character
set), and is used by English and most other Western European languages. For
more information look up "code page" in BOL.
Jacco Schalkwijk
SQL Server MVP
"Pejo" <ingeskrap@.tjohoo.se> wrote in message
news:OuFu3TZaEHA.2520@.TK2MSFTNGP12.phx.gbl...
> Big thanks, seem like it worked to change one of the fields is a table.
> One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
> does "CP1" stands for'
> //Peter
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

Thursday, March 8, 2012

"PRIMARY" filegroup is full

"PRIMARY" filegroup is full

"PRIMARY" filegroup is full

Tuesday, March 6, 2012

"Not enough Storage"

Saturday, February 25, 2012

"Multiple-Step operation cannot be generated Check each status value" Error

Thursday, February 9, 2012

"cannot resolve collation conflict for equal to operation" when running view

"cannot resolve collation conflict for equal to operation" when running view

"cannot resolve collation conflict for equal to operation" when running view

sql error

Blog Archive

About Me