Thanks Mark! That was super quick on the uptake ++

Works perfectly too, based on my example. Much appreciated 🙂

The following page on Microsoft connect explains this behaviour:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=295301

If you believe that it should be changed, then you can always rate it!

Yeah! I agree with all of the above!

I do thank you for all the questions that are insightful (and correct). It's an ego bruising event when you get something...

Matt,

I bet you had a dollar for every time someone said: "One more..."

If you could, please send one more to me too: bemunted@gmail.com

We're doing a migration to a 2005 cluster...

and this little checklist I came across by accident moments ago is a nice summary:

http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx

I particularly like this article:

http://www.microsoft.com/technet/technetmag/issues/2005/05/SQLCluster/?related=/technet/technetmag/issues/2005/05/SQLCluster

It details how to make sure you have redundant everything and explains how to seperate your cluster resources into the appropriate groups for maximum availability (and...

Hi Neil,

This will most likely be due to the recovery option you have selected when you reconfigured log shipping. You need your log shipping setup in Standby mode which will...

that's the eternal trade off isn't it - security vs performance...

You can set encryption per protocol from

Go to Configuration Tools -> SQL Server Configuration Manager

Go to Network Configuration

Right...

Hi,

This is normally related to not having the correct permissions for the AD account on the SQL Server or attempting to login with the wrong account.

Check this kb article:

Hi,

I think you'll find that all client/server communications are encrypted by default.

Check out "Native Encryption" in the product overview article: http://www.microsoft.com/technet/prodtechnol/sql/2005/overview.mspx

Cheers,

NathanM

GavinB noticed that the timestamp column was different in easch row and we've now realised it's some history information - so the joins were working properly!

!!

Your query looks good to me...

Get the patient information,

return the title (LEFT JOIN TITLE),

return the teamname (LEFT JOIN TEAM),

There are a lot of joins though which could be...