Logging of DTS package execution | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Logging of DTS package execution

Hi, I have a packageA which calls two packages say package1 and package2. There is a on success constraint between package1 and package2 (i.e. Package2 gets executed on successfull execution of package1). In package properties I have enabled the check-box for looging execution log to sql server and provided correct credentials. I have not selected check-box for ‘Fail package on Log error’. This packageA is scheduled to run daily and I get a log for this package and both the inner packages. However recently, about 10 days back, I was not able to find execution log for package1, however there were logs for packageA and package2 and both were executed successfully. I was puzzled to see the missing log and could find no reason why this happened. After that it ran successfully with logs present for all the three packages, but today once again the log for package1 is missing and package2 is running and its log is also persent. Can someone please guide me a way to find out a reason why sometimes package execution logs do not appear in msdb? Thanks.
can you run the following query against msdb and check if this logged. select * from sysdtspackagelog And check the relevant columns for anything you are looking for is present Cheers
No log was present in sysdtspackagelog table….
Package will be logged if it has been called for an execution, so in this case you have to check the workflow whether it has been referenced to execute during other package execution. PROFILER might help you to see what is happening in this case Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
You can also add the job step output file to write it to text file and see what it is writing.. Make sure you have the right authentication for logging.
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.