August 2, 2010 at 8:54 am
:exclamation: I recently ran into an issue where reporting services would not complete running a stored procedure that only took management studio a short time to complete.
My stored proc has a Try Catch block surrounding the acting code, so anything under severity level 11 doesn't get caught.
When I ran profiler against the sp, I found the error 8153 about an aggregate function eliminating a NULL value.
I went through the code and found a field that was sometimes NULL. I wrapped it with an ISNULL function and the error disappeared. Consequently, the sp completed in reporting services quickly.
Just wanted to share so no one else has to spend their entire morning pulling hair. 😉
Keith Wiggans
August 2, 2010 at 9:45 am
Severities below 11 are not errors. They're warnings.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply