Basics of SQL Server Job Scheduling


To create and attach a schedule to a job

1.    In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
2.    Expand SQL Server Agent, expand Jobs, right-click the job you want to schedule, and click Properties.
3.    Select the Schedules page, and then click New.
4.    In the Name box, type a name for the new schedule.
5.    Clear the Enabled check box if you do not want the schedule to take effect immediately following its creation.
6.    For Schedule Type, select one of the following:
·         Click Start automatically when SQL Server Agent starts to start the job when the SQL Server Agent service is started.
·         Click Start whenever the CPUs become idle to start the job when the CPUs reach an idle condition.
·         Click Recurring if you want a schedule to run repeatedly. To set the recurring schedule, complete the Frequency, Daily Frequency, and Duration groups on the dialog.
·         Click one time if you want the schedule to run only once. To set the One time schedule, complete the One-time occurrence group on the dialog.

To attach a schedule to a job

1.    In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
2.    Expand SQL Server Agent, expand Jobs, right-click the job that you want to schedule, and click Properties.
3.    Select the Schedules page, and then click Pick.
4.    Select the schedule that you want to attach, and then click OK.
5.    In the Job Properties dialog box, double-click the attached schedule.
6.    Verify that Start date is set correctly. If it is not, set the date when you want for the schedule to start, and then click OK.
7.    In the Job Properties dialog box, click OK.

To prevent a scheduled job from running, you must do one of the following:

·         Disable the schedule.
·         Disable the job.
·         Detach the schedule from the job.
·         Stop the SQL Server Agent service.
·         Delete the schedule.
If the schedule is not enabled, the job can still run in response to an alert or when a user runs the job manually. When a job schedule is not enabled, the schedule is not enabled for any job that uses the schedule.
You must explicitly re-enable a schedule that has been disabled. Editing the schedule does not automatically re-enable the schedule.

Comments

Post a Comment

Popular posts from this blog

SSIS vs. T-SQL

This is a common question which comes often before any developer to choose between the two as to follow which path to choose as SSIS or T-SQL for developing ETL solutions. well i also got similar scenario some time back and was in a dilemma to decide this. on a big picture it's always better to go with conventional way i.e. using T-SQL and not to go with the tool. But on doing some more reading and research over many blogs and forums and also the development phase of my work over some 2 and a half odd years. I found some good reasons and explanations over this as not to always stick to a particular approach and do proper analysis of the requirements to take a decision. Below are some of the key points which i was able to collect regarding this. 1.  If the data does need to be persisted temporarily it can be to a raw file in SSIS whereas T-SQL requires temporary tables for which there may be a management/security overhead. 2.  SSIS have a very good visual representatio
Read more

Sync SSAS Cube From One Environment to Another

Please Execute the Below Mentioned Script in Either the SQL Agent Job or XMLA Script Window or in the SSIS Package using the "Analysis Services Execute DDL Task" -  < Synchronize  xmlns:xsi = " https://www.w3.org/2001/XMLSchema-instance " xmlns:xsd = " https://www.w3.org/2001/XMLSchema " xmlns = " https://schemas.microsoft.com/analysisservices/2003/engine " > < Source > < ConnectionString > Provider=MSOLAP.6;Data Source=SOURCESERVER; Integrated Security=SSPI;Initial Catalog=SourceCubeName </ ConnectionString > < Object > < DatabaseID > SourceCubeName </ DatabaseID > </ Object > </ Source > < SynchronizeSecurity > CopyAll </ SynchronizeSecurity > < ApplyCompression > true </ ApplyCompression > </ Synchronize >
Read more

Pump data from one server to another Efficiently

Image
Sometimes the requirement comes when we need to pump the data from one server to another server. Though we have SQL Import\Export wizard which can do this quiet easily, but in that way we will loose some important features of the table --      1. The Identity property of a column in case we have one in the table.      2. All the indexes. To avoid this we can go with a simple SSIS package to which we just need to pass the table name as a parameter and it will do the rest, taking care of the above constraints. This is how the Package looks - Steps - 1. To make the executable dynamic we will drive the package from a table, where we will    store the names of all the tables which we want to refresh from the source server and we will store it in a result set variable (Table_List) Refer the variables list in the below figure used in the package. 2. Create a For each loop container which will iterate throu
Read more