Post reply

Interesting Issue

  • January 6, 2015 at 1:34 pm

    #1768246

    Alexander Suprun (1/6/2015)

    xsevensinzx (1/6/2015)

    I temporarily resolved the issue by backing up the old stored procedure under a new name and then recreating it under the original name. The report now runs as normal under multiple executions.

    I'll re-examine the backup and see what I'm missing here. If it's with the temp tables, then this is obviously bound to happen again. So far, the permissions and code look the same when compared. Seems the issue is specifically with executing the stored procedure from SSRS.

    Most likely execution plan was cached with "bad" parameter values.

    Thanks!

    I'll check that too.

Viewing post 16 (of 15 total)

You must be logged in to reply to this topic. Login to reply