Automic Workload Automation

  • Private Community
 View Only

  • 1.  Change COMBINED_ACTIVITIES in UC_SYSTEM SETTINGS

    Posted Feb 21, 2020 10:09 AM
    Hi all,

    someone suggested to change COMBINED_ACTIVITIES in UC_SYSTEM SETTINGS to get more objects in Executions results.
    V12.3.0

    ... change combined activities to 20.000 (default 500) ...
    I doubled it to 999 and did not see much change in Performance on our sandbox.

    Did anyone of you changed this so far?


    As this is factor 40 of the default I am afraid that system stability could be in danger...

    THX a lot
    Wolfgang

    ------------------------------
    Support Info:
    if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
    Otherwise update/upgrade your system and check if the problem still exists.
    ------------------------------


  • 2.  RE: Change COMBINED_ACTIVITIES in UC_SYSTEM SETTINGS
    Best Answer

    Posted Jan 12, 2021 09:10 AM
    Hi Wolfgang,

    some time ago I have changed the parameter value to 5000 resp. 10000 for some customers. Couldn't report a decrease in performance ...

    regards,
    Peter

    ------------------------------
    Capture Europe
    ------------------------------

    Original Message


  • 3.  RE: Change COMBINED_ACTIVITIES in UC_SYSTEM SETTINGS

    Posted Jan 13, 2021 03:06 AM
    Hi all,

    We have set it to 5000 and not noticed any issues because of that.

    /Keld.
    Original Message


  • 4.  RE: Change COMBINED_ACTIVITIES in UC_SYSTEM SETTINGS

    Posted Jan 13, 2021 03:34 AM
    Edited by Roney.Uba Jan 13, 2021 03:35 AM
    Hi All,

    Usually the tasks/executions list limit would be 5000, to avoid MS SQL Server to perform a lock escalation.

    https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms184286(v=sql.105)?redirectedfrom=MSDN

    Which means that, when selecting more than 5000 records, the whole EH and/or AH table could be locked because of the user session, preventing background processing to move on (preventing write to EH and/or AH tables).

    More recently, disabling the lock escalation was added as a recommendation for MSSQL.
    ALTER TABLE xxx SET(LOCK_ESCALATION=DISABLE)

    https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Admin/admin_MSSQLServer.htm?Highlight=lock%20escalation

    Finally, if other databases are used or if lock escalation is disabled, it should be fairly safe to increase this limit to a few thousand entries.

    Of course, the performance then depends on how much load this puts on the Database server.
    If dozens of users are clicking on refresh like crazy, this can indeed cause performance issues. ;-)

    Regards,

    Roney Uba LinkedIn+
         RoneyUba.com

              Automic Consultant


    Original Message