THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » Best Practices » SQL Server 2008   (RSS)
  • SQL Server 2008 R2 Best Practices Analyzer

    Maybe I'm a little late to the party, but I thought I would share with you the most recent release of Microsoft's Best Practices Analyzer for SQL Server 2008 R2 (you can also read the original blog announcement from CSS). Let me be clear: this tool is not just for people who are already on SQL Server 2008 R2.  It will also happily analyze ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on August 25, 2010
  • SQL Server challenge: show me trace flag 1118 is significant

    Here is a SQL Server challenge as I have failed so far:   Describe a reproducible workload that would see significant throughput improvement when trace flag 1118 is enabled.   I have seen a lot of chatters, anecdotes, and stories on the impact of trace flag 1118 on reducing tempdb contentions. But I have not seen ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on October 1, 2009
  • Performance impact: thread mode vs. fiber mode

    SQL Server can run in one of two modes: thread mode or fiber mode. By default, SQL Server runs in thread mode in which a SQL Server worker is associated with a Windows thread throughout all phases of its execution. This can be changed with the sp_configure option ‘Lightweight Pooling’. When Lightweight Pooling is turned on, SQL Server runs in ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on May 4, 2009
  • Performance impact: a large number of virtual log files – Part II

    In my previous post on the performance impact of having a large number of virtual log files (VLFs) in a transaction log, I showed that a large number of VLFs could be very bad for SQL Server 2008 performance. The test workloads were large batch delete, update, and insert. In other words, they were single monolithic transactions that ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 12, 2009
  • Performance impact: a large number of virtual log files – Part I

    It is generally known that having a large number of virtual log files (VLFs) in a database transaction log is undesirable. A blog post by the Microsoft support team in Stockholm showed that a large number of virtual log files could seriously lengthen the database recovery time. Tony Rogerson also reported that lots of virtual log files were bad ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 9, 2009
  • Let's deprecate UPDATE FROM!

    I guess that many people using UPDATE … FROM on a daily basis do so without being aware that they are violating all SQL standards.   All versions of the ANSI SQL standard that I checked agree that an UPDATE statement has three clauses – the UPDATE clause, naming the table to be updated; the SET clause, specifying the columns to change and ...
Privacy Statement