Content Management and Capture

Expand all | Collapse all

Anyway to stop INSERT into TASKSTATS table?

  • 1.  Anyway to stop INSERT into TASKSTATS table?

    Posted Fri August 28, 2020 07:22 AM
    Hi,
    I asked Support what the use of TASKSTATS table was.
    The operator told me only Report Viewer used this table.
    Why is Datacap always writing into TASKTATS anyway when it is not configured with Report Viewer?
    In one project, the size of this table had become like several hundred GB at one time.
    I told them what Support told me: Truncate it.
    Now in a new project that I am in, I am requesting the client to Truncate it likewise.
    But I and the client are wondering if Datacap can stop writing into TASKSTAS table. It seems like a total waste of the resource.
    I found these support documents, but not helpful. It does not have steps for v9 and I think Delete immediately after Insert slows down and also causes a big transaction log in MSSQL server.

    https://www.ibm.com/support/pages/stopping-inserts-taskstats-table-ibm-datacap-taskmaster-capture
    https://www.ibm.com/support/pages/latency-issues-ibm-datacap-taskmaster-capture

    ------------------------------
    dsakai
    ------------------------------


  • 2.  RE: Anyway to stop INSERT into TASKSTATS table?

    Posted Mon August 31, 2020 01:29 AM
    I don't know how to stop inserts into this table, but here are a couple of tips to manage the size.

    1) In Rulerunner, ensure the thread settings for your ingestion tasks have SkipSameBatch set to 1.  (The setting is on two levels of the thread structure - for simplicity, set both to 1.)

    2) Use a sheduled NENU (Datacap Maintenance Manager) job to purge / trim TaskStats outside of normal working hours.

    ------------------------------
    Robert Stegall
    ------------------------------



  • 3.  RE: Anyway to stop INSERT into TASKSTATS table?

    Posted Mon August 31, 2020 02:24 AM
    Thanks for your reply.
    2) I think this is what I am going to do. Making a rule in Maintenance Task Manager that truncates TASTSTATS every night.

    Because INSERT is done into TASKSTATS no matter what, and the client requires the MSSQL Database to be in FULL recovery mode,
    INSERT is continually growing Trasnsaction Log. I

    I hope Datacap in near future gives a feature to turn off this meaningless INSERT when no function is using TASKSTATS table.

    ------------------------------
    dsakai
    ------------------------------