I've never heard of disabled indexes causing any problems.

Are your execs logging into Integration Services and executing the package from the Stored Packages folder? Or are they running them from the child jobs?

So far as I know, it's not possible to pass an error outside of a jobstep to cause the job itself to fail. The error is only relevant inside the...

Thank you for letting us know. That will help with future questions.

Glad you got it working.

Heatstroke

Tell me about it!

Sure enough, same issue on the other packages that are having the exact...

Oh, for the love of ...!#(*%$#W$

I think I just found out what the issue is. EDIT: Forget the screenshots.

I have a file that comes over from a vendor named MyFile...

GilaMonster (7/6/2012)

---

While I belive you can insert into the job history tables (they're not system tables), it would probably be better if you created your own history tables for the...

Can I ask what makes you think this will work?

You said nothing about distribution, so here's a link. Check everything:

http://technet.microsoft.com/en-us/library/ms152757.aspx

In addition to what everyone else has already added,...

What error is it giving you?

I'm betting the distributor is still set up. Or the subscribers.

I don't know how you can add an entire job history, but you can check the success / failure of a job and its individual steps by querying against sysjobs,...

You may have to make the query dynamic SQL (stored in a variable) and execute the variable in order to get the Body = @tableHTML part of it working correctly.

Making it a clickable link. @=)