What are the challenges you face when working across database platforms? Take the survey
Options

Scheduled Job Hung

appwrightappwright Posts: 62
edited February 1, 2006 1:07PM in SQL Backup Previous Versions
I just ran a scheduled job and it backed up all the databases (350 of them), however now the job is hung. It's just sitting there and seems to be doing nothing. I assume it is trying to delete the log history or something but it has been hung for about 30 minutes now on an unloaded server.

Ideas?

Comments

  • Options
    peteypetey Posts: 2,358 New member
    After the backups complete, SQL Backup will proceed with the deletion of expired log files, the deletion of old msdb entries, the mailing out of the output if the MAILTO option is used, and saving the log.

    If you run sp_who2, can you see the connection status and if it's running, and if so, the command that's running? Was the log generated?

    Does the backup complete if you run the command manually via Query Analyzer?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    The job finally completed - it took it about 2 hours and 30 minutes to finish after it finished the regular backups. That's a long time to delete some log files!
  • Options
    peteypetey Posts: 2,358 New member
    Do you have a lot of files in the log folders? sp_delete_backuphistory's performance could be better too, e.g.

    http://sqlteam.com/forums/topic.asp?TOPIC_ID=36201
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.