Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: microsoft.public.sqlserver.programming Subject: Re: logging stored procedure fails when inserting via linked server Date: Wed, 24 May 2017 20:46:31 +0200 Organization: Erland Sommarskog Lines: 14 Message-ID: References: <14264424-14c3-48c6-828b-4c6a15cb903b@googlegroups.com> <1f6c1673-dc58-4650-8223-858c574ebb43@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="d1d1865120a768cedd901835da1c2146"; logging-data="13060"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19mLug5ho29V6rJqIjmHNVK" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:ISUYLkJAojUZK2Jkaso6dCv/jUE= Xref: csiph.com microsoft.public.sqlserver.programming:31320 > Digging further, it appears that it can be boiled down to the fact that > the inner procedure (BIGetFormatterColumnList) is being called to insert > into a table variable. the error can be reproduced with this snippet. I > need to be able to insert the output of the stored procedure into table > variable to gather the results for further work but i also want to be > able to log the start/end of the called procedure when i have a high > enough debugging level. When you run a procedure from INSERT EXEC, the procedure will run in the context of the transaction started by the INSERT statement, even if you did run BEGIN TRANSACTION yourself. -- Erland Sommarskog, Stockholm, esquel@sommarskog.se