This is a reply to Andrew Hancox post #460732...

I have seen this occur. My sproc (and ultimately application) took a long time to process. When I debugged, I was able...

When evaluating the WHERE clause, I find it good practice to include parenthsis around each target of comparison:

WHERE

( @ReorderPoint IS NULL OR ReorderPoint > @ReorderPoint )

and multiple comparisons

WHERE...

Thanks for this article. Your approach is very interesting especially with the use of CTE constructs. Finding good xml shaping articles is difficult at best and your approach...

Superaltive article. Thanks.

Agreed

Excellent article. Thank you very much. Your opening of how you worked in many places and faced the same issues (reporting, etc.) can, I am sure, be...

As Lynn and Matt pointed out, adding a new column and updateing will solve your problem. My example assumes you are using some version of Query Analyzer where you...

I do not disagree with you. It was a typo on my part. The easiest way to do it is as Lyn said. I was merely pointing...

Try this:

Without sampling a large population of your nvarchar date data, I will assume the example you gave will be sufficient.

Here I simulate your scenario.

declare @TestDateValue nvarchar(50)

set @TestDateValue = '01/01/05'

select...

Using CHR(39) might be a little cleaner than tripping ticks.   It is more readable as well.

For Example:

select char(39) + 'TEST STRING' + char(39)

returns: 'TEST STRING'

-Mike DiRenzo

In response to Mark Hickins comment concerning my thought processes, without question, you are obviously erudite.  True, I probably would not be on your team but probably leading your department.  My thought processes...

I concur with your statement of "I don't like cursors so I don't use them". It is an empty and unsupported posit.  It is my...

I thought SQL Server Central was a place where developers posted original authorship.  Clearly if this were original authorship, the author would have done his...