My team is pretty much all new and we inherited several automated jobs which we have little or no documentation on (nothing in the job description either). We have hundreds of automated jobs that run on the SQL Server Agent and various servers so I wanted to start documenting some basic information (When are these jobs scheduled?, How long do they usually take?, How often do they fail?, Is the length of execution time static or growing? If it is an SSIS package, where is it located and what does it do?, If it is a report, can it be migrated to SSRS scheduler?).
We have a college in the area that has asked us if we could utilize any interns. Although we have plenty of work, we are not able to grant access to sensitive data to nonemployees. I was considering restoring the database to another server and truncating the sensitive data tables leaving the system databases in tact for purposes of documenting the scheduled tasks. I am not sure this is a good idea since I might end up spending as much time “securing” the data as the actual task would take to complete. Does anyone have any creative solutions to this type of issue?
Maybe something like:
http://bradsruminations.blogspot.com/2011/04/documenting-your-sql-agent-jobs.html http://www.elsasoft.org/forum/topic.asp?TOPIC_ID=164
I would like to hear any feedback that others who have already overcome these types of challenges. I appreciate your help!!!
I have never used this tool myself, but I have heard some good things about Dataedo. https://dataedo.com/