How to create and manage MSSQL Jobs in Control Panel V10

What is MSSQL Job?

MSSQL Job lets you schedule a Transact-SQL (T-SQL) script to run automatically against one of the Microsoft SQL Server databases in your hosting account. It is useful for recurring database maintenance, data processing, cleanup, reporting, or other tasks that can be performed with T-SQL.

Each job is linked to one MSSQL database and runs at the frequency you choose. The minimum frequency is once every 1 minute. The number of jobs you can create is controlled by the MSSQL Job quota on your hosting account.

How to create an MSSQL Job

1. Sign in to Control Panel V10 and open the hosting account you want to manage.
2. Open Databases, then select MSSQL Job.
3. Review the MSSQL Job quota and current usage shown at the top of the page.
4. Click + Add Job.
5. Select the MSSQL database where the job should run.
6. Enter a unique job name.
7. Enter the frequency in minutes. The value must be 1 minute or greater.
8. Enter the Transact-SQL (T-SQL) script that you want the job to execute.
9. Click Submit to create the job.

Example

The following example removes records from a log table that are more than 30 days old:

DELETE FROM ApplicationLog
WHERE CreatedDate < DATEADD(DAY, -30, GETDATE());

Always test your T-SQL script manually against the selected database before scheduling it. Make sure the script targets the correct tables and data.

Manage an existing job

• On/Off: Use the status toggle to enable or disable a job. A disabled job remains saved but does not run on its schedule.
• View Log: Click the log icon to open the job history. Each entry shows the run time, status, step, and message returned by Microsoft SQL Server.
• Edit: Change the database, job name, frequency, or T-SQL script, then submit the updated job.
• Delete: Permanently remove the scheduled job when it is no longer needed.

Important notes

• A job uses the selected database and its assigned database login.
• The job cannot perform an action that the database login is not permitted to perform.
• Long-running or resource-intensive scripts may affect database performance. Schedule them carefully.
• If a job fails, open View Log and review the latest status and message for details.
• If your quota is full, delete an unused job or purchase additional MSSQL Job quota before creating another one.