• foxxo (6/21/2013)


    I'd like to question if it is actually running as sa.

    Is it the same if you use sys.dm_exec_sessions rather than the old sysprocesses?

    Also can you write the current security context info to a table from the job? Or add a jobstep with print SUSER_SNAME() and tick "include step output in history"

    You know, that's a very good question (about the sys catalog thing). I need to check that out.

    I did add the PRINT code to one of the other jobs (which has a similar setup) and got back the domain account instead of SA. We have several of these restore jobs, which we only need to run manually if they fail for some reason. We've gotten the SA account notification for those other jobs on intermittent occasions too.

    So I'll test this on the job I am having to run manually today and compare the two table views.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.