SQL Server Articles, Tips, FAQs, Reviews, Whitepaper, News etc - MyTechMantra.com

How to Configuring Database Instant File Initialization Feature of SQL Server

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 

Local Security Setting to Perform Volume Maintenance Tasks

Trending SQL Server Disaster Recovery Articles and Tips

Step 5. This will open up Perform Volume Maintenance Tasks Properties window as shown in the below snippet.

Perform Volume Maintenance Tasks Properties

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.

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.

Update gpupdate force

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.

Ashish Mehta

Ashish Mehta

Ashish Kumar Mehta is a database manager, trainer and technical author. He has more than a decade of IT experience in database administration, performance tuning, database development and technical training on Microsoft SQL Server from SQL Server 2000 to SQL Server 2014. Ashish has authored more than 325 technical articles on SQL Server across leading SQL Server technology portals. Over the last few years, he has also developed and delivered many successful projects in database infrastructure; data warehouse and business intelligence; database migration; and upgrade projects for companies such as Hewlett-Packard, Microsoft, Cognizant and Centrica PLC, UK. He holds an engineering degree in computer science and industry standard certifications from Microsoft including MCITP Database Administrator 2005/2008, MCDBA SQL Server 2000 and MCTS .NET Framework 2.0 Web Applications.

Newsletter Signup! Join 15,000+ Professionals




Be Social! Like & Follow Us...

Follow us

Don't be shy, get in touch. We love meeting interesting people and making new friends.

Recent SQL Server Tips

Manning