Archive | Instant File Initialization RSS feed for this section

Setting Instant File Initialization

6 Jun

In a previous article I showed how to detect if Instant File Initialization (IFI) has been set.
If IFI isn’t set and is required then the following steps are needed (this example uses Server 2012 R2).

Locate and execute the Run command:

Locating the ‘RUN’ command

and within it, run ‘secpol.msc’, which launches the ‘Local Security Policy’ control:

Local Security Policy control

Under ‘Local Policies’/’User Rights Assignment’, locate ‘Perform volume maintenance tasks’:

Local Security Policy Summary

Right-click on this and select ‘Properties’:

Right-click on ‘Perform volume maintenance tasks’

In this screen-shot I have already added the service account details, via the ‘Add User or Group’ button.
I found the required service account details by running this query:

SELECT  d.servicename ,
		d.service_account ,
FROM    sys.dm_server_services AS d;

Once the change has been applied the server will require restarting to actually implement the change.

Checking for Instant File Initialization

6 Jun [url=][img][/img][/url]

When SQL Server extends data or log files it fills the newly-acquired space with zeroes, to overwrite any data that may have been there beforehand. This action takes place when a database is created, restored, files are extended or added.
This can take a long time, depending upon the amount of space being initialised. This is one good reason for sizing your file requirements accurately and choosing when to make any extensions, rather than having the system perform them when the system is probably busy and holding up any number of processes.

What is Instant File Initialization?
Instant File Initialization (IFI) removes the zero-fill operation, so once the space is allocated it is immediately available. This can save a considerable amount of time.

How do I check for IFI?
One way of being notified of the status of IFI is via SQLCop, a free add-on that can be integrated within Redgate’s SQL Test framework.

SQLCop Error Message

However, this requires that xp_cmdshell is enabled and so might not be suitable for all environments.

Another method is via Brent Ozar’s ‘sp_blitz’ procedure. For versions from SQL Server 2014 SP2 this is fine, as it reads the SQL Server error log for information message relating to IFI.

EXEC sys.xp_readerrorlog 0, 1, N'Database Instant File Initialization: enabled';

Response from xp_readerrlog

From SQL Server 2008R2 SP1 a DMV has been available, which shows (amongst other things) if IFI is enabled and the Service Account, which is required should you need to enable IFI.

SELECT  d.servicename ,
		d.service_account ,
FROM    sys.dm_server_services AS d;

Response from DMV

IFI does not work against the log file – this must zero-fill as part of normal operation. It pays to size your log file correctly.

IFI does not work if Transparent Data Encryption (TDE) is used.

IFI does not work on sparse file (for example – database snapshots).

Trace flag 1806 disables IFI.

Because IFI does not overwrite newly-acquired disk space, it is technically possible to see the data within the deleted files that occupy this new disk space. This isn’t a trivial task (with DBCC PAGE) but may need to be considered.

Additional Links
IFI and a DBCC PAGE example
Microsoft Docs on IFI