I thought database creation was pretty fast in SQL 2005 and there was no
zero initialization
I ran a create database to create one with an initial size of 25GB for data
file and 25 GB of log file and it ran for 11 mins.
I have the dev edition. Could that be the reason ?
The service account need certain Windows privileges to do fast init. Also fast init is only for data
files (not log files). I've mentioned a few words about it at:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"SQL Server 2005:
SQL Server 2005 has "instant file initialization" which means that database files can be created and
also grow very fast since Windows doesn't "zero out" the data in the database file. Instant file
initialization is only available for data files, not log files. Also, instance file initialization
requires that the service account for the SQL Server service has the SE_MANAGE_VOLUME_NAME windows
privilige, which can be assigned using the Perform Volume Maintenance Tasks security policy. This is
by default only granted to Administrators."
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Hassan" <hassan@.hotmail.com> wrote in message news:eiiizunkHHA.4872@.TK2MSFTNGP03.phx.gbl...
>I thought database creation was pretty fast in SQL 2005 and there was no zero initialization
> I ran a create database to create one with an initial size of 25GB for data file and 25 GB of log
> file and it ran for 11 mins.
> I have the dev edition. Could that be the reason ?
>
>
No comments:
Post a Comment