Ashish MehtaWhy to configure Database Instant File Initialization in SQL Server? Its Advantages
SQL Server Database Administrators can leverage Database Instance File Initialization Feature which is available in Microsoft Windows XP Professional, Windows Server 2003 or later versions to reduce the time taken to restore very large databases.
The Database Instance File Initialization feature internally skips zeroing out of data pages thereby reducing the time taken when performing operations such as creation of new databases, adding new data or log files to an existing database, increasing the size of an existing data and log files (including database file auto grow operations) or restoring a database or a filegroup.
How to Using Database Instant File Initialization Feature
The Database Instant File Initialization feature can be used by SQL Server 2005 or later versions only when the SQL Server service account is granted SE_MANAGE_VOLUME_NAME privilege. Windows administrators can provide SE_MANAGE_VOLUME_NAME privileges to an SQL Server Service Account by adding it to Perform Volume Maintenance Tasks security policy.
Steps to Enable Database Instant File Initialization Feature of SQL Server
Step 1. Click Start | Control Panel | Administrative Tools | Local Security Policy
Step 2. In Local Security Policy window, expand Security Settings and then expand Local Policies.
Step 3. In Local Policies, expand User Rights Assignment folder. All the user specific policies will be displayed on the right side panel.
Step 4. In the right panel, double click Perform Volume Maintenance Tasks
Step 5. This will open up Perform Volume Maintenance Tasks Properties window as shown in the below snippet.
Step 6. On the Local Security Setting tab, click Add User or Groups… button, this will open up Select Users or Groups dialog box where you need to add the SQL Server Service Account and then Click OK to exit the Select Users or Groups dialog box.
Trending SQL Server Disaster Recovery Articles and Tips
- Improved Startup Parameters in SQL Server 2012
- SQL Server Database Engine Service Startup Options
- How to Configure TempDB on Local Disk in SQL Server 2012/2014 Failover Cluster to Improve Performance
- Database Backup Encryption in SQL Server 2014 a Step by Step Implementation Guide
- How to Fix “BACKUP detected corruption in the database log” Error in SQL Server
- How to Repair Database in Suspect Mode in SQL Server
- How to Start SQL Server without TempDB Database
Step 7. Click OK to exit the Perform Volume Maintenance Tasks Properties window.
Step 8. Finally click Start | Run and type the following command gpupdate /force to apply the modification in the security policy immediately as shown in the snippet below.
Conclusion
In this article you have seen how SQL Server Database Administrators can leverage Database Instance File Initialization Feature which is available in Microsoft Windows XP, Windows Server 2003 or later versions to reduce the time taken to restore very large databases.
