Jonathan Leffler wrote:
>
> The key point is that the definition is persistent, but the contents
> are per session -- I seem to remember there being a per-transaction
> option too...

OK then - I can get down to that.

Original poster has also explained that they are talking about schema only,
and not data.

I have sometimes heard people (both at work or on ng) asking "can I share my
temp table with another process?" and it's a bit tricky to explain why
not... What you described would also NOT offer that ability.

Is there any room for a temp table that is owned by one process, is shared,
but when the first process goes away the temp table is taken away with it? I
think the people who ask for data sharing in temp tables are looking for a
way to pass data back and forth between cooperating processes. Which almost
sounds like a persistent, logged queue within the engine...