PROBLEMS WITH THE SQL SERVER AGENT AND JOBS

  •  Hello everybody, regards!

    It happens that we have SQL SERVER 2000 and we have problems with the SQL SERVER AGENT, we have defined some jobs for running at night and making the database backups, but sometimes they don't run, so we have to do the backup manually. I'm not sure but I think it may be something related with the windows account is defined in the SQL SERVER AGENT.

    There are 2 accounts, ADMINISTRATOR (windows obviously) and SQLADMIN (which the site administrator created for me), previously the SQL SERVER AGENT had the ADMINISTRATOR account, and I had no problems usually, but now I have the problems, at this very moment it has the LOCAL ACCOUNT, sometimes I change it to SQLADMIN, I have problems!!! sometimes it runs, sometimes it doesn't, and something else: sometimes my partner, the site administrator, log on as ADMINISTRATOR into the server, sometimes I log on as SQLADMIN.

    I got confused so I want to know how it has to be, how should I log on into the server when I need it?, how should my partner log on into the server when he needs? does it affect when he logs on as ADMINISTRATOR? which is the account that has to be set up in the SQL SERVER AGENT?

    I'd appreciate a lot if any of you could help me a little with this matter...ok???

    Thanks a lot everyboy,

    Amaury, regards


    L.I. Amaury C.R.

  • Best method is to have the SQL services running under their own account. This is independent of the login you use.

    If the server doesn't need to access any network resources, then just keep them running as LocalSystem, or a Local user account. If they need to access network resources then set them up with a domain user account.

    To avoid any permissioning problems, important SQL Agent jobs for backups and maintenance should be owned by the 'sa' user.

     

    --------------------
    Colt 45 - the original point and click interface

  • Is this is happening after you restarting the server? may be after restarting the server u should have to manually start SqlserverAgent service sometimes, and this maty prevent running the scheduled job.

    If sqlserveragent is running and the scheduled job is not functioning then check your error logs and application event log to identify the exact cause of the problem...

  •  

    Thanks a lot for your help, it was very helpful!!!!!!!!

     

    regards,

    Amaury Coria Ramirez


    L.I. Amaury C.R.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply