|
Home > Archive > microsoft.public.sqlserver.server > August 2002 > filegroup is full
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hello.
One of my scheduled job failed, I got the following
message: Could not allocate space for object TABLE NAME in
database DB NAME because the PRIMARY filegroup is full.
I have almost 20GB of free space on the dirve where are
the database files.
Does any one konw how to resolve that problem?
Thank you
| |
| Wayne Snyder 2002-08-14, 9:23 am |
| A filegroup is full when
1. the disk on which its files live become full OR
2. The MAXSIZE of the files have been reached.
Go to Sql Enterprise Manager -> Databases -> properties and check/change the
maxsize of your data files.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it community
of SQL Server professionals.
www.sqlpass.org
"nicky" <nicky@hotmail.com> wrote in message
news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
> Hello.
>
> One of my scheduled job failed, I got the following
> message: Could not allocate space for object TABLE NAME in
> database DB NAME because the PRIMARY filegroup is full.
> I have almost 20GB of free space on the dirve where are
> the database files.
>
> Does any one konw how to resolve that problem?
>
> Thank you
| |
| Tibor Karaszi 2002-08-14, 9:23 am |
| I suggest pre-allocating storage. I've seen cases where autogrow doesn't seem to "catch up".
Also, gives better performance.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ublic.sqlserver
"nicky" <nicky@hotmail.com> wrote in message news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
> Hello.
>
> One of my scheduled job failed, I got the following
> message: Could not allocate space for object TABLE NAME in
> database DB NAME because the PRIMARY filegroup is full.
> I have almost 20GB of free space on the dirve where are
> the database files.
>
> Does any one konw how to resolve that problem?
>
> Thank you
| |
| Nicky 2002-08-14, 10:23 am |
| Hello Tibor.
What do you mean by pre-allocating storage?
Thank you.
>-----Original Message-----
>I suggest pre-allocating storage. I've seen cases where
autogrow doesn't seem to "catch up".
>Also, gives better performance.
>
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>
>"nicky" <nicky@hotmail.com> wrote in message
news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
>> Hello.
>>
>> One of my scheduled job failed, I got the following
>> message: Could not allocate space for object TABLE NAME
in
>> database DB NAME because the PRIMARY filegroup is full.
>> I have almost 20GB of free space on the dirve where are
>> the database files.
>>
>> Does any one konw how to resolve that problem?
>>
>> Thank you
>
>
>.
>
| |
| nicky 2002-08-14, 10:23 am |
| Hello Wayne.
I still have 20GB free on that drive and the
option 'unrestricted filegrowth' is checked.
>-----Original Message-----
>A filegroup is full when
>1. the disk on which its files live become full OR
>2. The MAXSIZE of the files have been reached.
>
>Go to Sql Enterprise Manager -> Databases -> properties
and check/change the
>maxsize of your data files.
>
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>
>I support the Professional Association of SQL Server
(PASS) and it community
>of SQL Server professionals.
>www.sqlpass.org
>
>"nicky" <nicky@hotmail.com> wrote in message
> news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
>> Hello.
>>
>> One of my scheduled job failed, I got the following
>> message: Could not allocate space for object TABLE NAME
in
>> database DB NAME because the PRIMARY filegroup is full.
>> I have almost 20GB of free space on the dirve where are
>> the database files.
>>
>> Does any one konw how to resolve that problem?
>>
>> Thank you
>
>
>.
>
| |
|
| He means setting the size of the db large enough so that it doesnt have to
autogrow before you run your process.
"Nicky" <Nicky@hotmail.com> wrote in message
news:24b901c243a7$f7de36d0$b1e
62ecf@tkmsftngxa04...
> Hello Tibor.
>
> What do you mean by pre-allocating storage?
>
> Thank you.
>
> >-----Original Message-----
> >I suggest pre-allocating storage. I've seen cases where
> autogrow doesn't seem to "catch up".
> >Also, gives better performance.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"nicky" <nicky@hotmail.com> wrote in message
> news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
> >> Hello.
> >>
> >> One of my scheduled job failed, I got the following
> >> message: Could not allocate space for object TABLE NAME
> in
> >> database DB NAME because the PRIMARY filegroup is full.
> >> I have almost 20GB of free space on the dirve where are
> >> the database files.
> >>
> >> Does any one konw how to resolve that problem?
> >>
> >> Thank you
> >
> >
> >.
> >
| |
| Nicky 2002-08-14, 11:23 am |
|
I am shrinking the database every day so the database has
to growth every day. It has been working like that for
almost 2 years without any problem. Today the data file
reached the size of 12 505.56MB and was not able to
growth more even if the is free space on the disk and no
max set up. I cleaned up the data base to down size the
file, shrinked the database (to 7 589MB) and every thing
is working again.
I just want to understand if there is a maximun size for
the data file?
Should I avoid to shrink the database every day?
Thank you for all you answers!
Nicky
>-----Original Message-----
>He means setting the size of the db large enough so that
it doesnt have to
>autogrow before you run your process.
>"Nicky" <Nicky@hotmail.com> wrote in message
> news:24b901c243a7$f7de36d0$b1e
62ecf@tkmsftngxa04...
>> Hello Tibor.
>>
>> What do you mean by pre-allocating storage?
>>
>> Thank you.
>>
>> >-----Original Message-----
>> >I suggest pre-allocating storage. I've seen cases where
>> autogrow doesn't seem to "catch up".
>> >Also, gives better performance.
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >Archive at: http://groups.google.com/groups?
>> oi=djq&as_ugroup=microsoft.public.sqlserver
>> >
>> >
>> >"nicky" <nicky@hotmail.com> wrote in message
>> news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
>> >> Hello.
>> >>
>> >> One of my scheduled job failed, I got the following
>> >> message: Could not allocate space for object TABLE
NAME
>> in
>> >> database DB NAME because the PRIMARY filegroup is
full. [colo
r=darkred]
>> >> I have almost 20GB of free space on the dirve where[/color]
are[c
olor=darkred]
>> >> the database files.
>> >>
>> >> Does any one konw how to resolve that problem?
>> >>
>> >> Thank you
>> >
>> >
>> >.
>> >
>
>
>.
>[/color]
| |
| Andrew J. Kelly 2002-08-14, 12:23 pm |
| Nicky,
You should definitely not shrink the DB each night. Why shrink it when you
know it will grow again the next day? That is very intensive work for the
server and not very efficient for the DB overall. What version are you
using? There was an issue (I think 7.0?) where the DB could not grow fast
enough for the actions under certain conditions. Bottom line is to make
your DB as large as you will need for regular operation and only manually
grow it when you anticipate needing more room. That doesn't mean to turn
off Autogrow though.
--
Andrew J. Kelly SQL MVP
Targitinteractive, Inc.
"Nicky" <nicky@hotmail.com> wrote in message
news:0b6a01c243b3$5406bd50$9be
62ecf@tkmsftngxa03...
>
>
> I am shrinking the database every day so the database has
> to growth every day. It has been working like that for
> almost 2 years without any problem. Today the data file
> reached the size of 12 505.56MB and was not able to
> growth more even if the is free space on the disk and no
> max set up. I cleaned up the data base to down size the
> file, shrinked the database (to 7 589MB) and every thing
> is working again.
>
> I just want to understand if there is a maximun size for
> the data file?
> Should I avoid to shrink the database every day?
>
> Thank you for all you answers!
> Nicky
>
> >-----Original Message-----
> >He means setting the size of the db large enough so that
> it doesnt have to
> >autogrow before you run your process.
> >"Nicky" <Nicky@hotmail.com> wrote in message
> > news:24b901c243a7$f7de36d0$b1e
62ecf@tkmsftngxa04...
> >> Hello Tibor.
> >>
> >> What do you mean by pre-allocating storage?
> >>
> >> Thank you.
> >>
> >> >-----Original Message-----
> >> >I suggest pre-allocating storage. I've seen cases where
> >> autogrow doesn't seem to "catch up".
> >> >Also, gives better performance.
> >> >
> >> >--
> >> >Tibor Karaszi, SQL Server MVP
> >> >Archive at: http://groups.google.com/groups?
> >> oi=djq&as_ugroup=microsoft.public.sqlserver
> >> >
> >> >
> >> >"nicky" <nicky@hotmail.com> wrote in message
> >> news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
> >> >> Hello.
> >> >>
> >> >> One of my scheduled job failed, I got the following
> >> >> message: Could not allocate space for object TABLE
> NAME
> >> in
> >> >> database DB NAME because the PRIMARY filegroup is
> full.
> >> >> I have almost 20GB of free space on the dirve where
> are
> >> >> the database files.
> >> >>
> >> >> Does any one konw how to resolve that problem?
> >> >>
> >> >> Thank you
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
| |
|
| Hello Andrew.
I was thought that I have to shrink the database every day
to recuperate all half empty pages. Is that true?
Thank you for your help!
>-----Original Message-----
>Nicky,
>
>You should definitely not shrink the DB each night. Why
shrink it when you
>know it will grow again the next day? That is very
intensive work for the
>server and not very efficient for the DB overall. What
version are you
>using? There was an issue (I think 7.0?) where the DB
could not grow fast
>enough for the actions under certain conditions. Bottom
line is to make
>your DB as large as you will need for regular operation
and only manually
>grow it when you anticipate needing more room. That
doesn't mean to turn
>off Autogrow though.
>
>--
>Andrew J. Kelly SQL MVP
>Targitinteractive, Inc.
>
>
>
>"Nicky" <nicky@hotmail.com> wrote in message
> news:0b6a01c243b3$5406bd50$9be
62ecf@tkmsftngxa03...
>>
>>
>> I am shrinking the database every day so the database
has
>> to growth every day. It has been working like that for
>> almost 2 years without any problem. Today the data file
>> reached the size of 12 505.56MB and was not able to
>> growth more even if the is free space on the disk and no
>> max set up. I cleaned up the data base to down size the
>> file, shrinked the database (to 7 589MB) and every thing
>> is working again.
>>
>> I just want to understand if there is a maximun size for
>> the data file?
>> Should I avoid to shrink the database every day?
>>
>> Thank you for all you answers!
>> Nicky
>>
>> >-----Original Message-----
>> >He means setting the size of the db large enough so
that
>> it doesnt have to
>> >autogrow before you run your process.
>> >"Nicky" <Nicky@hotmail.com> wrote in message
>> > news:24b901c243a7$f7de36d0$b1e
62ecf@tkmsftngxa04...
>> >> Hello Tibor.
>> >>
>> >> What do you mean by pre-allocating storage?
>> >>
>> >> Thank you.
>> >>
>> >> >-----Original Message-----
>> >> >I suggest pre-allocating storage. I've seen cases
where
>> >> autogrow doesn't seem to "catch up".
>> >> >Also, gives better performance.
>> >> >
>> >> >--
>> >> >Tibor Karaszi, SQL Server MVP
>> >> >Archive at: http://groups.google.com/groups?
>> >> oi=djq&as_ugroup=microsoft.public.sqlserver
>> >> >
>> >> >
>> >> >"nicky" <nicky@hotmail.com> wrote in message
>> >> news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
>> >> >> Hello.
>> >> >>
>> >> >> One of my scheduled job failed, I got the
following
>> >> >> message: Could not allocate space for object TABLE
>> NAME
>> >> in
>> >> >> database DB NAME because the PRIMARY filegroup is
>> full.
>> >> >> I have almost 20GB of free space on the dirve
where
>> are
>> >> >> the database files.
>> >> >>
>> >> >> Does any one konw how to resolve that problem?
>> >> >>
>> >> >> Thank you
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>
| |
| Andrew J. Kelly 2002-08-14, 6:23 pm |
| That is what a Clustered Index and DBCC DBREINDEX or DBCC INDEXDEFRAG will
do for you without having to shrink the DB.
--
Andrew J. Kelly, SQL Server MVP
TargitInteractive
"nicky" <nicky@hotmail.com> wrote in message
news:287701c243dd$d1575470$3be
f2ecf@TKMSFTNGXA10...
> Hello Andrew.
>
> I was thought that I have to shrink the database every day
> to recuperate all half empty pages. Is that true?
>
> Thank you for your help!
>
> >-----Original Message-----
> >Nicky,
> >
> >You should definitely not shrink the DB each night. Why
> shrink it when you
> >know it will grow again the next day? That is very
> intensive work for the
> >server and not very efficient for the DB overall. What
> version are you
> >using? There was an issue (I think 7.0?) where the DB
> could not grow fast
> >enough for the actions under certain conditions. Bottom
> line is to make
> >your DB as large as you will need for regular operation
> and only manually
> >grow it when you anticipate needing more room. That
> doesn't mean to turn
> >off Autogrow though.
> >
> >--
> >Andrew J. Kelly SQL MVP
> >Targitinteractive, Inc.
> >
> >
> >
> >"Nicky" <nicky@hotmail.com> wrote in message
> > news:0b6a01c243b3$5406bd50$9be
62ecf@tkmsftngxa03...
> >>
> >>
> >> I am shrinking the database every day so the database
> has
> >> to growth every day. It has been working like that for
> >> almost 2 years without any problem. Today the data file
> >> reached the size of 12 505.56MB and was not able to
> >> growth more even if the is free space on the disk and no
> >> max set up. I cleaned up the data base to down size the
> >> file, shrinked the database (to 7 589MB) and every thing
> >> is working again.
> >>
> >> I just want to understand if there is a maximun size for
> >> the data file?
> >> Should I avoid to shrink the database every day?
> >>
> >> Thank you for all you answers!
> >> Nicky
> >>
> >> >-----Original Message-----
> >> >He means setting the size of the db large enough so
> that
> >> it doesnt have to
> >> >autogrow before you run your process.
> >> >"Nicky" <Nicky@hotmail.com> wrote in message
> >> > news:24b901c243a7$f7de36d0$b1e
62ecf@tkmsftngxa04...
> >> >> Hello Tibor.
> >> >>
> >> >> What do you mean by pre-allocating storage?
> >> >>
> >> >> Thank you.
> >> >>
> >> >> >-----Original Message-----
> >> >> >I suggest pre-allocating storage. I've seen cases
> where
> >> >> autogrow doesn't seem to "catch up".
> >> >> >Also, gives better performance.
> >> >> >
> >> >> >--
> >> >> >Tibor Karaszi, SQL Server MVP
> >> >> >Archive at: http://groups.google.com/groups?
> >> >> oi=djq&as_ugroup=microsoft.public.sqlserver
> >> >> >
> >> >> >
> >> >> >"nicky" <nicky@hotmail.com> wrote in message
> >> >> news:20d801c243a2$221268f0$2ae
2c90a@phx.gbl...
> >> >> >> Hello.
> >> >> >>
> >> >> >> One of my scheduled job failed, I got the
> following
> >> >> >> message: Could not allocate space for object TABLE
> >> NAME
> >> >> in
> >> >> >> database DB NAME because the PRIMARY filegroup is
> >> full.
> >> >> >> I have almost 20GB of free space on the dirve
> where
> >> are
> >> >> >> the database files.
> >> >> >>
> >> >> >> Does any one konw how to resolve that problem?
> >> >> >>
> >> >> >> Thank you
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
|
|
|
|
|