Has anybody had any luck logging package execution and errors in SSIS?I have a package that executes just fine in debug mode, but fails as a job with the <sarcasm>incredibly useful</sarcasm> error message:"Execution of job failed. See the history log for details."So I check the job history and get other invaluable information, such as:"The job failed. The Job was invoked by User blindman. The last step to run was step 1"Ah, now all is clear. NOT!So I try to enable logging to a text file to find out what is going on. Here is the crap that gets output:OnError,HC1GEMSQLPRD1,NT AUTHORITY\SYSTEM,Transfer clas data,{DA16E07A-B8E8-450F-BDE6-EC244405D9D6},{1E59C18D-C24B-4709-9EC2-482302BD4A85},12/27/2006 11:19:05 AM,12/27/2006 11:19:05 AM,-1071611876,0x,The AcquireConnection method call to the connection manager "www.mydomain.edu.myserver.mydatabase" failed with error code 0xC0202009.
Seriously. I have had so many problems with SQL Server 2005, and come so close to irretrievably losing invaluable data on so many occasions, and had so much downtime, that I could NEVER recommend that any of my clients upgrade to this. In its implementation and documentation SQL Server 2005 is as bad as Oracle.STAR SCHEMAS ARE NOT DATA WAREHOUSES!