Well, Steve, sorry you missed the 65 degrees and sunny here in Seattle yesterday afternoon   It was a great day, especially for the U2 concert...

we actually ended up buying SQLSentry, so no more worries about SQLMail at all

nah, see, it doesn't help.  They're able to start the jobs just fine, but even refreshing the list of jobs doesn't update the "status" field.  So they don't know if...

Bless you - that script worked like a champ.   I couldn't run sp_MSforeachtable with DBCC REINDEX because the ? was putting in [dbo].[databasename] and the syntax was messing it up. ...

so, as it turns out, TargetServersRole not only allows the user to see all jobs, but also specifically denies them pretty much anything else they'd want to do with them. ...

Thanks folks - what I didn't know (and just learned yesterday) is that only sa can run jobs they don't own.  Hard to know sometimes what the ordinary users aren't...

This isn't to try to catch somebody in the act; often developers will just overstep for the sake of convenience; due to SOX we have to prevent them from doing...

And the way that I read it was:

"What if you change the word HAVING to WHERE?"

...which doesn't work, using a Where clause after a Group By.  So I picked "no...

I'm just looking forward to seeing Necrossomus show his face in this forum and explain his "explanation"- this was NOT intended to be a trick question.  (I actually wouldn't have...

That's a good point.  I'll make sure I applied the correct full backup too

thanks everybody!