Azure failover database showing exactly same data as primary
postledm
Posts: 10 New member
This is weird.
I have added a new Azure SQL database that has a replication partner. (not built by me)
Users connect to the failover group name
Monitor shows the same activity on the DR database as the prod database. Even though there is no direct activity on the DR database.
I have plenty of other Azure SQL databases that don't do this. All connections are to the failover group name and their activity is only recorded on the prod server.
Reporting queries run directly on the DR database and only that activity is what I see in Monitor.
Has anyone else seen this ?
the only difference I can see is the new database using the dtu model whereas all my existing database uses vcore model
I have added a new Azure SQL database that has a replication partner. (not built by me)
Users connect to the failover group name
Monitor shows the same activity on the DR database as the prod database. Even though there is no direct activity on the DR database.
I have plenty of other Azure SQL databases that don't do this. All connections are to the failover group name and their activity is only recorded on the prod server.
Reporting queries run directly on the DR database and only that activity is what I see in Monitor.
Has anyone else seen this ?
the only difference I can see is the new database using the dtu model whereas all my existing database uses vcore model
Tagged:
Answers
When you say DR database, just to clarify, are you talking about the replicated database? I ask because we sometimes call our Data Repository database for Monitor a DR. Also, does the activity show on both or just the DR?
I don't believe that the dtu vs vcore model would have any impact on this as that is just a billing model. Are there any other differences between the new database and the others? To diagnose further, I'd likely need to look into the logs to see what is happening.