# Scheduled SQL Job Register Worksheet

> Source: https://netray.co/tools/scheduled-sql-job-register-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable register of scheduled jobs with daily runtime, dependencies, owners and failure contacts.

## Category

developer

## Audience

- Database administrator
- ERP administrator
- ERP analyst

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Job name

**Key:** job

**Type:** text

#### System

**Key:** system

**Type:** select

**Options:**

- ERP application
- SQL Server Agent
- Windows Task Scheduler
- Cron
- Integration platform
- BI refresh

#### Start time

**Key:** start

**Type:** text

#### Duration (min)

**Key:** dur

**Type:** number

**Unit:** min

#### Runs per day

**Key:** runs

**Type:** number

#### Run minutes per day

**Key:** daily_min

**Type:** number

**Expr:** dur * runs

**Format:** number

#### Depends on

**Key:** depends

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Failure contact

**Key:** alert

**Type:** text

**Rows:**

**Job:** Nightly MRP regeneration

**System:** ERP application

**Start:** 22:00

**Dur:** 140

**Runs:** 1

**Depends:** Backup complete

**Owner:** Planning IT

**Alert:** erp-support

**Job:** Full database backup

**System:** SQL Server Agent

**Start:** 20:30

**Dur:** 55

**Runs:** 1

**Depends:** None

**Owner:** DBA

**Alert:** dba-oncall

**Job:** Index maintenance

**System:** SQL Server Agent

**Start:** 01:00

**Dur:** 70

**Runs:** 1

**Depends:** MRP regeneration

**Owner:** DBA

**Alert:** dba-oncall

**Job:** Open order extract to planning

**System:** Windows Task Scheduler

**Start:** 05:30

**Dur:** 6

**Runs:** 1

**Depends:** MRP regeneration

**Owner:** ERP analyst

**Alert:** erp-support

**Job:** Sales dashboard refresh

**System:** BI refresh

**Start:** 06:00

**Dur:** 12

**Runs:** 3

**Depends:** Open order extract

**Owner:** BI team

**Alert:** bi-support

**Totals:**

#### Total job minutes per day

**Key:** daily_min

**Agg:** sum

**Format:** number

#### Jobs registered

**Key:** job

**Agg:** count

**Format:** integer

**Summary:**

#### Job hours per day

**Key:** daily_hours

**Expr:** sum_daily_min / 60

**Format:** decimal

**Primary:** true

#### Longest single job (min)

**Key:** longest

**Expr:** max_dur

**Format:** number

**Notes:** Use the start time and duration columns to look for overlaps between heavy jobs such as backups, index maintenance and MRP. Job names above are examples, replace them with your own.

## Content

**Intro:** A nightly window is a shared resource. This register lists every scheduled job so you can see what runs when, how long it takes, what it depends on and who gets paged when it fails.

**Sections:**

#### How to use the register

**Body:** Enter one row per job across all schedulers: SQL Server Agent, Windows Task Scheduler, cron, the ERP's own batch queue and BI refreshes. Record the start time, the typical duration and how many times per day it runs. The worksheet totals the run minutes per day and shows the longest single job.

#### Using it to plan the batch window

**Body:** Sort rows by start time and check for overlaps among heavy jobs. A backup running while MRP regenerates, or index maintenance starting before MRP finishes, slows both and can cause blocking and timeouts. Dependencies matter more than clock times, so use the Depends on column and schedule downstream jobs relative to upstream completion where your scheduler allows it.

**Bullets:**

- Backups, index maintenance and MRP should not collide
- Extracts should start after the data they read is stable
- Leave slack for growth, since durations creep up
- Month end runs are longer than ordinary nights

#### Ownership and alerts

**Body:** A job without an owner and failure contact will fail quietly. Enter a team mailbox or on-call alias rather than an individual who may move on. Review the register when people change roles, and confirm alerts actually reach someone by testing them once a year.

#### Common mistakes

**Body:** Registers go wrong when only SQL Agent jobs are listed and the Task Scheduler scripts on an old server are forgotten. Another mistake is recording the planned duration instead of a recent actual. Update durations from job history every quarter, because data growth makes jobs slower.

**Cta:** If your overnight schedule has become fragile, we can help review the sequence and, where suitable, replace file extracts with on-premises, read-only query access.

**Faq:**

#### What should I include in the register?

**Answer:** Every scheduled or recurring automated task that touches the ERP or its data: database jobs, application batch jobs, file extracts, integrations and BI refreshes, with schedule, duration, dependencies, owner and alert contact.

#### How do I get actual durations?

**Answer:** From job history. In SQL Server Agent use the job history view or msdb tables. In the ERP, use the batch queue log. Take a typical value and a worst case from the last few weeks.

#### What is a safe gap between jobs?

**Answer:** There is no universal number. Leave enough slack that a job running 30 to 50 percent longer than normal still finishes before its dependents start, and test this against your month end volume.

#### Who maintains the register?

**Answer:** Name one owner, usually the DBA or ERP administrator, and require that any new scheduled job is added before it goes live. Make it part of your change process.

## Search terms

sql agent job register, scheduled job inventory template, batch job register excel, erp batch schedule template, job schedule documentation template, sql server agent job documentation, nightly job schedule worksheet

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json