Jerry, I totally agree with you! It all depends on the job and what the desired outcome is?

My biggest drawbacks are the use of connection pooling whether it is done in .Net or Java it tends to consume more resources and never freeing them up!

I agree licensing will get you every time.:w00t:

You can find the standards reports on MS and download them! But I found no way of pulling them off of SSMS...

If he created the package locally on his PC,

My Documents\Visual Studio 2005\Projects

If he was working on the server same thing!

If he saved it to SQL Server then it would be...

Very interesting find to say the least, never notice that behavior in my packages???

Beside the trace flag, I would also configure an alert to notify when this occurs so you could capture the issue.

Not sure why everyone was hung up on the OS version, typo! Much to look at as far server configuration and SQL configuration! If you don't specify memory, SQL...

Thanks for the great feedback....

Do you have any linked servers created? To me sounds like credentials are wrong!

I agree... Way to go....

I would redirect errors to a log or table then move on to the next record. I would also tack on a send email so that I am notified...

The most instances I had ever run on one server was 5 let alone 25 or 50??? Why?

I don't think you would need to reinstall everything just the Client Tools!

Usually when I build a A/P Cluster the install puts SQL Server Agent in its own Resource Group! My guess when you had a failover SQL Server Agent didn't come...