October 24, 2011 at 11:13 am
I inherited a package that was running fine, every night at 2:00, for years, then suddenly it began failing on 10-12-2011. I cannot see any difference in the package, as the same code runs fine on our UAT environment, but I can see that the SQL versions are different. In UAT, where it runs successfully, the version 9.0.3310, and the Prod server, where the package is failing in 9.0.3054.
I cannot tell where any windows updates or SQL Server updates have been installed, at least per the event logs on the server (App and Sys).
I have found where this is happened to some other people also, on 10-12-2011, as can be seen here: http://connect.microsoft.com/SQLServer/feedback/details/483175/failure-because-of-warning-about-null-aggregation
In my case, the query is in a data flow task, on one of the data sources:
SELECT code, MAX(message) AS Message
FROM prior_auth_reason_codes
WHERE (code IS NOT NULL) AND (code <> '')
GROUP BY code
ORDER BY code
If I run the same query through a query window in SSMS it runs just fine. Only through SSIS does it give an error.
Anyone else have this problem, and have you found a fix that doesn't require modifying the package?
Thanks,
Chris
Learning something new on every visit to SSC. Hoping to pass it on to someone else.
October 24, 2011 at 12:40 pm
The error, which comes from SQL Server, and does show in SSMS, but does not keep records from returning, is:
Warning: Null value is eliminated by an aggregate or other SET operation.
Thanks,
Chris
Learning something new on every visit to SSC. Hoping to pass it on to someone else.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply