eG Monitoring
 

Measures reported by SqlAzuCpyTest

Replication provides redundancy and increases data availability. With multiple copies of data on different database servers, replication provides a level of fault tolerance against the loss of a single database server.

Active geo-replication enables you to configure up to four readable secondary databases in the same or different data center locations (regions). Secondary databases are available for querying and for failover if there is a data center outage or the inability to connect to the primary database. The failover must be initiated manually by the application of the user. After failover, the new primary has a different connection end-point. Azure SQL Database auto-failover groups is a SQL Database feature designed to automatically manage geo-replication relationship, connectivity, and failover at scale. With it, the customers gain the ability to automatically recover multiple related databases in the secondary region after catastrophic regional failures or other unplanned events that result in full or partial loss of the SQL Database service's availability in the primary region. Additionally, they can use the readable secondary databases to offload read-only workloads. If you are using active geo-replication and for any reason your primary database fails, or simply needs to be taken offline, you can initiate failover to any of your secondary databases. When failover is activated to one of the secondary databases, all other secondaries are automatically linked to the new primary. If swift failover does not occur, then, there may be a lag in data transfer to the secondary databases. This may lead to the unavailability of data to the secondary databases which would eventually hamper the replication process. Therefore, it is necessary to check whether the geo-replication feature is enabled, and if enabled, it becomes mandatory to check the status of the primary and secondary databases and the status of replication to the secondary databases. The SqlAzuCpyTest test helps administrators in this regard!

This test auto-discovers the database instances on the target Microsoft SQL Azure database server and for each database instance, reports whether/not geo-replication is enabled. If geo-replication is enabled, this test reports whether the database instance is a primary or secondary database and the current status of replication.

Outputs of the test : One set of results for each database instance on the target Microsoft SQL Azure database server being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Is_georeplic_enabled Indicates whether/not the geo-replication feature is enabled on this database instance.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the geo-replication feature is enabled on this database instance. The graph of this measure however, represents the status of a server using the numeric equivalents only.
Is_primary Indicates whether/not this database instance is the primary database.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not this database instance is the primary database. However, the graph of this measure is represented using its corresponding numeric equivalents only - 0 or 1.
Is_secondary Indicates whether/not this database instance is the secondary database.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not this database instance is the secondary database. However, the graph of this measure is represented using its corresponding numeric equivalents only - 0 or 1.
Replication_Status Indicates the current status of replication on this database instance.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Seeding 1
Catch up 2
Pending 3

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current status of replication on this database instance. However, the graph of this measure is represented using its corresponding numeric equivalents - 1 to 3.
Replication_lagging Indicates the time duration in seconds, that replication to this database instance lags. Seconds A high value for this measure is a cause of concern. If the value of this measure is high, then, it may indicate that the databases are out of sync and data cannot be accessed from the databases when a failover occurs.
Secondary_database_mode Indicates the mode of the secondary database.   The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
No 0
All 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the mode of the secondary database. However, the graph of this measure is represented using its corresponding numeric equivalents only - 0 or 1.