With the SQL Server interface in Automate Schedule, it's easy to include Microsoft SQL Server jobs in your production job streams. This video shows you how to set up SQL Server definitions and schedule existing SQL Server jobs.
Note: Skybot Scheduler has been renamed to Automate Schedule and is now part of the Automate suite of products. The existing Skybot Scheduler features and functionality are the same; only the product name has changed.
Hi! Today we are going to show you how to set up your Microsoft SQL Server jobs in Skybot Scheduler. Centralizing the scheduling of SQL Server jobs and integrating them with your other IT processes saves time, reduces errors, and improves efficiency. Enterprise schedulers also provide additional functionality, such as event-driven scheduling, cross-system reactivity, output distribution, and more.
With Skybot Scheduler, it's easy to include SQL Server jobs in your production job stream. This video will show you how to set up SQL Server definitions and schedule existing SQL Server jobs using Skybot Scheduler.
The first thing that we do need to check is to make sure that we do have an agent connection to your SQL Server job. So I do have one defined here that we will go ahead and use.
The next step that we need to do is create a SQL Server definition. So we will come down here and go ahead and click on the "Create SQL Server definition" button. I'll just give it a name of the SQL Server itself with a quick descriptionîI'll just put demoîand you can also put tags in here. So I will put SQL and demo for some tags. And here we have to give a server instance. If you are not using a special server instance name on your SQL Server, then we will just go ahead and leave this blank. If you do have a certain server instance's name, we will go ahead and put that here. We are currently not using one so I am going to leave that blank.
Here, we decide whether we want to use trusted connection or if we are actually going to use Windows authentication. If we use trusted connection, that will be our Windows authentication. If we just keep this blank, and fill in our user name here, that means we are going to be using the SQL Server authentication, meaning somebody has actually been set up in the SQL Server to authenticate that way. I am actually going to use the trusted connection for this.
So we will go ahead and we will save that. That gives us our SQL Server definition all set up. Now what we need to do is go create a job so that we can use the SQL Server definition we just created.
So we will go create a new job and, again, we will just give this a quick test SQL name and demo description. Here we need to choose where this is actually going to run. So we need to choose the agent that the SQL Server is installed on. I will come down here and also give this some tags so it is easy to find.
And now we can schedule this job any way that we can normally schedule a Skybot job: days of the week, dateless, days of periods, intervals, and any of the other options that we do have. For this, I am actually going to keep it as an unscheduled job. So we will go down a little bit and come to the agent environment. Here, I need to give a username and password that is able to authenticate with that SQL Server database using the Windows authentication because I did use the trusted connection. So I will go ahead and put in my credentials here for the trusted connection. Put in my password, quick working path, and that will get me signed on to the SQL Server.
So now we can come down to the commands and here on the "add" button, we click on the little expanded section here. You will now see a SQL Server job that we can choose. Now here it is going to ask for the SQL Server definition so we can go ahead and choose the one that we had set up earlier.
And now we need to pick the job name. This is the job name that is currently set up within the SQL Server. So if I come over here to my Server Management Studio, these are the lists of jobs here that I can go ahead and run via Skybot. So I do have one called Dennis out there, so we will go ahead and choose that one.
Then you can choose whether you want verbose logging or not to go to troubleshoot later if you need it. So I am going to go ahead and select that and we will save it and create a job log for this so we can take a look at it and we can go ahead and save that.
So our job now has been created and if I now go ahead and run this, it will run the job out on the SQL Server. This is what the command looks like within Skybot. We will do a run job now. We can take a look at the history of this job and you can see it is currently running out there. And as we are letting that finish running, now that we do have the job defined in SQL Server, we can now add other things in it. Let's say I need this job to only run when my other job called "test" has finished. So I can go ahead and set that up and say run job "test" so now my job "test SQL" will only run when my job called "test" has completed. So we can go ahead and click "OK" to that and save it. So now when my test job runs, it will automatically run my "test SQL" job for me.
Go back and we will take a look at the history of the job and see it is completed on there and we can take a quick look at the job log and here you can see that we went ahead and we are authenticating against the SQL Server. And here it gave the job definition, gave us the run date, whether it has succeeded, so we are good out there.
It gave us the time and date stamp when the job out there was created, what time we actually ran it, and any other kind of information that you need. So that is how we can go ahead and easily set up and run your Microsoft SQL Server definition using Skybot Scheduler.
Still have questions? We can help. Submit a case to Technical Support.