|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Saturday, February 16, 2013 6:31 PM
Points: 464,
Visits: 8,712
|
|
|
|
|
|
UDP Broadcaster
      
Group: General Forum Members
Last Login: Wednesday, January 02, 2013 12:15 PM
Points: 1,443,
Visits: 711
|
|
James, Well done! an excellent article...
Mark
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 11:47 AM
Points: 564,
Visits: 1,454
|
|
Multiple log files: I thought the recommendation was one log file per cpu, for performance?
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 7:30 AM
Points: 1,114,
Visits: 1,140
|
|
Indianrock (1/5/2009) Multiple log files: I thought the recommendation was one log file per cpu, for performance? That's recommended for the data-files of the TempDB... (also keep them the same size)
** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 11:47 AM
Points: 564,
Visits: 1,454
|
|
Oh, of course. I made my comment before the coffee was ready, sorry.
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: 2 days ago @ 10:29 AM
Points: 889,
Visits: 931
|
|
Good article. One thing to add, if running SQL2K5 or later on Windows 2003 or later, enable instance file initialization. Doing this will minimize the impact of growing the log or data file, especially for larger growth settings.
David
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 11:47 AM
Points: 564,
Visits: 1,454
|
|
This article indicates Instant File Initialization is only for data files. http://www.microsoft.com/technet/prodtechnol/sql/2005/physdbstor.mspx
Instant File Initialization
SQL Server 2005 added support for the Windows instant file initialization feature. By default, when a file is created or grows larger, the pages in that file are initialized by writing zeros before the file gets used. This overwrites any existing data that remains on the disk. Instant initialization is only used for data files (not log files) and is enabled when the account running SQL Server has the Windows SE MANAGE VOLUME NAME privilege, which is available only on Microsoft Windows XP, Windows Server 2003 or later versions. This occurs in five scenarios: •
During file creation •
CREATE DATABASE, including tempdb creation at server startup. •
RESTORE DATABASE •
During file modification •
ALTER DATABASE...MODIFY FILE. •
Modifications that result in autogrow activity.
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: 2 days ago @ 1:47 PM
Points: 31,406,
Visits: 13,722
|
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: 2 days ago @ 10:29 AM
Points: 889,
Visits: 931
|
|
This article indicates Instant File Initialization is only for data files.
That was an oversight on my part, you are correct. To much R&R over the holiday I guess. 
David
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Saturday, February 16, 2013 6:31 PM
Points: 464,
Visits: 8,712
|
|
Steve, and everyone else...
Thanks for the great compliments!
Yes, as mentioned in my article, there is no performance benefit to multiple log files. It seems the only benefit is file management for disk space and other administrative tasks where you would want the log file in a smaller size (i.e. disk mirroring, or limited hard drive space).
BOL: Adding and Deleting Data and Transaction Log Files (http://msdn.microsoft.com/en-us/library/ms191433.aspx), says "SQL Server uses a proportional fill strategy across all the files within each filegroup and writes an amount of data proportional to the free space in the file. This enables the new file to be used immediately. In this way, all files generally become full at about the same time. However, transaction log files cannot be part of a filegroup; they are separate from one another. As the transaction log grows, the first log file fills, then the second, and so on, by using a fill-and-go strategy instead of a proportional fill strategy. Therefore, when a log file is added, it cannot be used by the transaction log until the other files have been filled first."
This is a solid indication that there is no benefit to performance when using multiple transaction log files.
Thanks, James
~ Without obstacles, you cannot progress ~ http://sqln.blogspot.com/
|
|
|
|