SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Client side automatic reconnect fails after DB failover when SQL Server on non-default ports


Client side automatic reconnect fails after DB failover when SQL Server on non-default ports

Author
Message
radek.hruby
radek.hruby
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1346 Visits: 204
This sound logically to me. Good hint. Thank you very much - I need to check this.
muth_51
muth_51
SSC Eights!
SSC Eights! (935 reputation)SSC Eights! (935 reputation)SSC Eights! (935 reputation)SSC Eights! (935 reputation)SSC Eights! (935 reputation)SSC Eights! (935 reputation)SSC Eights! (935 reputation)SSC Eights! (935 reputation)

Group: General Forum Members
Points: 935 Visits: 2905
"When a SqlConnection is successfully opened, the failover partner name is returned by the server and supersedes any values supplied in the connection string” indicates the failover partner name is returned. This would be the same failover partner name that you use for the Primary/Mirror relationship.

It sounds like in your case you would want to make sure that the application is able to contact the mirror based upon that failover partner name. If you run the query on the primary in the mirror:
select * from sys.database_mirroring

You can see the mirroring_partner_instance will be what is returned and what it is going to connect to. I hope this information helps.
radek.hruby
radek.hruby
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1346 Visits: 204
I'm aware of this ... but the application can't connect to the mirror just by its name - when the port information is missing ... and this is in my opinion the root cause. When I failover the database to the secondary server, on the client computer I can see attempts for connections to the secondary server but ON THE DEFAULT SQL TCP PORT 1433 (via TCPView). The "only" question is why aliases and/or default SQL port don't work.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search