Correct, it is part of the session. If you used a global temporary table ##
instead of # then you would have a problem. Also, it is possible to put
T-SQL in the dataset tab itself and theoretically you can put a temp table
there. But then you get exactly the problem you mention below. You could
actually take your code from your stored procedure and past it into the
generic query designer (two panes, you switch with one of the buttons to the
right of the ...). However, in most cases this is a bad idea due to how RS
processes reports. Put the logic in the stored procedure and everything will
work correctly and you will have no problems whatsoever.
If my comments about putting T-SQL in the dataset pane of RS is confusing
just ignore it. The important point is that yes the temp table in a stored
procedure is 100% multi-user safe.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> Hi,
>
[quoted text clipped - 22 lines]
>
> Dan
Dan - 17 Jul 2008 16:59 GMT
> Correct, it is part of the session.
Thanks for clarifying this for me. I feel much better now knowing this.
> If my comments about putting T-SQL in the dataset pane of RS is confusing
> just ignore it. The important point is that yes the temp table in a stored
> procedure is 100% multi-user safe.
Thanks for all the details. I understand perfectly everything you said.
Thanks again for all your help and time,
Dan