All goes well when I execute it in SQL Analyzer. So, I tried to attach this stored procedure to the trigger. When...
a certain column in one table changes, I want the trigger to call this stored procedure. It seems easy, but when I tried it, the SQL Server instance blocked. I got a message saying there was a permissions problem of using the method sp_OACreate. I've modified the authorization, but it still won't work.
When I execute the stored procedure and trigger separately, there's no problem. Is there any difference between these two ways, or did I lose something in my test?
Dig Deeper on Microsoft SQL Server 2005
Related Q&A from Greg Low
Should developers be granted permissions to production queue in a SQL Server environment? See why expert Greg Low suggests proc access by WITH ... Continue Reading
Find how to save stored procedure output to the network drive via SQL Server Management Studio. Continue Reading
Copying stored procedures between databases on the same SQL Server 2005 can be done through scripting the stored procedures with this method. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.