June 30, 2009 at 10:53 am
we have a database that is around 150GB and over 300 tables and over the years people have requested that periodic updates, inserts and deletes be run. we dumped these into SQL jobs and scheduled them to run as requested.
later on we started adding the trouble ticket #'s to the jobs to identify them later on. then we got tired of having a lot of simple DML jobs so we started adding new requests to existing jobs that run on the same schedule. Now people forgot when they asked us to schedule something and it's hard to find the offending job.
does anyone have a way to easily organize dozens of DML statements that run on different schedules? We might have to move to a separate SQL server that does nothing but run jobs on remote servers and document each DML as a separate job with the corresponding ticket number under which it was requested.
June 30, 2009 at 11:09 am
Why not just make stored procs for each job and put a comment in each of these SPs to find out what ticket number it is created for? You can call multiple SPs as different steps.
-Roy
June 30, 2009 at 11:10 am
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply