Whenever I run a job or create a job, then run it, it executes as another id for which I never use and do not even have a password for.
Where is this configured and how to I force a job to run as my id (assuming I have the proper privileges)?
I'm thinking it's something to do with what id starts the sql server agent or similar to that.
Steve