Sap Jobs and AlwaysOn

[Former Member]

Hello all,

During SAP installation SAP creates some jobs like:

SAP CCMS_<xxx>_<xxx>_Blocking_Lockstats

SAP CCMS_<xxx>_<xxx>_Update_Tabstats

SAP CCMS_<xxx>_<xxx>_MSSQL_COLLECTOR

My doubt here is if i should create a storage procedure in order to disable or enable this jobs according with their instance Role (primary or secondary).

Regards,

Arestas

[luisdarui · Accepted solution]

Hi Carlos,

Our partners at Microsoft recently released a new post with a Summary of all AlwaysOn topics:

http://blogs.msdn.com/b/saponsqlserver/archive/2015/10/23/sql-server-alwayson-summary.aspx

This post is listed there:

SQL Agent Jobs in an AlwaysOn / Mirroring Environment:

http://blogs.msdn.com/b/saponsqlserver/archive/2014/12/03/sql-agent-jobs-in-an-alwayson-mirroring-en...

Make sure to read also SAP Note 2153963 - DBACOCKPIT (DB13 and DB12) not working correctly with SQL Server AlwaysOn and Mirroring.

Kind regards,

Luis Darui

[Former Member · Accepted solution]

Hello Luis,

Tanks for your answer. It was already clear to me that for non SAP Jobs what i had to do. My doubt was regarding just the SAP jobs.

This was a false question since in an AlwaysOn environment they wont run because databases wont be open to writes in non primary instances.

With your notes, now i know that there are some procedure that can be implemented in order to the jobs only run in primary or secondary accordingly with my needs.

Tanks again,

Arestas