Yesterday I made a post about using a queue instead of a list because the code was so much cleaner. I think it is very important that code is clean and easier to read.

But then Denis asked about the performance differences between the 2 methods. I hadn't worried about the performance, because in my case the performance was good in both cases.

But I aim to please my fellow LTDers, so I did a little performance test. And let me remind you that like most performance tests, this one ...

In order to figure out if you need more memory for a SQL Server you can start by taking a look at Buffer cache hit ratio and Page life expectancy.

Buffer cache hit ratio

Here is what Books On Line has to say about Buffer cache hit ratio

Buffer cache hit ratio

Percentage of pages found in the buffer cache without having to read from disk. The ratio is the total number of cache hits divided by the total number of cache lookups over the last few thousand page accesses. After a long period of time, the ratio moves very little. Because reading from the cache is m...

So I just got a brand new shiny QuadCore PC with 6GB of RAM and Vista on it. I decided to setup ReadyBoost since I have a couple of USB dongles laying around.

How does ReadyBoost work? Here is what Wikipedia has to say

Using ReadyBoost-capable flash memory (NAND memory devices) for caching allows Windows Vista to service random disk reads with performance that is typically 80-100 times faster than random reads from traditional hard drives. This caching applies to all disk content, not just the page file or sy...

Your testbed has to have the same volume of data as on production otherwise you are not really testing anything.

This blogpost is kind of a rant after I noticed this post on Stackoverflow

I do not believe there is a problem with the create trigger statement itself. The create trigger statement was successful and quick in a test environment, and the trigger works correctly when rows are inserted/updated to the table. Although when ...

Microsoft made available the Troubleshooting Performance Problems in SQL Server 2008 white paper on their site. This white paper is 102 pages long, the scope of this white paper is limited to the problems commonly seen by Microsoft Customer Service and Support (CSS).

Below is what is covered in this white paper:

Introduction

Goals

Methodology



Resource Bottlenecks

Tools for Resolving Resource Bottlenecks



CPU Bottlenecks

Memory Bottlenecks

I/O Bottlenecks

tempdb

Slow-Running Queries

Exten...