Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On a server with MS SQL Server 2008 installed, we use the SQL Server Agent to schedule a large amount of SSIS-packages, all with unique schedules throughout the day.

Now and then, the server needs to be restarted (patching etc). Is it safe to right-click on SQL server agent and select 'stop'? The SSIS-packages are not that well-built and if they are stopped right in the middle of something data might become corrupted.

So, does stopping SQL Server Agent mean that jobs are 'killed', or is it just so that no more jobs will be scheduled to run from that moment?

share|improve this question

migrated from May 27 '13 at 10:18

This question came from our site for system and network administrators.

up vote 9 down vote accepted
  1. Yes, jobs are aborted. Non-SQL process (eg CmdExec) are aborted too.
  2. No more jobs run until SQL Server Agent is started again. Missing scheduled jobs will not be run.

After comment:

SQL Server Agent is just another connection to the DB engine. It will send an abort to the DB engine and all SQL jobs are stopped.

Abort means something here: it is a specific client action. See

share|improve this answer
When you say aborted, that really means 'killed' right? A job that is running when I click 'stop' on SQL server agent is NOT allowed to finish? – David May 27 '13 at 8:10
@David: Correct. Answer updated – gbn May 27 '13 at 8:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.