• Kwisatz78 (4/10/2013)


    Yes thats right I was really just trying to understand the differences between the est. and actual number of rows, and the explanations you have given go some way to do that.

    In fact the reason I was looking at this at all was because in SSRS the code validation fails on a subscription yet the subscription runs fine. I am currently looking into the use of tmp tables when validating code this way, as I believe the issue may lie in that.

    Thanks

    Do you mean the T-SQL generates a syntax error when parsed or that a run-time error occurs on execution when SSRS calls the stored proc? Using temp tables in the stored proc shouldn't be a problem. The first thing I always check in this situation is whether the credentials passed to the remote server have the appropriate permissions there. Linked server configurations default to using the security credentials of the current local login, but you can map a local login to a different set of credentials to use on the remote server. What credentials is your SSRS report running with, what credentials does the linked server connection pass to the remote server, and are the necessary permissions present in both places?

    Jason Wolfkill