Sql Job Problem
-
I have a job that executes 3 stored procedures. When the job runs, Sql reports success for all steps, however the stored procedures don't seem to run. They are populating work tables on 3 different dbs. When I run the procs outside of the job, they do what they are supposed to. Has anyone run into anything like this?
-
Are 3 stored procedures in same database or in different database?
-
Let's hope your worktables are no #- or ##tables
These are only available within their own connection.
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
No - they are not temp tables and job runs the same proc on 3 diffent databases, sequentially. It is possible that the proc is timing out, but why would sql not report a job failure in that case?
-
Do you have return values from each stored proc that you can test within the job steps?
You could write to a debug table or OS file dependant on the return value to prove that the procs have been executed, i.e. that you have permission on them and are accessing the correct ones.
Alternatively you could monitor each of the 3 DB from SQL Profiler to see what, if anything, is happening and where it's happening - just in case you're not getting the correct DB, etc.
I've had some probs with jobs myself - not stopping when they say they have and so on, so I'd be interested in what you discover!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply