>> what sort of perf improvement do you expect from this change? 

One thing I have noticed is that, if a SQL collation sequence is used, comparison operations, especially LIKEs, are...

How about:

SELECT *

FROM YourTable

ORDER BY

        CASE Code

        WHEN 1 THEN 10000 -- larger than MAX(ACCT)

        ELSE Acct

        END

        ,Amount DESC

How about:

SELECT [ID]

        ,COUNT(CASE WHEN Value BETWEEN 0 AND 9 THEN 1 END) AS [0_9]

        ,COUNT(CASE

Maybe something like the following will work:

Set WshShell = WScript.CreateObject("WScript.Shell")

WshShell.Run("""c:\program files\internet explorer\iexplore.exe"" http://www.yahoo.com")

Sorry if I seemed a little hard, but I have seen code like this cause too many problems.

On the question of the results, it is difficult for anyone to comment...

This is NOT the best approach to take for this type of problem. It is best to use a set based approach with the data either being cleansed first or...

If possible, change the dates and times to use datetime.

Also, how are you going to define a month? For days, hours and minutes the following should work:

SELECT D.MiDiff/1440 AS...

Try casting the column to varchar(n) and then back to nvarchar(n) and seeing if it is the same.

SELECT YourNVarCharColumn

FROM YourTable

WHERE YourNVarCharColumn <>

        CAST(CAST(YourNVarCharColumn as varchar(<collength&gt

Your example output does not seem to make much sense. You may want something along the lines of:

-- *** Start of test data ***

DECLARE @t TABLE

(

 UserID int NOT NULL PRIMARY...

Is this what you want?

WHERE 1 =

 CASE

 WHEN NULLIF(NEWREQDATE, '00000000') IS NULL AND NULLIF(ORIGREQDATE, '00000000') IS NULL

 THEN 0

 WHEN NULLIF(NEWREQDATE, '00000000') IS NULL

  AND DATEDIFF(d, CAST(ORIGREQDATE AS datetime), GETDATE()) > 1

 THEN 1

 WHEN NULLIF(NEWREQDATE,...

Your second SP still uses a pseudo cursor.

You should really look at writing set based code. To do this one needs to know the DDL (CREATE TABLE with PKs and...

Something else you could try is explicitly specifying the type of join.

When there are more than 3 or 4 tables in a query I have noticed that the optimizer works...