February 26, 2010 at 4:14 pm
I just built a new sql 2000 server (Don't ask why) and installed it on windows 2003 datacenter edition r2. I setup a network account, made it a local admin on the server and a sys admin on the server. I am using this account for the server and agent services. I used the standard microsoft SQL utility to move users from an old server to this one. No errors were detected.
However when I created a batch job on the server and ran it, it used a totaly different account. I did not set up a proxy. Maybe moving the users messed up a sid or something. Does anyone have a clue?
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
February 26, 2010 at 5:37 pm
Did it run as your user (the user you're logged in as)? Seems whenever I created T-SQL jobs, it uses my credentials.
----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------
February 26, 2010 at 6:00 pm
I forgot about the job owner. When I fixed that the problem was solved. Duh!
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
February 26, 2010 at 6:03 pm
I thought that was the case. The last person to edit the job ended up as the owner, and it often used their credentials for things.
Very, very annoying
February 26, 2010 at 6:39 pm
Yes. But now that it is corrected, life is good!
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply