You created the problem when you changed the CAST to datetime from date. It was cast as date because you really don't want to capture time of day...

Might be another "learning opportunity", but I have to mention the following segment of the code:

WHERE (dbo.TCDaily.Kind <> 'A02') OR (dbo.TCDaily.Kind <> 'J02') OR (dbo.TCDaily.Kind <> 'J04') OR (dbo.TCDaily.Kind <>...

There isn't always a "best" or "right" way to do a given thing. Take a look at the following:

DROP TABLE #tblLeaders

DROP TABLE #tblMembers

CREATE TABLE #tblLeaders (

LeaderID int,

Leader varchar(50)

);

INSERT...

There is no direct mapping for a field defined as DECIMAL(65,2). As I indicated previously, there's just no way for SQL Server 2008 to support 65 decimal digits...

Just curious if you've tried my code... Let me know...

SQL Server 2008 only supports up to 38 decimal digits, so I can't imagine there's any practical way to support 65. However, if you know that the values...

This should be posted in the 2012 forum, not the 2008 one.

Here's a dynamic pivot for you... albeit with nulls instead of blanks, but given that you're having numbers in the columns without blanks, nulls seem more appropriate, and it's less...

Without considerably more detail, it would be hard to know where to look. However, I'd look at the query behind the dataset in question, and be sure to...

Sean Lange (5/28/2014)

Is there an...

It's even simpler:

DECLARE @dteTo AS date = GETDATE();

There's no need for a CAST or a CONVERT, as implicit conversion works just fine for this purpose.

I'm going to go with a literal interpretation of the original poster's written words:

that he/she wants records that don't appear in BOTH of the previous year queries.

Here's my shot:

;WITH PRIOR_YEAR_DATA...

That's quite detailed, and I'm sure it could be pursued, but the effort level at this point is somewhat high, and given that I'm already up against a deadline, there's...

It's already been tested. Against a measly million rows. It's a decryption function that is already CLR. It took far too long to be the...

Hmmm.... that's disappointing news. We would find it impractical to build a web-service for something with such low volume, and making the assembly UNSAFE isn't going...