Sue_H (10/7/2016)

---

sgmunson (10/7/2016)

---

Finally got past the version difference by editing the package on the server where it was failing, and then after a couple other quick edits, it worked okay....

Finally got past the version difference by editing the package on the server where it was failing, and then after a couple other quick edits, it worked okay. ...

Well, I've now discovered that the versions of SQL Server are just slightly different. Here are the version details:

Microsoft SQL Server 2012 - 11.0.2100.60 (X64)

Feb 10 2012...

The moment you said "almost the same code", I had to conclude that there's no way to know if the changes might have caused your grief or not. ...

I know this topic is a bit old, but I'm wondering if anyone can recommend a particular testing platform or particular website that does SQL testing, whose results have been...

This will do the job:

DECLARE @a AS TABLE (

[Type] varchar(30),

SubType varchar(30),

dates date,

datesdiff decimal(19,4)

);

INSERT INTO @a VALUES('a','ab','2016-04-01',0);

INSERT INTO @a VALUES('a','ab','2016-04-01',2);

INSERT INTO @a VALUES('a','ab','2016-04-01',3);

SELECT *

FROM @a;

SELECT REPLACE([Type], CHAR(9), '') AS [Type], SubType,...

What if I don't want to log to a file, but instead just have the output go into the text you see in Job History, as well as seeing it...

You didn't say whether...

How about the following:

CREATE TABLE #Data (

PrimaryKeyID INT...

Just wondering if you've got some NVARCHAR data that is a problem because of the data length, or perhaps there's data in production that's not in your testing instance?

Your query uses T-SQL language features that are NOT a part of SQL 2008. Perhaps this needs to be posted in the forum appropriate to the version of...

Check to see what security context the SQL Agent uses to run jobs. If it's not the same as when you run in SSMS, that might be your problem...

drew.allen (3/10/2016)

---

sgmunson (3/10/2016)

---

I don't have a 2012 instance handy, or I could have tried using LEAD or LAG with some GROUP BYs, but here's a query that only uses 2008...

You're welcome. Enjoy... Some thoughts on potentially improving its performance:

1.) Perhaps generate the additional 6 months in the 2nd CTE instead of in the WHERE clause...

I don't have a 2012 instance handy, or I could have tried using LEAD or LAG with some GROUP BYs, but here's a query that only uses 2008 syntax that...