April 17, 2013 at 12:04 am
Comments posted to this topic are about the item Stairway to Transaction Log Management in SQL Server Level, 8: Optimizing Log Throughput
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 17, 2013 at 6:18 am
Great article. It drives me crazy that Microsoft, out of the box, has such small sizing and grow by 10% for model and TEMPDB. The first thing I do when I install SQL Server is fix that. Plus I always size the transaction log file for any new database to match what I think it will need to be and have a good growth rate on it. From time to time I check on transaction log file sizes too and run the DBCC LOGINFO() to see how fragmented the transaction log is.
April 17, 2013 at 2:24 pm
Very informative article.
Our SQL servers are virtual VMWare machines on a NetApp raid 5 environment. Do you have recommendations on setting up a transactionlog on such a system?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy