Putting ORs in the WHERE clause is going to impact the execution plan and performance - by how much depends on the whole statement.

Unless performance is absolutely critical, though, I...

There was a lengthy exchange on this site a few months ago regarding ensuring that security classified data is genuinely destroyed. The outcome seemed to be that SQL Server...

I feel that this is one of those questions where 'If I need to know, I must be doing something wrong'! Could you put the values in a temporary...

An additional factor not mentioned above :

Table variables cannot be used in parallel processing and so may lead to a less efficient query plan on a multi-processor box. I...

I think what you want is :

SELECT SUM(CASE WHEN id BETWEEN '17' AND '29' THEN '1' END) AS '17-29',

SUM(CASE WHEN id BETWEEN '30' AND '39' THEN '1' END) AS '30-39',

SUM(CASE...

You can set it dynamically in T-SQL :

SET QUOTED_IDENTIFIER ON/OFF

Why do you say that it is bad practice? - or do you just mean at the connection level?

It depends on how the dll has been written, registered and called. You need to check with the author / documentation.

You also could use the COALESCE function which returns the first non-null value of its arguments. In your case, COALESCE([Adj Due Date], [Due Date]) ... but this will take...

This is most certainly not my area of expertise but I recall reading recently a post about problems with chaining network authorisation between more than two NT / 2000 boxes....

I had a problem recently with an SP using table variables running slowly in production when it had been OK in development. The difference turned out to be that...

It sounds like the security settings on the COM+ component not matching SQL Server or the box itself.

You need 'GO' + CHAR(13) in front of 'CREATE PROCEDURE ...

Surely, the only test that you need is for the equality (unless you really want 0 when TOT_WAIT_TIME is zero; you are, not unreasonably, assuming that TOT_WAIT_TIME never will exceed...

I've not seen this behaviour. Probably obvious but, while I assume that you have the timeout property set on the Connection object in VB, as a workaround, what about...

I have seen this effect also but have not had the opportunity to investigate.