Re: 'PRIMARY' filegroup is full - no it's not!
From: Mike Epprecht \(SQL MVP\) (mike_at_epprecht.net)
Date: 02/09/05
- Next message: Dale: "Re: 'PRIMARY' filegroup is full - no it's not!"
- Previous message: John Smith: "News Group for SQL2005...."
- In reply to: Dale: "RE: 'PRIMARY' filegroup is full - no it's not!"
- Next in thread: Dale: "Re: 'PRIMARY' filegroup is full - no it's not!"
- Reply: Dale: "Re: 'PRIMARY' filegroup is full - no it's not!"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 9 Feb 2005 21:22:18 +0100
Hi
Yes, you might have it on autogrow, but think about this:
Processes are filling your DB, your DB is virtually full, Autogrow kicks in,
Growing a DB by 10% does take a while, during this time, the last remainder
of the pages gets used up. Bingo, no more space as the DB is still growing.
Primary Group Full gets returned to your processes. The newly allocated
pages are not available for use until the DB has grown fully.
The lesson here. Grow your DB in advance of large operations so that you
don't run into this problem.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dale" <Dale@discussions.microsoft.com> wrote in message
news:64492BF2-BB58-48D5-A458-D1BE70FC9372@microsoft.com...
> We have having the same exact problem. There is 30+ GB Free on the Drive
> (Dynamic Disk, by the way). Database is set to unrestricted file growth.
> Everything looks fine with the configuration of the sql
database...however,
> the database thinks there is no free space on the drive. Very wierd!!
> Database is just shy of 5gb, but General Tab says 0.00Mb Free. Looks
like
> ill be calling MS soon!!
>
> Dale
> txskibum@hotmail.com
>
>
>
> "Ray.Net" wrote:
>
> > I have a SQL Server 2000 database, in which the size of the primary
> > filegroup is 5 GB. The disk where the data resides has 14 GB of free
> > space - that should be more than enough free space for a 5 GB
> > database, right?
> >
> > The problem is that when I perform certain operations (esp. recreating
> > a clustered index), it still seems to run out of space with this
> > error:
> > Could not allocate space for object 'ActivityTracker' in database
> > 'DataLoad' because the 'PRIMARY' filegroup is full. The statement has
> > been terminated.
> >
> > Here's where it gets weird: in the database properties "Automatically
> > grow file" IS checked, and Maximum file size is unrestricted. So
> > there's lots of free space (nearly 3X the size of the db), and the
> > growth is not restricted - what makes it think the filegroup is full?
> >
> > I found a few newsgroup postings that suggested sometimes the
> > auto-grow cannot grow fast enough, so you should manually increase the
> > size of the database. I tried this, using "alter database" to raise
> > the size of the primary filegroup as high as 12GB - more that twice
> > its original 5GB size - but it still fails with the error message
> > above. And - here's another weird thing - at the time the error
> > occurs, the database shrinks itself back down to 5 GB (even though I
> > do NOT have the "Auto shrink" property checked). What's going on
> > here?
> >
> > I appreciate any ideas you can offer on why this database seems to run
> > out of space when there's plenty of space to be had.
> >
> > Ray
> >
- Next message: Dale: "Re: 'PRIMARY' filegroup is full - no it's not!"
- Previous message: John Smith: "News Group for SQL2005...."
- In reply to: Dale: "RE: 'PRIMARY' filegroup is full - no it's not!"
- Next in thread: Dale: "Re: 'PRIMARY' filegroup is full - no it's not!"
- Reply: Dale: "Re: 'PRIMARY' filegroup is full - no it's not!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
