Select * from msdb.dbo.SysJobHistory where Run_Status = 4 AND job_id = '3017EDE7-E5AC-4ECA-A376-FCEA13AD57DC'

Run_Status = 4 means that the step is running, look at the same table to find the correct job_id.

You can go in Edit post / Delete to remove one of them.

Yes... try opening a transaction and executing something that will violate a constraint. The whole operation will be rolled back.

Tripple post due to memory exception.

Finish the thread here : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=23&messageid=229771

Tripple post due to memory exception.

Finish the thread here : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=23&messageid=229771

335K rows in 15 seconds isn't really slow. What are the server specs. What is the execution plan?

union will do a DISTINCT select of the 2 result sets hence the order changing, use union all of you don't want that to happen.

Doesn't matter. There's always a transaction to rollback if a major error occurs.

you can do them all in one shot by removing the where login=@manualindex. Other than that it's hard to shorten the code.

What's the query ran from QA?

I'm gonna go on a limb here and say that it shouldn't be too hard to write such a generator (especially since I ain't gonna try to write it ATM...

What if a trigger code generator was built so that the trigger would use static sql?

It can be done in a set based approach.

This is an exemple of a way to do it in Yukon... I'll try to see if I can do...

... we'll see.

How about christ?