SQL job scheduling concern | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL job scheduling concern

My main concern is eg: one our non production databases have 31 databases on it and naturally I have the standard backups and maintenance jobs created for each one of the 31 databases. Personally prefer not to run two SQL jobs (inc. maintenance jobs) at the same time even on different databases and therefore I have to schedule them in individually, which needs constant looking after, due to the likes of database growth. <br /><br />I have started to look around for SQL scheduling applications eg<a target="_blank" href=http://www.embarcadero.com/products/jobscheduler/index.html>http://www.embarcadero.com/products/jobscheduler/index.html</a> , however I would love to hear from someone who is already using a similar product.<br />Or have written their own SQL scripts for this.<br /><br /><br />Jozsef <img src=’/community/emoticons/emotion-5.gif’ alt=’;-)’ /><br />
I use two jobs, one for all of the database backups/dbccs and the other for all of the log backups. All the databases are then done in turn which avoids any overlaps Cheers
yes, i do likewise – no need to shed cash on 3rd party apps for this kind of thing.. Tom Pullen
DBA, Oxfam GB
We never had troubles in managing and executing scheduled jobs using SQLAgent, on a system which has 50 databases and I joined the small database (<5GB) in one go to perform backup/database maintenance tasks. And personally I don’t prefer third party tools to manage the important (Heart) of the databases and in any case SQL Server & SQLAgent are only processes will handle the request, so why to use third party for few graphical representation. Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Hommer duhhh….<br />I couldn#%92t see the forest from the trees… <br /><br />Two SQL jobs is very simple and an elegant solution.<br />Thanks guys. <img src=’/community/emoticons/emotion-5.gif’ alt=’;-)’ /><br /><br />PS: I also strongly agree with Satya, I really didn#%92t want to get a third party software to touch my babies. I have a SQL script which looks at the MSDB and gives me the history for any of the SQL jobs, however I still HAD the issue of rescheduling overlapping jobs.<br /><br />Jozsef