I have an app that:
1. creates a temp table
2. uses fastload interface to insert rows into table
3. calls stored proc to process rows
Everything is done on the same connection.
If the stored proc is a CLR stored proc, the temp table is visible but
always appears empty (CLR stored proc is using the context connection).
If the stored proc is TSQL, everything works as it should (temp table is
visbile and has rows).
Is this some limitation of context connection? possibly in conjunction with
fastload? Anyone have any ideas?