Showing posts with label disk. Show all posts
Showing posts with label disk. Show all posts

Thursday, March 8, 2012

Datafiles placement in filegroup

I'm working with a production database connecting remotely. All the datafile
s, index files and log is placed on the same disk but in different filegroup
names based on separate physical files. But I expect if I place the index f
iles or/add log files sep
arate from the datafiles I mean in different disk it will improve the perfor
mance.
If my expectation is correct then can I change the place of the index and lo
g files in separate location while the database is on-line yes the database
is implemented with log-shipping too.
Please evaluate my query and do give a proper suggestion.
Thanks in advance
Sunilsurely it will improve the performance if the log files are placed seperate
from the data files (different disks).
for the indexes u can delete the existing index and recreate it specifying
the new location.
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:4690C174-4988-4737-82D9-7C0ED08FDF5D@.microsoft.com...
quote:

> I'm working with a production database connecting remotely. All the

datafiles, index files and log is placed on the same disk but in different
filegroup names based on separate physical files. But I expect if I place
the index files or/add log files separate from the datafiles I mean in
different disk it will improve the performance.
quote:

> If my expectation is correct then can I change the place of the index and

log files in separate location while the database is on-line yes the
database is implemented with log-shipping too.
quote:

>
> Please evaluate my query and do give a proper suggestion.
>
> Thanks in advance
> Sunil
>

Datafiles placement in filegroup

I'm working with a production database connecting remotely. All the datafiles, index files and log is placed on the same disk but in different filegroup names based on separate physical files. But I expect if I place the index files or/add log files separate from the datafiles I mean in different disk it will improve the performance.
If my expectation is correct then can I change the place of the index and log files in separate location while the database is on-line yes the database is implemented with log-shipping too.
Please evaluate my query and do give a proper suggestion.
Thanks in advance
Sunilsurely it will improve the performance if the log files are placed seperate
from the data files (different disks).
for the indexes u can delete the existing index and recreate it specifying
the new location.
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:4690C174-4988-4737-82D9-7C0ED08FDF5D@.microsoft.com...
> I'm working with a production database connecting remotely. All the
datafiles, index files and log is placed on the same disk but in different
filegroup names based on separate physical files. But I expect if I place
the index files or/add log files separate from the datafiles I mean in
different disk it will improve the performance.
> If my expectation is correct then can I change the place of the index and
log files in separate location while the database is on-line yes the
database is implemented with log-shipping too.
>
> Please evaluate my query and do give a proper suggestion.
>
> Thanks in advance
> Sunil
>|||You are mostly correct.
Creating new files doesn't automatically improve
performace, it also depends upon the raid configuration of
the disk its going on.
For instance putting a log file on a RAID 0 disk will make
it faster than putting it on a raid 5 disk.
Although its different for every type of application a
normal implementation with cost constraints its to put the
log files on a raid 0 or raid 0+1 with the data files on
raid 5.
J
>--Original Message--
>I'm working with a production database connecting
remotely. All the datafiles, index files and log is placed
on the same disk but in different filegroup names based on
separate physical files. But I expect if I place the index
files or/add log files separate from the datafiles I
mean in different disk it will improve the performance.
>If my expectation is correct then can I change the place
of the index and log files in separate location while the
database is on-line yes the database is implemented with
log-shipping too.
>
>Please evaluate my query and do give a proper suggestion.
>
>Thanks in advance
>Sunil
>.
>

Sunday, February 19, 2012

Databasefile can not automatically grow

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
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...
>
>
|||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...[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 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
|||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.co...e_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 enough
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 Size
> of the Data File.
> "christofer fransson" wrote:

Databasefile can not automatically grow

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 FranssonRun 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...
> > 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
>
>|||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...
> 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...
>> > 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
>>|||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 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|||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...
>> 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...
>> > 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
>>
>|||Paul
http://www.sql-server-performance.com/database_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...
>> 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...
>> 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...
>> > 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
>>
>>
>|||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 enough
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:
> 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 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

Databasefile can not automatically grow

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

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
--
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.