Configuration Running Values Differs From Configured

When a configuration option in SQL Server is set to a value different from the one currently in use, it often means that the change requires a restart to take effect. This difference can lead to unexpected behavior until the restart is completed, which is why it’s essential to resolve these mismatches.

Why Running Values Differ From Configured

  • Restart Required: Some settings need a SQL Server restart to apply the configured values. Until that restart occurs, SQL Server will continue using the old value.

  • Potential Misconfiguration: Running with mismatched values could cause issues such as performance degradation, security concerns, or unexpected behavior.

Suggested Action

  • Restart SQL Server: Schedule a restart of the instance to apply the configured values.

  • Revert the Changes: If the restart isn’t possible or needed, revert the changes to match the running values.

How to Compare Startup and Running Configurations in SQL Server

You can compare the configured values with the current running values using the following SQL query:

SELECT name,
       value,
       value_in_use
FROM sys.configurations
WHERE value <> value_in_use;

This query lists all configuration options where the configured value differs from the running value, helping you identify what needs to be adjusted.

How Aireforge Detects Configuration Mismatches

Aireforge automatically checks for configuration mismatches and highlights any discrepancies between the configured and running values. It provides recommendations on whether a restart is needed or if the configuration can be adjusted without restarting the instance. By running these checks regularly, you can prevent potential performance or stability issues caused by misconfigurations.