This should help you :

Select * from msdb.dbo.SysJobHistory where job_id = '42ADD00B-46AB-4EF5-AD59-DE476FA638D2' order by run_date desc, run_time desc

Yes... but AJ already posted the solution. Just open the books online and you'll be able to find the solution.

Nice thinking... but what happens if the list of keywords is dynamic and you still want to use static sql?

Can you post the table definition, some sample data along with the expected results so we can easier help you (in case AJ's solution doesn't work in your situation)?

... With the execption of administrative stored proc that need to do work in many dbs, but not necessarely all at the same time. It can be a good...

... must have been a typo .

Also, this is exactly why you should always specify the object owner. There are other reasons, even more important than this one, but this is one area where...

If you want to keep the original data, then you won't have more efficient than this. You can't multiple replaces at one time in sql server so you have...

ok, now that we have this, can you try to catch the stats of the long execution (or the short one if this is the long running one)?

Yup .

... Unless he wants to change the data and never ahve to worry about his again. But that's his choice to make.

Ya I reread up on this, and in the disable section of the constraint, they referrence only updates and inserts as affected operations... so I guess truncate/delete is out of...

I don't see anything out of the ordinary... but then again it's hard to see anything in this context

However there see to have...

Nobody... that's why I warned him it could happen but I don't see that happening really often. It takes a tie at the third rank to cause this behavior......

Oops, let's try it like this (order by date DESC).

X 2005-03-02 11:27:43.000 2005-03-02 11:31:00.000

X 2005-03-02 11:27:43.000 2005-03-02 11:31:00.000

X 2005-03-04 09:59:54.000 2005-03-04 10:03:13.000

X...