Sometimes, its just the smallest of details that can make all the difference. For example, on my test system (see the end of this posting for a description), I created a new 50GB database. The database creation process took about 5 minutes and 50 seconds to complete.
Next, I populated the database with over 61 million rows of data, which virtually occupied all of the available space within the newly created database. After that, I backed up the database using SSMS, and then I deleted the original database.
At this point, I restored the database from the backup using SSMS. Below, you see the typical Restore Database screen.
At the bottom, right-hand side of the screen in the Progress box, notice the “Executing (0%)” indicator. Between the time I clicked the OK button to begin the restore, and when the “Executing (0%)” counter began to move, it took about 5 minutes and 50 seconds. At that point, the counter began to increment and the database was restored.
Now I make one very small change to my SQL Server instance (I’ll describe it in just a moment), and then I repeat the above steps (after deleting the database I just restored). First, I created a new 50GB database. This time, instead of taking 5 minutes and 50 seconds to create the database, it takes just under 2 seconds, a savings of about 5 minutes and 48 seconds. Next, I populated the database with the same amount of data as before, backed it up, and then deleted the original file. When I restored the database this time around, instead of having to wait 5 minutes and 50 seconds before the backup began to restore, I only had to wait just under 2 seconds. In both of these cases, I saved a significant amount of time.
So what was the very small change that I made, and why did it radically reduce the amount of time for database creation and database restoration to occur? I turned instant file initialization on.
What is Instant File Initialization?
In my first two examples, before instance file initialization was turned on, the reason it took so long for the database to be created, or the database to be restored (before a database can be restored, its space must first be pre-allocated, much like creating a new database), SQL Server had to go to every page in the 50 GB database and zero each one of them out. It can take a lot of time for SQL Server to go to every 8K page in a file (especially very large files) and physically zero out each page. When instant file initialization is turned on, SQL Server doesn’t have to zero out every 8K page that has been allocated. Instead, the space is just allocated to SQL Server by the operating system in one fell swoop, which is a very quick process, potentially saving you a great deal of time.
How Do You Turn Instant File Initialization On?
Unlike most configuration features in SQL Server, there is no on/off switch for instant file initialization. Instead, you have to assign a specific user right to the SQL Server Service (mssqlserver) account. Here’s what you need to do to turn on instant file initialization.
First of all, to use instant file initialization with SQL Server in a production environment, you must be using some combination of:
- Windows Server 2003 or
- Windows Server 2008 or
- Windows Server 2008 R2
- SQL Server 2005 (any edition) or
- SQL Server 2008 (any edition) or
- SQL Server 2008 R2 (any edition)
Second, you must assign the SQL Server Service (mssqlserver) a special user right called “Perform volume maintenance tasks”. To do this, start the Local Security Policy tool (you must be a local administrator to perform this task), then drill down to Security Settings | Local Policies | User Rights Assignment | Perform volume maintenance tasks, as you see in the screenshot below.
Once you have located “Perform volume maintenance tasks”, right-click on it and select “Properties”, and the “Perform volume maintenance tasks Properties” screen appears. Click on “Add User or Group” and then proceed through the remaining screens until you select the account that is being used as the service account for SQL Server. In the screen shot below, notice that I have added the BRADMCGEHEEsqlserverservice account to this user rights assignment. This is the user account I use on my test server to run my SQL Server instance.
Once the SQL Server service account has been assigned this user right, you will have to restart the SQL Server service (of course, only when it is not being used), and from this point forward, instant file initialization is turned on for all MDF files in your SQL Server instance.
Note: If your SQL Server service account is a member of the local administrators group, then the account already has the “Perform volume maintenance tasks” user right and you don’t need to assign it again.
Why Isn’t Instant File Initialization Turned On by Default?
When a SQL Server instance is first installed, one of the things you must enter is a SQL Server service account. If you follow the best practice and select a domain user account to be used as the SQL Server service account, the setup process automatically assigns the domain user account with only just enough rights and permissions to run SQL Server. The “Perform volume maintenance tasks” user right is not automatically assigned during installation because it is not required to run SQL Server, and because allowing the service account to have this additional user right introduces a very small security risk.
Oh no, a security risk! Well, not really much of a security risk. Here’s the possible security risk scenario. The disk that is being used to create the new database on has been used for storing data that has been previously deleted. As you may know, when data is deleted from disk by the operating system, it really is not physically deleted; the space holding the data is just marked as being available. At some point, the older data will be overwritten with new data. This occurs all the time on millions of computers throughout the world every day. And as such, any data that has been marked for deletion, but not yet overwritten, is potentially available for access if you have the right tools and know what you are doing. In fact, undelete software uses this to recover data that has been accidently deleted.
When instant file initialization is not turned on, and when SQL Server allocates space for an MDF file, each of the pages allocated for the database is
zeroed out, which removes the older data, in theory, preventing it from being accessed. I say “in theory” because there are computer forensics techniques that can even recover data that has been overwritten, but that discussion is really not applicable here.
So if instant file initialization is turned on, there is a very slight risk that someone could go to the pages allocated for the new database and read any older data that still may exist there. This is essentially a non-issue in virtually every organization, other than those that require very high security. But because of this potential security issue, instant file initialization is not turned on by default.
If instant file initialization is turned on, and pages are not zeroed out when the database is initially created, SQL Server will automatically overwrite any data that might have been on those pages when SQL Server needs that space.
When Is Instant File Initialization Used?
If instant file initialization is turned on, it is used in all of these cases:
- When a database is first created
- When a an existing database’s size is manually increased
- When tempdb is recreated each time SQL Server is restarted
- When autogrowth kicks in
- When backups are restored (as the space has to be pre-allocated before a restore can occur)
Instant file initialization only affects MDF and NDF files, not LDF files. In other words, transaction log files can’t take advantage of instant file initialization. This is because log files are circular in nature and must be zeroed out, as random data in transaction log pages can be problematic. In my earlier test, when I created a new 50 GB database, the MDF file was 50 GB and the log file was only 1 MB. If I had created a large log file (which is not uncommon), it would have taken awhile for the log to be created, although the MDF file would have been instantly created. This is also true when you manually increase the size of a log file, or when log file autogrowth occurs. In other words, don’t expect to have all of your databases (MDF and LDF files) created in less than 2 seconds like in my test. While the MDF will be created virtually instantly, the log file may take awhile to be created.
When I was working with SQL Server 2000 a few years back, which does not support instant file initialization, one of the things that annoyed me the most when restoring large databases was waiting for the database space to be allocated before the restore actually began. During emergency database restores, this wasted a lot of precious time, preventing me from getting the database back into production as fast as I would have preferred. If you aren’t using instant file initialization today, you are facing this same problem. That’s why I recommend all SQL Server 2005/2008 instances have instant file initialization turned on. The time saved when restoring databases is the best reason to use instant file initialization.
Check to See if Your SQL Server Instances Have Instant File Initialization Turned On
Hopefully, by now, you see the benefits of using instant file initialization. Assuming that you don’t already know if instant file initialization is turned on or off on the SQL Servers your manage, I challenge you to check and see, and if you find it turned off, turn it on and reap its many benefits.
- Dell T610 Tower, with a single, 6-core CPU (Intel Xeon X5670, 2.93 Ghz, 12M Cache, HT, 1333MHz FSB); 32GB 1333MHz RAM; a PERC H700 RAID controller; two 146GB 15K SAS Drives; one dual-port HBA (to connect to the DAS); and dual network connections. Hyper-threading turned off.
- One PowerVault MD3000 DAS with two, dual-port controllers, and 15 146GB 15K SAS drives. MDF files located on RAID 10 array with 10 spindles, LDF files on RAID 10 array with 4 spindles, backup drive on a single spindle.
11 thoughts on “Instant File Initialization Speeds SQL Server”
Pingback: Tweets that mention Instant File Initialization Speeds SQL Server | SQL Aloha -- Topsy.com
Nice post Brad,
I find the quickest way to open up “Local Security Policy” is to run “secpol.msc” from the cmd prompt.
Hi Brad, this is a great tip and is often one that gets overlooked, particularly in large environments where the DBA may not necessarily be responsible for the initial server build.
There is a post over on Paul Randal’s blog that provides a method to check if the required permissions have been given to the SQL Server Service account, which may also be of interest to readers.
Glad to see this item is included on your SQL Server Instance checklist. All of your checklists are fantastic resources by the way so thanks for taking the time to build and share them with the community!
Just a note, instead of specifying the actual service account, Microsoft recommends granting it to the Local Machine User Group that gets created during the installation of SQL, SQLServer2005MSSQLUser$[SERVERNAME]$MSSQLSERVER.
That way, if you change service accounts credentials via the SQL Server Configuration Manager, the new service account will automatically be granted the rights to do Instant File Initialization.
@Jose A. Hernandez: I think that’s a great suggestion, thanks!
Pingback: SQL Server Links and news this week | John Sansom - SQL Server DBA in the UK
Does this apply when you have a SAN or other “smart disk” device such as our Netapp?
Hi Randy, I can answer this for you……
Yes it still applies.
Instant File Initialization is a method of allocating storage space on the IO subsystem that is independent of the storage technology being used.
Thanks John. Maybe I’ll post this on a Netapp forum because I’m not making any headway on persuading our Systems group that this makes any difference on a Netapp.
Randy, I agree 100% with John.
A greate article, Brad alway brings new things.
Comments are closed.