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 » Testing » Best Practices   (RSS)
Showing page 2 of 2 (20 total posts)
  • Reduce the Contention on tempdb with Trace Flag 1118: Take 2

    My earlier attempt to see what's going on with trace flag 1118 on SQL Server 2005 SP2 (9.00.3042) didn't take me too far because the results were not conclusive. I was motivated by seemingly conflicting suggestions from KB article Q936185 and whitepaper Working with tempdb in SQL Server 2005. The KB article lists the following as conditions that ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on August 10, 2007
  • Reduce the Contention on tempdb with Trace Flag 1118: To Enable, or Not to Enable?

    A recently published KB article Q936185 seems to contradict the recommendation of using trace flag 1118 and multiple tempdb data files with equal sizing to reduce the contention on tempdb object allocation in SQL Server 2005. The article states the following: In Microsoft SQL Server 2005, you may notice blocking ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on August 7, 2007
  • Which is Faster -- (1) Copy and Local Bulk Insert or (2) Bulk Insert across Network?

      A while back, I was asked which of the following two bulk insert options would be faster: Copy/Bulk Insert: First copy the data file from server B to server A, and then bulk insert the data into a table on server A Bulk Insert across Network: Directly bulk insert the data from server B into the table on server A Intuitively, the ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on July 23, 2007
  • Performance Impact of Procedure Calls without Owner Qualification -- SQL Server 2000

    My reaction was ''Wow!'', when I first saw the test results. I had to triple check the results and repeat the tests several more times in random order to make sure that I didn't make a mistake and that the results weren't a fluke. Good news is that the results are highly reproducible! The results I'm excited about are from the tests I conducted ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on July 5, 2007
  • Performance Impact of Using NTFS Compression with Read-Only Databases

    SQL Server 2005 supports placing read-only filegroups or read-only databases on NTFS compression. In other words, you can compress the database files in a read-only filegroup or a read-only database. This can be a very useful feature if saving disk storage is of high priority. But what are the performance implications of using this SQL Server ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on May 4, 2007
  • Should I Use a Windows Striped Volume?

    In Windows Server 2003, you can use the Disk Management console to create a striped volume over multiple dynamic disks (well, you can also create a mirrored, a RAID-5 volume, etc). If these disks (or LUNs) are presented from a SAN, most likely you can stripe across the same storage devices--making up these LUNs--inside the SAN to present ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on March 12, 2007
  • Find the Knee of the Curve

    Whether you are load testing SQL Server or evaluating the I/O performance of a storage subsystem, you need to make sure that you cover the entire spectrum of the load levels--from light and moderate all the way to heavy and saturated--before you draw any conclusion. This is especially important when you are doing performance comparison. Relying on ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 21, 2007
  • Is RAID 5 Really That Bad?

    RAID 5 is a dirty word in the DBA community and beyond. There are websites devoted to trash RAID 5. I've seen DBAs declaring performance root cause found the very moment they found out that some database files were placed on RAID 5 volumes. You'd be ridiculed and run out of town if you dare to suggest putting the transaction log file on RAID ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 7, 2007
  • Performance Impact of Disk Misalignment

    Just google for Windows disk alignment best practice, and you would find thousands of articles, whitepapers, and posts, all preaching the practice of aligning disk partitions on the 64K boundary. For instance, one of the EMC recommendations prescribes a disk alignment value of 64K for the host file systems when deploying SQL Server 2005. Microsoft ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on February 1, 2007
  • How Many Data Files Should I Create for a User Database?

    Whenever this question comes up, my typical response is to pass along the following Microsoft recommendations: The number of data files within a single filegroup should equal to the number of CPU cores. See the ''Physical Database Storage Design'' whitepaper. Lining up the number of data files with CPU’s has scalability advantages for ...
    Posted to Linchi Shea (Weblog) by Linchi Shea on January 29, 2007
Privacy Statement