Viewing 6 posts - 1 through 6 (of 6 total)
OK I realized that I was simply wrong about Herts Chen's solution. It DOES work just as he explained. Here is my new code:
USE tempdb
GO
CREATE PROC SP_DoSomething AS BEGIN
SET NOCOUNT ON
DECLARE...
January 20, 2006 at 4:59 pm
Thanks for the tip Brian! I had messed around with that earlier and even though I could use that to get the command that is executing, it doesn't return the...
January 20, 2006 at 3:47 pm
It's not technically impossible but is probably not recommended in most situations. Here is a way to do it (without the table parameter actually working). There is also a way...
January 20, 2006 at 1:01 pm
Ahh, figured it out. You can do it by nesting the EXECs
EXEC ('SET ANSI_NULLS ON EXEC(''' + @sql + ''')')
cool.
January 10, 2006 at 5:45 pm
Actually, I found that in the MSDTC security configuration dialog from the component services, if I set the "Transaction Manager Communication" authentication from "Mutual Authentication Required" to "Incoming Caller Authentication...
January 5, 2006 at 7:25 pm
I am experiencing this as well referencing a stored procedure on a linked server from a trigger. Unfortunately, the suggestions here didn't help me either. Were you ever able to...
January 5, 2006 at 6:57 pm
Viewing 6 posts - 1 through 6 (of 6 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy