Scheduling alerting jobs

By default, a single alerting job runs every 10 minutes on the server. However, you can change the number of alerting jobs and their frequency.

About this task

  • You can configure alerting to use up to 10 alerting jobs to distribute alert processing more efficiently. Although the jobs run to the same schedule, the start times are offset slightly.

  • The time taken to run an alert depends on the hardware setup, system load, and the complexity of the data and any queries in the alert. To ensure that alerting is working as expected, account for the performance implications of running your alerts before setting your alerting schedule.

  • For performance reasons, do not schedule these jobs to run at the same time as the routine backup or large imports (or the alerting jobs should be temporarily disabled while these tasks are running).

  • There is one job for processing email alerts. No setup is required on the SQL Server machine beyond setting up the SQL Server instance for email.

  • The number of actions detected by the alerting job, and whether all actions are detected, will depend on the frequency with which the job runs. In particular, editing a record after the job completes and then undoing that edit before the next job runs will not be detected. However, the two edits will always be recorded in the audit log (depending on how you have chosen to configure auditing).

Procedure

  1. In iBase Designer, select Tools > Feature Availiabilty > Alerting Configuration and click Schedule.

  2. Select the schedule type from the list (all the jobs will use the same schedule type):

    • Start automatically when SQL Server Agent starts - alerting jobs will run to the same schedule as the SQL Server Agent.

    • Start whenever the CPUs become idle - see your SQL Server documentation for information on CPU Idle Schedules.

    • Recurring - alerting jobs will run on a specified schedule.

    • Once - alerting jobs will run once on the date and time you specify.

    Note: Turn off Enable if you do not want the schedule to take effect immediately. In SQL Server, the job will be listed as not enabled and not scheduled.

  3. Specify the frequency at which the job runs. This can be changed at any time without needing to pause alerting.

    Note: Do not schedule alerting jobs to run at the same time as any routine backups or large imports.

  4. Click OK.

Results

The job will run at the next scheduled date and time if the job is enabled, and the SQL Server Agent is started.