I’ve grown up reading Tom Clancy and probably most of you have at least seen Red October, so this book caught my eye when browsing used books for a recent trip. It’s a fairly human look at what’s involved in sailing on a Trident missile submarine…
In part one of this post I showed how you can use a report to run SQL Server Agent Jobs by using a report. In that post I only showed you how to run a single job but hardcoding in the job name. Someone recently asked if it was possible to have a drop-down list of jobs to choose from instead of have the hardcoded job name so I thought it made for a great opportunity to write a part 2.
Create a Data Source that points to MSDB on the server that the SQL Agent job that you want to run is located.
Create a DataSet that runs the system stored procedure sp_start_job with a parameter called @jobname
Create a second DataSet that runs a select statement against the system table sysjobs.
Right-click on the @jobname parameter and change the available values to Get values from a query. The Dataset should be the one created in Step Three and in this case the Value field and Label field are both the field called name.
Add some text! Let the user know what’s going on. Drag a textbox over and add the appropriate text. I wrote an expression using the @jobname parameter so it read which job was started:
=“Running this report will start the SQL Agent job called “+Parameters!jobname.Value+“.”
Preview the report. You should have a parameter drop-down list of all your jobs that you can select and run.
Select the job you would like to start then hit View Report. I have several Reporting Services Subscriptions you can see by the GUID names listed. When the report runs you should see your textbox appear.