locked
SCSM Database is increasing rapidly RRS feed

  • Question

  • Hi,

    we observed our SCSM 2012 ( hyper V based virtual servers for SCSM -2 management servers, 2 portal & 1 DW ) database is increasing gigantically & affecting Service manager.

    It is just enabled in production and didnt had too many records. Earlier our monitoring tool integrated with SCSM generated more than 15000 incidents & we closed all after resolving,

     it was very quick and filling the disk space in few hours even after increasing the space to 400 GB

    As per SQL table reports, dbo.windows workflow task job status was consuming more size.So Tried disabling all customized workflows but there was no luck.

    we restored the database prior to alert generation Suspecting the alerts triggered & everything observed normal, ( DB around 30 GB and log around 80GB), later found that database is still growing, in two days database reached 189 GB ( log in few GB only) without very few number of incident records ( around 15 )

    Still, dbo.windows workflow task job status only consuming DB size

    Pls suggest.

    Sumesh

    Sunday, June 28, 2015 7:52 AM

Answers

  • Maybe this blog post is helpful: More Aggressively Grooming the JobStatus and WindowsWorkflowTaskJobStatus Tables

    Andreas Baumgarten | H&D International Group

    Sunday, June 28, 2015 9:35 AM
  • If you want to decrease the size of the WindowsWorkflowTaskJobStatustable you can decrease the PartitionAndGroomingSettings to 1 and wait for 24 hours. This will hopefully shrink the table size.

    If you are interested in which workflow/rule are in the WindowsWorkflowTaskJobStatus table you can run the following SQL query:

    select WindowsWorkflowTaskJobStatus.DataItemLastModified, WindowsWorkflowTaskJobStatus.RuleId, Rules.RuleName from WindowsWorkflowTaskJobStatus
    Inner Join Rules
    On WindowsWorkflowTaskJobStatus.RuleID = Rules.RuleID
    Order by DataItemLastModified DESC

    For instance in our environment most of the jobs are related to the Exchange Connector:

    2015-06-25 00:18:24.037 # A362D834-FD87-262F-2B63-E6F39E6A0E31 # ExchangeConnector.0337e43a5f934786b1ba086b922418c1


    Andreas Baumgarten | H&D International Group

    Monday, June 29, 2015 6:52 AM

All replies

  • Maybe this blog post is helpful: More Aggressively Grooming the JobStatus and WindowsWorkflowTaskJobStatus Tables

    Andreas Baumgarten | H&D International Group

    Sunday, June 28, 2015 9:35 AM
  • Thanks for the suggestion,

    artitionAndGroomingSettings set DaysToKeep were already set to 3 & 15.

    I verified the workflow status too, unable to find any recent failed( failed only before the Restored DB date ), but there are many scheduled especially notifications.

    Sunday, June 28, 2015 12:09 PM
  • Is it both the Service Manager and DWDataMart databases that are growing? Do you use SCCM? Did somebody flip the switch on AI (for instance?) and set it to ALL objects?  What monitoring tool are you using to generate requests? SCOM? Do you use Orchestrator in this environment?  Not sure how to assist with limited info, but maybe some of these questions answered will help trigger some ideas.

     
    Sunday, June 28, 2015 2:51 PM
  • If you want to decrease the size of the WindowsWorkflowTaskJobStatustable you can decrease the PartitionAndGroomingSettings to 1 and wait for 24 hours. This will hopefully shrink the table size.

    If you are interested in which workflow/rule are in the WindowsWorkflowTaskJobStatus table you can run the following SQL query:

    select WindowsWorkflowTaskJobStatus.DataItemLastModified, WindowsWorkflowTaskJobStatus.RuleId, Rules.RuleName from WindowsWorkflowTaskJobStatus
    Inner Join Rules
    On WindowsWorkflowTaskJobStatus.RuleID = Rules.RuleID
    Order by DataItemLastModified DESC

    For instance in our environment most of the jobs are related to the Exchange Connector:

    2015-06-25 00:18:24.037 # A362D834-FD87-262F-2B63-E6F39E6A0E31 # ExchangeConnector.0337e43a5f934786b1ba086b922418c1


    Andreas Baumgarten | H&D International Group

    Monday, June 29, 2015 6:52 AM
  • Thanks for the response,

    I could see Asset Management Workflows & Exchange connector RuleIDs are getting executed mainly.

    Yes , lot of DW, temp DBs also generated.

    we have SCCM, SCOM connectors and NETCOOL monitoring tool integration through email.

    Exchange connector is connecting to Cloud.

    Monday, June 29, 2015 9:31 AM