Hi!
I have a database (12Gb) that is configured to automatically grow with 10 %,
unrestricted file growth and a lot of space left on disk. SQL2000 ENT ed.
When the file becomes full the event log alarms with the message: Could not
allocate space for object '' in database '' because the 'PRIMARY' filegroup
is full.
Why does not the file automatically grow'
Someone out there having the same experience?
/Christofer FranssonBOL says
Updates information about the distribution of key values for one or more
statistics groups (collections) in the specified table or indexed view. To
create statistics on columns
Look , I will try to explain what happened as I'm understanding it
Your database is set up in Autgow method by 10 percent for example. Each
process/transaction is filling the database and when this (Autogrow) feature
kicks in ,SQL Server needs to allocate free space and new datapages in the
datafile
Once it found it marks it as 'occupied'. While your database growing it
does take some time and process has to wait and at this time as all new
datapage is 'occupied' , the system throws the error
I hope you get the idea
"christofer fransson" <christoferfransson@.discussions.microsoft.com> wrote
in message news:C8840E12-8AC3-46AD-9342-5BFD7FAA1362@.microsoft.com...[vbcol=seagreen]
> The tempdb is not a problem it has enough space.
> What does the update statistics do in this case?
> "Uri Dimant" wrote:
>|||Verify that 'Maximum Size' for the Data File is not set to the Current Size
of the Data File.
"christofer fransson" wrote:
> Hi!
> I have a database (12Gb) that is configured to automatically grow with 10
%,
> unrestricted file growth and a lot of space left on disk. SQL2000 ENT ed.
> When the file becomes full the event log alarms with the message: Could no
t
> allocate space for object '' in database '' because the 'PRIMARY' filegrou
p
> is full.
> Why does not the file automatically grow'
> Someone out there having the same experience?
>
> /Christofer Fransson|||Have you tried manually growing the file?
Could there be an NT restriction eg a quota
Paul
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%236J7vBUPGHA.2888@.tk2msftngp13.phx.gbl...
> BOL says
> Updates information about the distribution of key values for one or more
> statistics groups (collections) in the specified table or indexed view. To
> create statistics on columns
> Look , I will try to explain what happened as I'm understanding it
> Your database is set up in Autgow method by 10 percent for example. Each
> process/transaction is filling the database and when this (Autogrow)
> feature kicks in ,SQL Server needs to allocate free space and new
> datapages in the datafile
> Once it found it marks it as 'occupied'. While your database growing it
> does take some time and process has to wait and at this time as all new
> datapage is 'occupied' , the system throws the error
> I hope you get the idea
>
>
>
> "christofer fransson" <christoferfransson@.discussions.microsoft.com> wrote
> in message news:C8840E12-8AC3-46AD-9342-5BFD7FAA1362@.microsoft.com...
>|||Paul
http://www.sql-server-performance.c...se_settings.asp
"Paul Cahill" <anon@.anon.com> wrote in message
news:ewZOlZUPGHA.2124@.TK2MSFTNGP14.phx.gbl...
> Have you tried manually growing the file?
> Could there be an NT restriction eg a quota
> Paul
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%236J7vBUPGHA.2888@.tk2msftngp13.phx.gbl...
>|||What is the timing?
Basically, at 12GB your growth will be 1.2GB. As was pointed out, SS has to
'initialize' each block in that growth. It takes time to write 1.2GB. WHile
that is happening, processes can't write to the db.
How long it will take to do the initialization depends on your box and disk
speeds.
How long have you waited to see if the problem 'fixes itself'? If less than
1/2 hour (again depending on box and disks), you may not have given it enoug
h
time.)
I suggest a different growth pattern of , say 16MB at a time instead of
exponential % growth.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Absar Ahmad" wrote:
[vbcol=seagreen]
> Verify that 'Maximum Size' for the Data File is not set to the Current Siz
e
> of the Data File.
> "christofer fransson" wrote:
>|||Run UPDATESTATISTICS command (see in the BOL)
I'd check a size of TEMPDB as well
"christofer fransson" <christoferfransson@.discussions.microsoft.com> wrote
in message news:CC9B7757-7D25-4D3D-BBE5-452DAAD71F2E@.microsoft.com...
> Hi!
> I have a database (12Gb) that is configured to automatically grow with 10
> %,
> unrestricted file growth and a lot of space left on disk. SQL2000 ENT ed.
> When the file becomes full the event log alarms with the message: Could
> not
> allocate space for object '' in database '' because the 'PRIMARY'
> filegroup
> is full.
> Why does not the file automatically grow'
> Someone out there having the same experience?
>
> /Christofer Fransson|||The tempdb is not a problem it has enough space.
What does the update statistics do in this case?
"Uri Dimant" wrote:
> Run UPDATESTATISTICS command (see in the BOL)
> I'd check a size of TEMPDB as well
>
> "christofer fransson" <christoferfransson@.discussions.microsoft.com> wrote
> in message news:CC9B7757-7D25-4D3D-BBE5-452DAAD71F2E@.microsoft.com...
>
>
