Here is the basic thought. There are two types of rows. Those with another one that starts right after and needs to be combined in the results. ...

I posted this on another thread. I am just copying it in here because it is also relevant to this thread.

An identity can make a great primary key for...

Does this get you what you are looking for?

SET NOCOUNT ON

DECLARE @TempTable TABLE

(

patient varchar(10),

datebegin datetime,

dateend datetime

)

INSERT @TempTable

SELECT 'A', '1/1/05', '1/31/05' UNION

SELECT 'A', '2/1/05', '2/20/05' UNION

SELECT 'A', '2/21/05', '3/15/05'...

There is another option.  Here is how I like to write stored procs for pages such as searches that have optional fields.  It is best shown with an example

Let's say you...

With files you basically have two options.

1.  put the file in the db

2.  store the file on the disk and store the silename in the db.

Storing files in...

An identity can make a great primary key for multiple reasons

1.  It is great for joining.  I would hate to have a 3 column composite key that was migrating all...

This shouldn't be the case unless connections are being left open.  When a connection is closed, killed, or dies it automatically rolls back the transaction.

I did this to make sure...

Two things to add here:

1.  It seems possible to me that you are seeing a benefit the second time you run it because of caching on the SQL Server.  SQL...