July 10, 2014 at 12:06 am
Comments posted to this topic are about the item Instant File Initialization
July 10, 2014 at 5:04 am
Great article, 5 stars. I new nothing about this. Learned something new today already!
-- Itzik Ben-Gan 2001
July 10, 2014 at 8:22 am
Does it save time when the file is expanded? It is a best practice to keep the file increase size relatively small because of the hit on performance when the database file grows, does Instant Initialize help in this regard? Thanks, Rick
July 10, 2014 at 8:32 am
rick.foster (7/10/2014)
Does it save time when the file is expanded? It is a best practice to keep the file increase size relatively small because of the hit on performance when the database file grows, does Instant Initialize help in this regard? Thanks, Rick
Yes, IFI saves time when the file is expanded (either manually or by AutoGrowth).
For example, if currently your data file size is 40 GB & you want to expand it to 70 GB proactively, IFI helps you there by reducing the processing time.
July 10, 2014 at 8:33 am
Alan.B (7/10/2014)
Great article, 5 stars. I new nothing about this. Learned something new today already!
Thanks for your kind words Alan. Glad you find it useful.
July 11, 2014 at 12:18 am
4 stars! You should mention how to confirm that it took effect, by looking at the errorlog after creating a database, to see if it no longer says "Zeroing completed". There is a script to check for this, using sp_readerrorlog, at: http://sqlblog.com/blogs/tibor_karaszi/archive/2013/10/30/check-for-instant-file-initialization.aspx
Note it also requires trace flags 3004 and 3605 to make that information actually show up in the errorlog, see: http://www.rdx.com/Blog/dba_tips/2011/03/undocumented-trace-flags-inside-the-restore-process/[/url]
July 11, 2014 at 1:09 am
Please consider voting for these related Microsoft Connect feature requests (I just added #917919):
July 11, 2014 at 3:12 am
Thomas Keller (7/11/2014)
4 stars! You should mention how to confirm that it took effect, by looking at the errorlog after creating a database, to see if it no longer says "Zeroing completed". There is a script to check for this, using sp_readerrorlog, at: http://sqlblog.com/blogs/tibor_karaszi/archive/2013/10/30/check-for-instant-file-initialization.aspxNote it also requires trace flags 3004 and 3605 to make that information actually show up in the errorlog, see: http://www.rdx.com/Blog/dba_tips/2011/03/undocumented-trace-flags-inside-the-restore-process/[/url]
Thanks for your valuable comments Thomas. When writing this article, I initially thought to provide this information in the article, however I skipped that later for the simplicity of article.
My idea was that after reading the article people will be curious about IFI & they will find out about these undocumented DBCC commands very soon.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply