Collects the amount of free space available in the In-Memory OLTP File Group container (in Megabytes).
The rule collects the amount of free space available in the In-Memory OLTP File Group container (in Megabytes).
The In-Memory OLTP File Group Container folder typically grows over time as more data is added into In-Memory tables.
When the available disk space on the drive where the database storage location is configured becomes too low, failures can occur, preventing successful processing of data, delaying user’s queries, or affecting other applications, which share the same allocation of disk space.
The resolution(s) for low available disk space depend upon the root causes, which must be investigated in each case when this issue occurs. The condition may be alleviated by any of many potential approaches:
Decrease the amount of data being stored in In-Memory tables.
Remove data consuming disk space on the same drive with the In-Memory OLTP File Group Container folder.
Increase the size of the logical drive on which the In-Memory OLTP File Group Container folder is stored with Disk Manager.
Copy the In-Memory OLTP File Group Container folder in its entirety to a new drive with more available space.
Name | Description | Default Value |
Enabled |
| Yes |
Generates Alerts |
| No |
Interval (seconds) | The recurring interval of time in seconds in which to run the workflow. | 900 |
Script Delay (milliseconds) | This parameter sets the delay between consecutive T-SQL queries executed by the workflow. This may help to reduce the footprint generated by the workflow in case of large number of target objects. Please advise with Microsoft Support before changing this parameter. | 0 |
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 |
Target | Microsoft.SQLServer.2014.Container |
Category | PerformanceCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.SQLServer.2014.DataSource.Container.FreeSpacePerf | Default |
WriteToDB | WriteAction | Microsoft.SystemCenter.CollectPerformanceData | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData | Default |
<Rule ID="Microsoft.SQLServer.2014.CollectionRule.Container.SpaceFreeMB" Target="SQL2014Core!Microsoft.SQLServer.2014.Container" Enabled="true">
<Category>PerformanceCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.SQLServer.2014.DataSource.Container.FreeSpacePerf">
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
<ConnectionString>$Target/Host/Host/Host/Property[Type="SQL2014Core!Microsoft.SQLServer.2014.DBEngine"]/ConnectionString$</ConnectionString>
<ServerName>$Target/Host/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ServerName>
<SqlInstanceName>$Target/Host/Host/Host/Property[Type="SQL2014Core!Microsoft.SQLServer.2014.ServerRole"]/InstanceName$</SqlInstanceName>
<ObjectName>In-Memory OLTP Container</ObjectName>
<CounterName>In-Memory OLTP File Group container free space (MB)</CounterName>
<InstanceName/>
<DatabaseName>$Target/Host/Host/Property[Type="SQL2014Core!Microsoft.SQLServer.2014.Database"]/DatabaseName$</DatabaseName>
<DBFileId>$Target/Property[Type="SQL2014Core!Microsoft.SQLServer.2014.Container"]/ContainerID$</DBFileId>
<Value>$Data/Property[@Name='FreeSpaceSpaceMB']$</Value>
<TimeoutSeconds>300</TimeoutSeconds>
<ScriptDelayMsec>0</ScriptDelayMsec>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData"/>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData"/>
</WriteActions>
</Rule>