Hello, all
The application I am working with quietly imposes some
limitation on its connection to MSSQL that will not let me
create a temporary table. Below are some of my attempts with
the corresponding results:
SQL: CREATE TABLE #TEST(a INT)
ERR: CREATE TABLE is unsupported
SQL: BEGIN CREATE TABLE #TEST(a INT) END
RES: No error, but no table is created.
SQL: SELECT 1 a INTO #TEST
ERR: Browse mode cannot be used with INSERT,
SELECT INTO, or UPDATE statements.
On the other hand, that same connection allows anything
within dynamic SQL, but of course it is executed in its own
context and has no effect on the parent context. What else
can I try to coax it into creating a table, or is there no
chance?
Yes, I know that it smells bad, but sometimes one has to
choose the lesser evil while in reverse-engineering and
fixing poorly maintained legacy software. Originally, it
used a separate connection to create a global temporary
table with a GUID for name, and to pass that name as a
parameter to many user-supplied stored procedures, which had
to be written in dynamic SQL...
--
() ascii ribbon campaign - against html e-mail
/\
www.asciiribbon.org - against proprietary attachments