I have an issue about the Automatically Grow File property in the SQL Server
2000.
We have a database with 1.3 GB, the option Automatically Grow File is
selected growing in 50 Mb. This database keeps the application data about 3
years.
I heard somewhere that the performance will be better if I would create two
Database Files.
The first one should has 1.5 Gb and the option Automatically Grow File
*unselected* and the second one should has 100 Mb and the option
Automatically Grow File *selected*, growing in 50 Mb. Also, each time the
second file is used I should reorganize/shrink the database to release space
enough or increase the size of the first database file manually. They say
that because, if the option Automatically Grow File is selected, each time
you insert a record in a table the SQL Server needs to verify if there is
enough free space in the database file.
Is that plausible?
Is there really this high cost each time you insert a record in a table?
Thanks in advance.
Marcos
No. That's not really a consideration on what you do with
your file configurations. SQL Server checks the PFS pages to
find the space to insert new rows no matter what the growth
settings are.
The following article has performance implications of
autogrow, autoshrink settings:
INF: Considerations for Autogrow and Autoshrink
configuration in SQL Server
http://support.microsoft.com/?id=315512
-Sue
On Thu, 9 Mar 2006 09:29:29 -0800, Marcos
<Marcos@.discussions.microsoft.com> wrote:
>I have an issue about the Automatically Grow File property in the SQL Server
>2000.
>We have a database with 1.3 GB, the option Automatically Grow File is
>selected growing in 50 Mb. This database keeps the application data about 3
>years.
>I heard somewhere that the performance will be better if I would create two
>Database Files.
>The first one should has 1.5 Gb and the option Automatically Grow File
>*unselected* and the second one should has 100 Mb and the option
>Automatically Grow File *selected*, growing in 50 Mb. Also, each time the
>second file is used I should reorganize/shrink the database to release space
>enough or increase the size of the first database file manually. They say
>that because, if the option Automatically Grow File is selected, each time
>you insert a record in a table the SQL Server needs to verify if there is
>enough free space in the database file.
>Is that plausible?
>Is there really this high cost each time you insert a record in a table?
>Thanks in advance.
>Marcos
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment