Если в одном коннекте, 2-ая ХР вызывается явно (не через exec(...)) и обращение к временной таблице опять же явное, то можно.

Выделенное объясняет поведение QA

"Temporary tables are automatically dropped when they go out of scope, unless explicitly dropped using DROP TABLE:

A local temporary table created in a stored procedure is dropped automatically when the stored procedure completes. The table can be referenced by any nested stored procedures executed by the stored procedure that created the table. The table cannot be referenced by the process which called the stored procedure that created the table.


All other local temporary tables are dropped automatically at the end of the current session.


Global temporary tables are automatically dropped when the session that created the table ends and all other tasks have stopped referencing them. The association between a task and a table is maintained only for the life of a single Transact-SQL statement. This means that a global temporary table is dropped at the completion of the last Transact-SQL statement that was actively referencing the table when the creating session ended. "

А под явным вызовом процедуры я имел ввиду то, чио в 1-ой ХР пишется строка
exec mypoc2

а не так

SET @mystr = 'exec myproc2'
exec(@mystr)

в этом случае выполнение exec(@mystr) создаст другой коннект, в котором уже временная таблица видна не будет.

Пример из BOL-a работает прекрасно (SQL2000 SP1)

CREATE PROCEDURE Test2
AS
CREATE TABLE #t(x INT PRIMARY KEY)
INSERT INTO #t VALUES (2)
SELECT Test2Col = x FROM #t
GO

CREATE PROCEDURE Test1
AS
CREATE TABLE #t(x INT PRIMARY KEY)
INSERT INTO #t VALUES (1)
SELECT Test1Col = x FROM #t
EXEC Test2
GO

CREATE TABLE #t(x INT PRIMARY KEY)
INSERT INTO #t VALUES (99)
GO

EXEC Test1
GO