February 28, 2023 at 3:39 pm
Hi there,
I just wanted peoples opinion on what I've seen in the Mirroring Monitor.
We are encountering a few odd issues where dotnet app seem to intermittently try to connect to our DR DB.
Naturally we gone through all of our connections strings.
Our current thinking is that sometimes the mirror server is not responding to the principle, the databases loses connection and this is when the issue the occurs.
Anyway, I just wonder what people thoughts are.
The DB stuff is a relatively recent DB that I established mirroring for and only has one entry.
The DB Things in an old DB and the one associated with the one with are having issues with.
You can see that the first entry has the sql server name on the primary but does not have the sql alias.
So the DB Mirroring entries for Things goes as.
PROD SQL Server > DR SQL Server\Alias
PROD SQL Server\Alias > DR SQL Server\Alias
Every sql I run in terms of looking at the mirror and its endpoints just returns one record for this DB , but the mirroring Monitor shows two records.
What to people think? Could that cause and issues with connections? Would we consider dropping the mirroring and recreate it?
March 1, 2023 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply