You can probably write some code in 24x7 to pull job information from an external database, such as "execution file, host name, agent name", etc... A while ago, we were investigating possibilities of allowing users to hook 24x7 to their databases where job definitions can be stored. However, this effort was abandoned. Here are just a few reasons to not to do this: 1. Performance impact and dependencies on the database performance and availability. Basically, using external database means that jobs cannot be processed in a timely manner (seconds and sub-seconds levels). 2. Inconvenience in setting up and managing jobs. At least several people must be involved in development and management process instead of just one (e.g. 1 sysadmin or developer vs. DBA, security, developers, sysadmins) 3. System stability could be significantly affected by stability of the database and network, vs. stability of the autonomous 24x7 systems. 4. Internal 24x7 security, job database encryption, job integrity and several other features will not make any sense if job definitions are stored externally. 5. The convenience of having all jobs, all scripts, all configuration setting in a single place (single job database file) is gone with keeping different pieces in different places. Another aspect is that job definitions and setting can be changed in an external database without 24x7 Scheduler knowing about these changes. This significantly reduces quality and integrity of the scheduled jobs and complicates as well as increases the job troubleshooting time. 6. Requirement for an external database significantly decreases number of people who can use the product as not all of them have a good database system and know how to use it. Even more, in most cases people will not be able to run 24x7 on standalone systems that are not connected to a network. 7. Product cost itself, additional cost of product support as a result of for various database integration issues. 8. and more ... : Hi,
: I want to have all job related information like job name, execution file
: name, host name, agent name ect. in a database and the scheduler should
: execute these jobs. Is there a way to handle this situation??? : Thanks
|
