Also if I recompile the SP again - It goes back on a go slow

Here's the main guts of the query (modified for security)

WITH C_CTE (IssueID

,StartNo

,EndNo

,No

,LCSID

...

The other thing that is missing is any code to handle decimal and numeric datatypes with Precision and Scale.

Although some 'Best Practices' will change there are more that won't - Can't see it ever being anything but best practice to avoid code like

INSERT myTable

SELECT * FROM myOtherTable

Could be very useful to newbies - Things like thou shalt not use cursors (unless there is no other way - There is you just need to think a bit...

How about a forum just covering Best Practices ?

DECLARE @ms AS INTEGER

SELECT @ms = 86399998

SELECT CONVERT (CHAR(13), DATEADD (ms, @ms, '01/01/00'), 14)

Obviously this would be the maximum number that it would show...

Bob do you know the definition of an expert - An Ex is a has been and a spirt is a drip under pressure - Does that help 🙂

That gets my vote !

I've got two 🙂

The principle of the question was good just the layout was poor as mentioned above and the answer given is obviously wrong - surprise that one person actually got this...

Sorry Jeff I misread what you wrote 🙂

But Jeff

NOTE: This problem does not apply to SQL Server 7.0 and later.

You're pulling all of the data between '12/4//2001' and '8/31/2008' and then limiting it in your select statement to '1/1/2004' and '8/31/2008' - Do you need to populate the temp...

Why don't you store the results that you want to mail out in a table and set up a job to run sp_send_dbmail against this table - Presumably a...

Is it me or are these posts getting random ?