Post reply

Sql Server Agent Service

  • September 7, 2015 at 7:58 am

    #399004

    Hello all,

    In a simple SQL Server 2014 implementation with synchronous replication what should the the status of the SQL Server Agent Service?

    From my understanding it should always be in the stopped stat so that jobs don't run in the secondary replica.

    Problem is that when a automatic failover occurs the service wont start by itself.

    This happens because i didn't make the right configs? Or just because it has to be started manually?

    Regards,

  • September 7, 2015 at 8:01 am

    #1824986

    You mean Availability Groups with synchronous replicas?

    SQLAgent should be running. Jobs should have logic to check whether they're running on the primary replica or not, and if not to not run further.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • September 7, 2015 at 8:13 am

    #1824991

    Yes with sync replicas.

    Jobs are created by the platform that is using database (SAP) in this case. Guess i ll try get some information about this.

    I think jobs are started by SAP platform but we never know...

    Tanks for your help mate.

    Regards,

    Arestas

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

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