Event ID: 17052 - Urgent

Good afternoon,
I'm getting the error with the Event ID: 17052
with the following text:
Error: 1105, Severity: 17, State: 2
Could not allocate space for object 'X' in database 'Y' because the
'PRIMARY' filegroup is full.
And the processo aborts.
The database has now the size 18093.06MB (17751.75MB[Used] + 341.31MB[Free])
Transaction Log: 5474.12MB (28.42MB[Used] + 5445.7MB[Free])
Server description:
Windows 2000 Server SP4 SQL 2000 SP4
2 CPU Xeon 3.06
2GB RAM
142GB x2 (RAID 1)
It is urgent
Thanks in advance
Regards
Rui MendonçaSome more information:
The folloing error apears too:
Error: 1101, Severity: 17, State: 2
Could not allocate new page for database 'Y'. There are no more pages
available in filegroup PRIMARY. Space can be created by dropping objects,
adding additional files, or allowing file growth.
Please help
Thanks
Regards
Rui Mendonça
"RM" <EurovidaSup@.newsgroups.nospam> wrote in message
news:erKmvMhlGHA.4696@.TK2MSFTNGP05.phx.gbl...
> Good afternoon,
> I'm getting the error with the Event ID: 17052
> with the following text:
> Error: 1105, Severity: 17, State: 2
> Could not allocate space for object 'X' in database 'Y' because the
> 'PRIMARY' filegroup is full.
>
> And the processo aborts.
> The database has now the size 18093.06MB (17751.75MB[Used] +
> 341.31MB[Free])
> Transaction Log: 5474.12MB (28.42MB[Used] + 5445.7MB[Free])
> Server description:
> Windows 2000 Server SP4 SQL 2000 SP4
> 2 CPU Xeon 3.06
> 2GB RAM
> 142GB x2 (RAID 1)
> It is urgent
> Thanks in advance
>
> Regards
> Rui Mendonça
>|||The disk on which your DB resides is full. As an Interim measure, you can
shrink your DB. Also, do you have both the log and the MDF on the same disk.
If so, try shrinking the log file.
--
Venkat
sql server admirer
"RM" wrote:
> Some more information:
> The folloing error apears too:
> Error: 1101, Severity: 17, State: 2
> Could not allocate new page for database 'Y'. There are no more pages
> available in filegroup PRIMARY. Space can be created by dropping objects,
> adding additional files, or allowing file growth.
> Please help
> Thanks
> Regards
> Rui Mendonça
>
> "RM" <EurovidaSup@.newsgroups.nospam> wrote in message
> news:erKmvMhlGHA.4696@.TK2MSFTNGP05.phx.gbl...
> > Good afternoon,
> > I'm getting the error with the Event ID: 17052
> > with the following text:
> > Error: 1105, Severity: 17, State: 2
> >
> > Could not allocate space for object 'X' in database 'Y' because the
> > 'PRIMARY' filegroup is full.
> >
> >
> > And the processo aborts.
> >
> > The database has now the size 18093.06MB (17751.75MB[Used] +
> > 341.31MB[Free])
> > Transaction Log: 5474.12MB (28.42MB[Used] + 5445.7MB[Free])
> >
> > Server description:
> > Windows 2000 Server SP4 SQL 2000 SP4
> > 2 CPU Xeon 3.06
> > 2GB RAM
> > 142GB x2 (RAID 1)
> >
> > It is urgent
> >
> > Thanks in advance
> >
> >
> > Regards
> > Rui Mendonça
> >
>
>|||Hello Rui,
As Venkat mentioned, this issue could occur if disk hosting the database is
full. From your description and size of free space, this is most likely the
cause of the issue. To shrink the database, you can use either DBCC
SHRINKDATABASE or DBCC SHRINKFILE. For more information about how to shrink
a database, please refer to the "Shrinking a database" topic in BOL:
http://msdn.microsoft.com/library/en-us/createdb/cm_8_des_03_3vvp.asp
If you want, you could also move database to new disks with bigger space:
224071 INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/?id=224071
FYI, this issue could also occur if a database was set to a limited size.
Please understand urgent issue is not recommended to handle in newsgroup
because response time may not meet your needs. We encourage you to contact
CSS directly for more immediate assistance:
International Support (non-US/Canada):
http://support.microsoft.com/common/international.aspx
US and Canada:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone
Thank you for your understanding.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Good Morning,
about the free space that I mentioned is refered to the DataBase in
Enterprise Manager. The drive hosting this DB has 22,5GB free space.
More, I use daily the procedures:
BACKUP DATABASE [Y] TO DISK = N'M:\Y.BAK' WITH INIT , NOUNLOAD , NAME =N'Y', SKIP , STATS = 10, NOFORMAT
BACKUP LOG [Y] WITH NO_LOG
DBCC SHRINKDATABASE (Y, TRUNCATEONLY)
So the log remains small...
The issue is not lack of space I believe.
TIA
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:ePWsBrolGHA.132@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> As Venkat mentioned, this issue could occur if disk hosting the database
> is
> full. From your description and size of free space, this is most likely
> the
> cause of the issue. To shrink the database, you can use either DBCC
> SHRINKDATABASE or DBCC SHRINKFILE. For more information about how to
> shrink
> a database, please refer to the "Shrinking a database" topic in BOL:
> http://msdn.microsoft.com/library/en-us/createdb/cm_8_des_03_3vvp.asp
> If you want, you could also move database to new disks with bigger space:
> 224071 INF: Moving SQL Server Databases to a New Location with
> Detach/Attach
> http://support.microsoft.com/?id=224071
> FYI, this issue could also occur if a database was set to a limited size.
> Please understand urgent issue is not recommended to handle in newsgroup
> because response time may not meet your needs. We encourage you to contact
> CSS directly for more immediate assistance:
> International Support (non-US/Canada):
> http://support.microsoft.com/common/international.aspx
> US and Canada:
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone
> Thank you for your understanding.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||I belive it is not a Space issue because the drive hosting the DB has 23GB
free disk space.
The values I mentioned are about the DB.
More, I use daily the procedures:
BACKUP DATABASE [Y] TO DISK = N'M:\Y_Backup.BAK' WITH INIT , NOUNLOAD , NAME
= N'Y', SKIP , STATS = 10, NOFORMAT
BACKUP LOG [Y] WITH NO_LOG
DBCC SHRINKDATABASE (Y, TRUNCATEONLY)
Please follow-up.
TIA
Rui Mendonça
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:ePWsBrolGHA.132@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> As Venkat mentioned, this issue could occur if disk hosting the database
> is
> full. From your description and size of free space, this is most likely
> the
> cause of the issue. To shrink the database, you can use either DBCC
> SHRINKDATABASE or DBCC SHRINKFILE. For more information about how to
> shrink
> a database, please refer to the "Shrinking a database" topic in BOL:
> http://msdn.microsoft.com/library/en-us/createdb/cm_8_des_03_3vvp.asp
> If you want, you could also move database to new disks with bigger space:
> 224071 INF: Moving SQL Server Databases to a New Location with
> Detach/Attach
> http://support.microsoft.com/?id=224071
> FYI, this issue could also occur if a database was set to a limited size.
> Please understand urgent issue is not recommended to handle in newsgroup
> because response time may not meet your needs. We encourage you to contact
> CSS directly for more immediate assistance:
> International Support (non-US/Canada):
> http://support.microsoft.com/common/international.aspx
> US and Canada:
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone
> Thank you for your understanding.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Rui,
Thank you for your update. If we confirm disk size is not the issue, I
recommend you check your database settings and do some modifications:
You could Check whether you allowed automatically grow file and whether you
set the maximum limit on the database.
Use the statement "exec sp_helpdb [database name]" to check; or you can use
"SQL Server Enterprise Manager", right click the database, click
"Properties".
If the option "automatically grow file" was not selected, select it. If
growth rate is 0%, please also change it.
I look forward to your reply.
Thanks & Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello!
"automatically grow file" was OK
"growth rate is 10%"
unrestricted was selected
both MDF & LDF
Thank you very much for your replys.
Meanwhile, I have opened a phone case by Microsoft.
Rui Mendonça
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:A4VeE0qlGHA.4928@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> Thank you for your update. If we confirm disk size is not the issue, I
> recommend you check your database settings and do some modifications:
> You could Check whether you allowed automatically grow file and whether
> you
> set the maximum limit on the database.
> Use the statement "exec sp_helpdb [database name]" to check; or you can
> use
> "SQL Server Enterprise Manager", right click the database, click
> "Properties".
> If the option "automatically grow file" was not selected, select it. If
> growth rate is 0%, please also change it.
> I look forward to your reply.
> Thanks & Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Rui,
Thank you for your update. I would think it shall be more efficient to work
with Microsoft PSS direclty via phone to solve this issue.
Since the database space is already very huge, the 10% growth will also be
a large I/O operation and may last very long. As the space allocation
request is always triggered by the application, when the time-out value is
reach, the application will time out and cause this problem. Also, the
space allocation operation will be rolled back, that is, the file size will
remain the same until next file expansion.
When a database is huge, we recommend the following setting:
1) Disable the auto-shrink and auto-close option of the database.
2) Change the database to ?grow by megabytes? (such as 100M) instead of
?Grow by percent?
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.