Problem Calling Remote Stored Procedure
-
Hi Gurus -
I'm having a problem - I have update and delete triggers on a table that call a local stored procedure. In turn, the local sp calls a remote stored procedure (the remote sp is very simple, just does a simple insert into a table). This works with no problem in our test environment - but it does NOT work in production (i.e., the remote sp doesn't do the insert).
The only difference I can see between test & production is that the source database in production runs under 6.5 compatibility mode. Has anybody ever tripped over this?? And if so, is there a work around??
One other clarification: All servers involved are SS2K and I'm using the old-fashioned Remote Server feature - NOT linked servers.
Thanks much for your time and consideration.
Mike at the Mill -
This was removed by the editor as SPAM
-
Just a thought,
Whenever i have had something that did not work in production but does in development it is because of security. I am god on my box and allowed to do a lot more than my application permissions can. I would suspect this could be the problem here as well.
You may want to try connecting to your production server with query analyzer using the credentials of your application then call the first stored procedure and see what happens.
An additional thing to check is if the 2nd stored procedure is available to the credentials of the original application. Calls from your database to sp's in another database can cause errors that way if the user hasn;t proper permission
Just a few ideas
tal McMahon
-
Thanks Tal -
Right on the money. It was security. I appreciate the response.
Mike at the Mill
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply