SQL Diagnostic Manager Console now communicates with multiple DMSO Management Clusters, consolidating the collected data to present it in a single view.
DMSO Management Clusters Architecture
Windows Console maintains knowledge and connections to a single SQL Repository and a single DM Management service. To access any data instance SQL DM queries to a single DM repository.
With the existence of multiple DM Repositories and Management Services in cluster environments, DMSO Manager maps cluster layers. To do so, it relies on cluster metadata.
DMSO Cluster Metadata
DMSO Cluster Metadata describes which monitored instance is owned by a specific Management Cluster. Besides, Metadata is part of the mapping layer process.
This process is achieved by
- Intercepting references to the DM Repository and DM Management Service.
- Mapping the DM Repository and DM Management service reference information to the appropriate DM Repository or Repositories.
- Correctly assembling the data when more than one Repository contributes to the results.
DMSO Cluster Database
DMSO Cluster Database stores and maintains the data collected by the metadata. This data may
- Exist on a stand-alone server for performance and scalability reasons.
- Be provisioned on one of the management Clusters.
The DM Windows Console reads the instance to Management Cluster mappings into memory and maintains these mappings as a cache to speed instance to Management Cluster mappings.
DMSO Cross Cluster Metadata
Some elements of the metadata utilized by the Diagnostic Manager are system-wide items, such as DMSO Users.
DMSO Users are defined in the context of the whole scale-out cluster deployment. All Management Clusters are provisioned with the same users which execute with the same level of permissions across all the clusters.
Note
When you add a DMSO user, SQL Diagnostic Manager provisions it across all Management Clusters.