Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM config comparison between two configs never finishes for large config files

NCM config comparison between two configs never finishes for large config files

Updated: July 26, 2016

Overview

When you do a comparison between two configuration files (running vs startup) that are very large (about 16.000 lines), NPM sometimes does not finish the comparison.  

The first config you chose is loaded nearly instantly but as soon as the comparison begins, it does not continue. However, the comparison of smaller config-files (1500-2000) works fine.

 

Environment

NCM, all supported versions

Cause 

This behavior is known in NCM with very large config files.

 

Resolution

Use the Config Change report Job when comparing large configs.  

 

 

Last modified

Tags

Classifications

Public