|
|
|
Ten Centuries
Group: General Forum Members
Last Login: Thursday, June 25, 2009 7:55 AM
Points: 1,087,
Visits: 1,837
|
|
A job failed for the first time today on our SQL 2005 instance, running an SSIS package, that to my knowledge, has not been changed for about a month.
When looking at the job step properties, I found out that the location of the .config file was wrong, so I have the strong suspicion that the job/package has been tampered with.
Is there a way changes to SSIS packages can be audited somehow?
The package has been deployed in the File System.
|
|
|
|
|
Hall of Fame
Group: General Forum Members
Last Login: Thursday, July 02, 2009 4:39 PM
Points: 3,365,
Visits: 2,397
|
|
If the config file path was wrong in the job step, wouldn't that indicate that the job was changed rather than the package?
Unfortunately, I don't think a modification history of jobs is kept, except for the date_modified column in msdb.dbo.sysjobs.
Greg
|
|
|
|
|
Ten Centuries
Group: General Forum Members
Last Login: Thursday, June 25, 2009 7:55 AM
Points: 1,087,
Visits: 1,837
|
|
Greg Charles (10/2/2008)
If the config file path was wrong in the job step, wouldn't that indicate that the job was changed rather than the package?
Unfortunately, I don't think a modification history of jobs is kept, except for the date_modified column in msdb.dbo.sysjobs.
thank you, you gave me an idea.
I will look at a recent backup of the msdb database to see if that job has been changed in the last couple of days.
|
|
|
|
