OS Loaded Modules

The OS Loaded Modules collection captures data from sys.dm_os_loaded_modules. This DMV returns a row for each module loaded into the SQL Server address space.

Why collect this data?#

Some modules such as antivirus software are known to cause issues when loaded into SQL Server address space. These problems might vary from performance issues to weird bugs and corruption.

More information:

• Performance and consistency issues when certain modules or filter drivers are loaded.
• Detours or similar techniques may cause unexpected behaviors with SQL Server.
• How to choose antivirus software to run on computers that are running SQL Server

Reporting#

If you go to the OS Loaded Modules tab under the “Checks” node in the tree, you will see if there are issues with loaded modules for any instance.

If you see any instances highlighted red, review the Notes column and click to drill down for more information. You might need to update your AV software configuration.

Configuring#

If you see a warning for a “Unknown Module”, you can update the configuration to display either red or green after evaluating the module. Click the configuration button on the toolbar.

The LIKE operator is used to match on Name, Company and Description. Leave any value as % to match all values - for example, you might want to match on just the Module name. The status column should be specified as:

• 1 - Critical (Red)
• 2 - Warning (Orange)
• 3 - N/A (Grey)
• 4 - OK (Green)

The Notes column is used to provide some context information about this rule.

If you click the “Show System” checkbox, you will see the system provided values. The system values can’t be updated or deleted.

To delete a rule, click the row header and press the Delete button on the keyboard.

How status is determined#

It’s possible that a module will match multiple rules. The first match with the highest status value will be used to assign the status. If a module matches 4 - OK and 1 - Critical, the status will be 1 - Critical.