You can check to see if they have finished yet using the undocumented function xp_sqlagent_enum_jobs as described in this excellent article by Gregory A. SQL Agent jobs: Create multiple SQL jobs, and start them asynchronously from your proc using sp_start_job.Call a SQL stored proc on each application thread. Custom application: Write a simple custom app in the language of your choice, using asynchronous methods.That doesn't mean you don't still have a lot of options (some of them mentioned in other answers): Just to be totally explicit: TSQL does not (by itself) have the ability to launch other TSQL operations asynchronously. I had to research this recently, so found this old question that was begging for a more complete answer. What's the point in 8 cores if we can't use them all at once? Start stored procedures sequentially or in parallel If you test the job status for the sub jobs, you can implement your conditional start of sproc 3 as well. It's not exactly what we're looking for, but the result is the same.
From that point, they all run autonomously. I'm doing a similar thing at the moment, and the only way I've found to avoid using SSIS or some external shell is to split my load routine into 'threads' manually, and then fire a single master sqlagent job which in turn executes as many sp _ start _ job's as I have threads. How can I run sql server stored procedures in parallel? The job itself may continue to do it's steps. It will just start the job and return immediately. So imagine it like sp_start_job is called in async manner. But here, you are running jobs in those iterations not the actual statements. Next iteration will start when the last is done.
0 kommentar(er)
