Azure-docs: Replication lag

[LuisGonzalezLT]

Is there a way to see how far behind the replica is? I tried the same approach as for geo-replicas using dm_geo_replication_link_status but got nowhere. dm_hadr_database_replica_states doesn't work in Azure SQL Database.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7a2961d1-4448-11b7-2dc2-3b738bd70939
• Version Independent ID: 206eb022-25c4-66d7-7285-0d53a84956e3
• Content: Azure SQL Database - read queries on replicas
• Content Source: articles/sql-database/sql-database-read-scale-out.md
• Service: sql-database
• GitHub Login: @anosov1960
• Microsoft Alias: sashan

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT Thanks for the feedback. We are actively investigating and will get back to you soon.

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT I am showing that sys.dm_geo_replication_link_status (Azure SQL Database) is to return "Show replication lags and last replication time of my secondary databases." Example:

SELECT
link_guid
, partner_server
, last_replication
, replication_lag_sec
FROM sys.dm_geo_replication_link_status;

What is sys.dm_geo_replication_link_status not providing you?

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[LuisGonzalezLT]

It worked fine for a geo-replica, but didn't work for the replica opened up
by read scale out.

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT Thanks for the feedback. I will look into read-out scale Powershell cmdlets.

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT I think this is what you are looking for: sys.dm_operation_status (Azure SQL Database)

Example:
SELECT * FROM sys.dm_operation_status WHERE major_resource_id = ‘myddb’ ORDER BY start_time DESC;

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT Please let me know if the above does not meet your needs. I can reopen this issue and continue the investigation or have you create a feature request in the Azure SQL User Voice. Thanks, ~Mike

[LuisGonzalezLT]

Coming back to revisit this after a long hiatus. Sorry for the delay.
sys.dm_operation_status isn't what I need.
What I am specifically looking for is a version of:
SELECT * FROM sys.dm_geo_replication_link_status
that reports on the read scale-out replica, not the geo-replica, so I can see what the lag time is of the read scale-out replica.
sys.dm_geo_replication_link_status only reports on geo-replicas.

[LuisGonzalezLT]

@Mike-Ubezzi-MSFT Just checking to see if we may be able to take a peek at this ^ again.

[Mike-Ubezzi-MSFT]

This is a forum question but looking into this now. The MSDN and Stack Overflow forums have more eyeballs looking at questions. This channel is specific to correcting/enhancing the documentation. If this information is something that could enhance the documentation, we can look into adding it, etc. Thanks, Mike!

[LuisGonzalezLT]

Yeah - I put a formal feature request in for it over in the "How can we
improve Azure SQL Database?" forum. Thanks :-)

[Mike-Ubezzi-MSFT]

I have a question out to an individual. I will get back with you....

[LuisGonzalezLT]

Much appreciated.

On Mon, Dec 17, 2018 at 1:05 PM Mike Ubezzi [e-mail]
wrote:

I have a question out to an individual. I will get back with you....

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13693#issuecomment-447940558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AolEIp3h4y28MGq0AQMSL-f738DLX5_iks5u59zdgaJpZM4WEZus
.

[Mike-Ubezzi-MSFT]

@LuisGonzalezLT Okay, so there is no solution to this at the moment. The User Voice is the best channel to address this. Thanks for following up!

[LuisGonzalezLT]

OK. Thanks for checking into it. It didn't seem like there was a way so
that confirms what I thought.

On Mon, Dec 17, 2018 at 4:16 PM Mike Ubezzi [e-mail]
wrote:

@LuisGonzalezLT https://github.com/LuisGonzalezLT Okay, so there is no
solution to this at the moment. The User Voice is the best channel to
address this. Thanks for following up!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13693#issuecomment-448001629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AolEIuuTdQDQdZWkUEqpO1aEarn8QlTtks5u6AmfgaJpZM4WEZus
.

[MatthewSteeples]

Just in case anyone else wants to vote, here is the uservoice - https://feedback.azure.com/forums/217321-sql-database/suggestions/36299335-provide-insight-into-the-replication-lag-between-a