The total number of connections to the SMS site database has exceeded the standard operational threshold. If SMS processes are unable to obtain a SQL connection, standard SMS operations involving the SMS site database will be stopped. For example, this could prevent new inventory data from being added to the SMS site database or prevent new software distribution packages from being processed. Whether or not the situation worsens depends on the cause of the high number of connections.
The SMS site database connections can exceed the threshold because:
Management points are not using replicated SMS site databases, causing substantial queries to the SMS site database.
The SMS site database server has insufficient memory.
Other applications running on the installation of SQL Server are using many connections.
To resolve this issue and lower the SQL connections:
If the SQL Server default has been modified so it is not configured for an infinite number of connections, configure it to allow more connections. If the SQL Server is configured to allow sufficient connections, or to allow unlimited connections, verify that there is sufficient memory to allocate to those connections.
Investigate the possibility of dedicating a replicated SMS site database to the management point.
Use a dedicated installation of SQL Server for the SMS site database.
For more information about changing the number of SMS site database server connections, refer to your SQL Server product documentation.
For additional information about configuring connections in SQL Server 7.0 and SQL Server 2000, and about resolving error messages involving maximum connection limits, see article 320728 in the Microsoft Knowledge Base.
For more assistance, a list of additional support options is available in the support section of the SMS Web site at Support for Systems Management Server.
If this alert is generating too many false positives, you can modify the threshold tab of the rule properties to designate values more appropriate for your environment.
This alert is best handled by the SQL Server administrator in conjunction with the SMS administrator.
| Target | Microsoft.SMS.2003.SMS_Server_Class | ||
| Parent Monitor | DB | ||
| Category | StateCollection | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Mom2005ID='{ECF49FF9-5FDD-4D90-9273-6EC420D0FE29}' |
Home
ENU <UnitMonitor ID="SMS_2003_Perf_Threshold__SMS_SQL_Connections___500_over_2_hours_9_Rule.AdvancedAlertCriteriaMonitor" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType" Accessibility="Internal" Target="Microsoft.SMS.2003.SMS_Server_Class" Enabled="true" ParentMonitorID="DB" Comment="Mom2005ID='{ECF49FF9-5FDD-4D90-9273-6EC420D0FE29}'">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SMS_2003_Perf_Threshold__SMS_SQL_Connections___500_over_2_hours_9_Rule.AdvancedAlertCriteriaMonitor.StringResource">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Name$</AlertParameter1>
<AlertParameter2>$Data/Context/Description$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Success" MonitorTypeStateID="Success" ID="AlertLevelSuccess"/>
<OperationalState HealthState="Warning" MonitorTypeStateID="Warning" ID="AlertLevelWarning"/>
<OperationalState HealthState="Error" MonitorTypeStateID="Error" ID="AlertLevelError"/>
</OperationalStates>
<Configuration>
<ServerRole>SMS Server</ServerRole>
<Component>DB</Component>
<ServerRoleInstance>$Target/Property[Type="Microsoft.SMS.2003.SMS_Server_Class"]/Name_1$</ServerRoleInstance>
<RuleId>$MPElement[Name="SMS_2003_Perf_Threshold__SMS_SQL_Connections___500_over_2_hours_9_Rule"]$</RuleId>
<ErrorThreshold>500</ErrorThreshold>
<ErrorOperator>Greater</ErrorOperator>
<WarningThreshold>300</WarningThreshold>
<WarningOperator>Greater</WarningOperator>
</Configuration>
</UnitMonitor>