Just to be completely open about all this, I am employed by BMC Software. Having said that, I would like to suggest using an Enterprise Job Scheduler, like BMC CONTROL-M, that provides the ability to run SQL Server jobs such as sql scripts or stored procedures. If you use CONTROL-M, you get centralized job status monitoring from single management console across any number of database instances. You get all the infrastructure that has usually been built to manage scheduling such as 24x7 staffing, alerting via the scheduling console, email, automatic incident creation in Remedy, Service Desk Express, HP Service Desk and other such tools, ability to define automatic recovery actions and simple and intuitive dependencies between database tasks and other batch such as running your apps, file transfers, managing ERPs like SAP, Peoplesoft or Oracle eBusiness Suite, etc.
You don't need to create additional databases to track anything because CONTROL-M does it all for you. You don't need to write and maintain scripts and perhaps best of all, DBAs can spend their time administering databases rather than doing job scheduling.