Home
  •  

MSSQL 2017 on Windows: Active Checkpoint File Pairs

Microsoft.SQLServer.2017.Windows.CollectionRule.DBFileGroupFx.CheckpointFile.Active (Rule)

Collects the number of active checkpoint file pairs in Memory-Optimized Data Filegroup.

Knowledge Base article:

Summary

The rule collects the number of active checkpoint file pairs in Memory-Optimized Data Filegroup.

Active CFPs contain the inserted/deleted rows from previous closed checkpoints. They contain the contents of the tables that area read into memory before applying the active part of the transaction log at the database restart. We expect that size of these checkpoint files to be approximately 2x of the Memory-Optimized data size of memory-optimized tables, assuming the merge operation is keeping up with the transactional workload.

Overrideable Parameters

Name

Description

Default Value

Enabled

Enables or disables the workflow.

Yes

Interval (seconds)

The recurring interval of time in seconds in which to run the workflow.

900

Synchronization Time

The synchronization time specified by using a 24-hour format. May be omitted.

 

Timeout (seconds)

Specifies the time the workflow is allowed to run before being closed and marked as failed.

300

Timeout for database connection (seconds)

The workflow will fail and register an event, if it cannot access the database during the specified period.

15

Element properties:

TargetMicrosoft.SQLServer.2017.Windows.DBFilegroupFx
CategoryPerformanceCollection
EnabledTrue
Alert GenerateFalse
RemotableTrue

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.SQLServer.2017.Windows.DataSource.HKFilePairs Default
Mapper ConditionDetection System.Performance.DataGenericMapper Default
WriteToDB WriteAction Microsoft.SystemCenter.CollectPerformanceData Default
WriteToDW WriteAction Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData Default

Source Code:

<Rule ID="Microsoft.SQLServer.2017.Windows.CollectionRule.DBFileGroupFx.CheckpointFile.Active" Target="SQL2017WD!Microsoft.SQLServer.2017.Windows.DBFilegroupFx" Enabled="true">

  <Category>PerformanceCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Microsoft.SQLServer.2017.Windows.DataSource.HKFilePairs">

      <MachineName>$Target/Host/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/MachineName$</MachineName>

      <InstanceName>$Target/Host/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/InstanceName$</InstanceName>

      <ConnectionString>$Target/Host/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.DBEngine"]/ConnectionString$</ConnectionString>

      <MonitoringType>$Target/Host/Host/Property[Type="SQL2017WD!Microsoft.SQLServer.2017.Windows.DBEngine"]/MonitoringType$</MonitoringType>

      <DatabaseName>$Target/Host/Property[Type="SQL2017L!Microsoft.SQLServer.2017.Library.Database"]/DatabaseName$</DatabaseName>

      <State>2</State>

      <SqlTimeoutSeconds>15</SqlTimeoutSeconds>

      <TimeoutSeconds>300</TimeoutSeconds>

      <IntervalSeconds>900</IntervalSeconds>

      <SyncTime/>

    </DataSource>

  </DataSources>

  <ConditionDetection ID="Mapper" TypeID="SystemPerf!System.Performance.DataGenericMapper">

    <ObjectName>Memory-Optimized Filegroup</ObjectName>

    <CounterName>Active Checkpoint File Pairs</CounterName>

    <InstanceName/>

    <Value>$Data/Property[@Name='Count']$</Value>

  </ConditionDetection>

  <WriteActions>

    <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData"/>

    <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData"/>

  </WriteActions>

</Rule>