Click here to Skip to main content
14,742,361 members
Home » Discussions » Database
   

Database

 
GeneralRe: Problem with Access Pin
Tim Carmichael17-Jan-18 3:24
MemberTim Carmichael17-Jan-18 3:24 
QuestionOLEDB connection to a SQL server database hosted in an availability group (repost) Pin
kmoorevs2-Jan-18 12:38
Memberkmoorevs2-Jan-18 12:38 
AnswerRe: OLEDB connection to a SQL server database hosted in an availability group (repost) Pin
PIEBALDconsult2-Jan-18 15:12
professionalPIEBALDconsult2-Jan-18 15:12 
GeneralRe: OLEDB connection to a SQL server database hosted in an availability group (repost) Pin
kmoorevs4-Jan-18 9:33
Memberkmoorevs4-Jan-18 9:33 
AnswerRe: OLEDB connection to a SQL server database hosted in an availability group (repost) Pin
Joe DiNatale4-Jan-18 12:10
MemberJoe DiNatale4-Jan-18 12:10 
GeneralRe: OLEDB connection to a SQL server database hosted in an availability group (repost) Pin
kmoorevs4-Jan-18 12:33
Memberkmoorevs4-Jan-18 12:33 
GeneralRe: OLEDB connection to a SQL server database hosted in an availability group (repost) Pin
S Douglas7-Mar-18 12:35
professionalS Douglas7-Mar-18 12:35 
AnswerRe: OLEDB connection to a SQL server database hosted in an availability group (repost) Pin
S Douglas7-Mar-18 12:31
professionalS Douglas7-Mar-18 12:31 
Interesting, I've setup a couple of Availability groups for applications but never had any issues (well once I got the devs to stop trying to use the IPs).

I wonder if the issues you faced are related to
Create or Configure an Availability Group Listener (SQL Server) | Microsoft Docs

[Snippet]
Issue: If your Availability Group or Failover Cluster Instance has a listener name (known as the network name or Client Access Point in the WSFC Cluster Manager) depending on multiple IP addresses from different subnets, and you are using either ADO.NET with .NET Framework 3.5SP1 or SQL Native Client 11.0 OLEDB, potentially 50% of your client-connection requests to the availability group listener will hit a connection timeout.

Workarounds: We recommend that you do one of the following tasks.

If do not have the permission to manipulate cluster resources, change your connection timeout to 30 seconds (this value results in a 20-second TCP timeout period plus a 10-second buffer).

Pros: If a cross-subnet failover occurs, client recovery time is short.

Cons: Half of the client connections will take more than 20 seconds

If you have the permission to manipulate cluster resources, the more recommended approach is to set the network name of your availability group listener to RegisterAllProvidersIP=0. For more information, see "RegisterAllProvidersIP Setting” later in this section.

Pros: You do not need to increase your client-connection timeout value.

Cons: If a cross-subnet failover occurs, the client recovery time could be 15 minutes or longer, depending on your HostRecordTTL setting and the setting of your cross-site DNS/AD replication schedule.
[/Snippet]

In all likely hood the issue was the RegisterAllProvidersIP. If the HA Group is running in a multi subnet cluster. Then for every Node in the HA group its IP is published to DNS, So if there are 5 nodes that it can live on, there are five different IPs listed in DNS. Traversing them all can take some time to find the right one currently active.

Easy fix, set RegisterAllProvidersIP to 0.

Common sense is admitting there is cause and effect and that you can exert some control over what you understand.


QuestionMore than interesting... Pin
Kornfeld Eliyahu Peter31-Dec-17 22:05
professionalKornfeld Eliyahu Peter31-Dec-17 22:05 
AnswerRe: More than interesting... Pin
Jörgen Andersson1-Jan-18 4:44
professionalJörgen Andersson1-Jan-18 4:44 
GeneralRe: More than interesting... Pin
Kornfeld Eliyahu Peter1-Jan-18 5:31
professionalKornfeld Eliyahu Peter1-Jan-18 5:31 
GeneralRe: More than interesting... Pin
Jörgen Andersson2-Jan-18 6:28
professionalJörgen Andersson2-Jan-18 6:28 
SuggestionRe: More than interesting... Pin
Richard Deeming8-Jan-18 8:22
mveRichard Deeming8-Jan-18 8:22 
GeneralRe: More than interesting... Pin
Jörgen Andersson8-Jan-18 10:03
professionalJörgen Andersson8-Jan-18 10:03 
GeneralRe: More than interesting... Pin
Richard Deeming9-Jan-18 2:26
mveRichard Deeming9-Jan-18 2:26 
GeneralRe: More than interesting... Pin
Jörgen Andersson9-Jan-18 9:39
professionalJörgen Andersson9-Jan-18 9:39 
AnswerRe: More than interesting... Pin
jschell1-Jan-18 8:04
Memberjschell1-Jan-18 8:04 
GeneralRe: More than interesting... Pin
Kornfeld Eliyahu Peter1-Jan-18 9:23
professionalKornfeld Eliyahu Peter1-Jan-18 9:23 
GeneralRe: More than interesting... Pin
ZurdoDev8-Jan-18 9:05
professionalZurdoDev8-Jan-18 9:05 
QuestionTrigger value > ? write in different table Pin
brian121026-Dec-17 14:44
Memberbrian121026-Dec-17 14:44 
AnswerRe: Trigger value > ? write in different table Pin
Victor Nijegorodov26-Dec-17 23:13
MemberVictor Nijegorodov26-Dec-17 23:13 
AnswerRe: Trigger value > ? write in different table Pin
Richard MacCutchan26-Dec-17 23:41
mveRichard MacCutchan26-Dec-17 23:41 
Rant[REPOST] Trigger value > ? write in different table Pin
Richard Deeming8-Jan-18 8:24
mveRichard Deeming8-Jan-18 8:24 
Questiondata between 1st jan to December 31st of previous year query --no hard coded dates. Pin
sai.201226-Dec-17 11:51
Membersai.201226-Dec-17 11:51 
AnswerRe: data between 1st jan to December 31st of previous year query --no hard coded dates. Pin
Victor Nijegorodov26-Dec-17 23:06
MemberVictor Nijegorodov26-Dec-17 23:06 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.