Fred,
Global temp tables are available from any connection including the next
package. You can get around this if you make table name unique per package
session. This also means you will have to supply the real table name to all
depending tasks at run time. Kludgy, but works.
Another approach is to use the same table for all package sessions, but with
an additional session identifier column. This one may be easier in design.
Ilya
"Fred" <anonymous (AT) discussions (DOT) microsoft.com> wrote
Quote:
Hi,
I need to create a table and use it in a package. However, this package
may be called simultaneously by several users. Can anyone tell me the
|
standard way of doing this? I have played around with temporary tables but
separate execute sql steps don't seem to recognise them. Can I use global
temp tables? Are they global only in the scope of the package?