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 » SQL Server 2008 » Testing   (RSS)
  • Spit it out already!

    You’ve probably seen that commercial where the chewing-gum company van stalks the guy who has been chewing the same piece of gum too long, and they attack him and make him chew another piece. I feel like that with SQL Server 2000. Almost every shop I go into has at least one primary application running on SQL Server 2000. Now, don’t get me wrong ...
    Posted to Buck Woody (Weblog) by BuckWoody on January 6, 2010
  • After the Upgrade, it runs differently…

    I got a question yesterday in the mail that I thought I would just answer here in a broad context. While I can’t troubleshoot or do performance tuning from a distance, there are some interesting concepts and suggestions this e-mail brings up: “I have recently seen a change from SQL Server from 2005 to 2008 in where it handles CASE statements ...
    Posted to Buck Woody (Weblog) by BuckWoody on December 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
Privacy Statement