Great article. It always amazes me how many people don't know about this feature. I still find servers in our infrastructure that do not have it enabled.
I have one question for you. You mention that you have a checklist for server builds. I am currently working to build one of these for our SQL team. I was wondering if you might share yours as an example I can learn from.
We collect statistics of all userdb + msdb and script out all databases at least once a week.
We also collect all sys.configurations settings so we keep track per instance.
Every instance also keeps track of individual configuration changes ( via a persisted table in our admin db that is being compared every hour ) using a sqlagent job.
Also, in our environment we have server engineers that handle the OS part of server configurations. If you have a similar setup, where do you draw the line of SQL configs vs. OS configs. I have been told by my engineers that the Instant File Initialization would be an OS config, but they are not willing to add it to their checklist.
Please inform your OS engineers, they do your sqlserver instances wrong by not adding that to their checklist !
On the other hand, it would be OK if they would grant you the auth. to grant that Windows membership to the service account of your instance. This would mean you would have total freedom using the correct domain account for your sqlserver service(s).
It also depends how good a job you as a dba can do pre-sizing your data files at install time, the size your db files grow by as well as that frequency.
As always, as long as your customers don't suffer, this doesn't surface, but you (and your OS engineers) could prevent file extend issues due to file initialization by granting your service account(s) this Windows authority.
if you want to play it as managers like to hear it:
What's the company cost of losing n Seconds of business due to timeouts of extending a file ? :ermm: