|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > Data files growth
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]
|
|
|
| We have a SQL 7 database with 3 data files in the primary filegroup.
The files have all been allocated 65GBs each and set for unrestricted
file growth in 500MB increments. There is plenty of space on the
drive where these files are. The question is what will happen if
these files all consume 65GBs? Will the files grow beyond the 65GBs
even though that is all of the space that has been allocated to them
even thought they are set for unrestricted file growth?
Two of the files have all most reached the allocated space but one is
14GBs away. Will the database grind to a halt or continue to grow?
Thanks,
Greg
| |
| Keith Kratochvil 2002-11-20, 2:23 pm |
| It sounds like you created your database with three data files.
You initialized each data file to 65GB (and they started out empty).
You have been adding data....and two of the files are "close" to the initial
size (65GB) and the third has some room to grow.
From the way it sounds you have free space on your data volume(s) -- so your
database could grow.
You are asking "will they grow?"
yes
Since they are set to unrestricted file growth, they will keep growing until
they cannot grow any more (this will happen when you are out of disk space).
Growing the files in 500MB increments might be extreme. While the database
is expanding certain actions will be held up while SQL Server allocates the
additional size. Depending on the type/quality of the drive/raid array this
operation could be transparent, or it could cause slowdowns/blocking due to
queueing. You might want to have the files grow at a smaller rate (100MB)
or manually increase them as needed.
--
Keith, SQL Server MVP
"Greg" <gjackson@thq.com> wrote in message
news:nrkntucrh03ke6teuvgb7gg81
d5f8k3u6a@4ax.com...
> We have a SQL 7 database with 3 data files in the primary filegroup.
> The files have all been allocated 65GBs each and set for unrestricted
> file growth in 500MB increments. There is plenty of space on the
> drive where these files are. The question is what will happen if
> these files all consume 65GBs? Will the files grow beyond the 65GBs
> even though that is all of the space that has been allocated to them
> even thought they are set for unrestricted file growth?
> Two of the files have all most reached the allocated space but one is
> 14GBs away. Will the database grind to a halt or continue to grow?
>
> Thanks,
> Greg
| |
|
| That's the situation exactly. Two files are basically full but the
last one has 16GBs available. If I want to manually increase the size
of the two files that are full, how will this affect users? Will I
need to schedule this for a slow time? All files are on the same
drive.
Thanks for the help,
Greg
On Wed, 20 Nov 2002 14:14:10 -0600, "Keith Kratochvil"
<keith.kratochvil.back2u@novusprintmedia.com> wrote:
>It sounds like you created your database with three data files.
>You initialized each data file to 65GB (and they started out empty).
>
>You have been adding data....and two of the files are "close" to the initial
>size (65GB) and the third has some room to grow.
>
>From the way it sounds you have free space on your data volume(s) -- so your
>database could grow.
>
>You are asking "will they grow?"
>
>yes
>Since they are set to unrestricted file growth, they will keep growing until
>they cannot grow any more (this will happen when you are out of disk space).
>
>Growing the files in 500MB increments might be extreme. While the database
>is expanding certain actions will be held up while SQL Server allocates the
>additional size. Depending on the type/quality of the drive/raid array this
>operation could be transparent, or it could cause slowdowns/blocking due to
>queueing. You might want to have the files grow at a smaller rate (100MB)
>or manually increase them as needed.
| |
| Keith Kratochvil 2002-11-20, 4:23 pm |
| You can grow the files while people are in the system, but I would recommend
that you pick a slower time of the day just to minimize impact.
--
Keith, SQL Server MVP
"Greg" <gjackson@thq.com> wrote in message
news:a4vntuo135lddv2k9re15jtue
f9tmmtvhh@4ax.com...
> That's the situation exactly. Two files are basically full but the
> last one has 16GBs available. If I want to manually increase the size
> of the two files that are full, how will this affect users? Will I
> need to schedule this for a slow time? All files are on the same
> drive.
>
> Thanks for the help,
> Greg
>
> On Wed, 20 Nov 2002 14:14:10 -0600, "Keith Kratochvil"
> <keith.kratochvil.back2u@novusprintmedia.com> wrote:
>
> >It sounds like you created your database with three data files.
> >You initialized each data file to 65GB (and they started out empty).
> >
> >You have been adding data....and two of the files are "close" to the
initial
> >size (65GB) and the third has some room to grow.
> >
> >From the way it sounds you have free space on your data volume(s) -- so
your
> >database could grow.
> >
> >You are asking "will they grow?"
> >
> >yes
> >Since they are set to unrestricted file growth, they will keep growing
until
> >they cannot grow any more (this will happen when you are out of disk
space).
> >
> >Growing the files in 500MB increments might be extreme. While the
database
> >is expanding certain actions will be held up while SQL Server allocates
the
> >additional size. Depending on the type/quality of the drive/raid array
this
> >operation could be transparent, or it could cause slowdowns/blocking due
to
> >queueing. You might want to have the files grow at a smaller rate
(100MB)
> >or manually increase them as needed.
>
|
|
|
|
|