Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
AlwaysOn High Availability Groups on SQL with Microsoft NAV
ShaNas
Member Posts: 6
in SQL General
AlwaysOn High Availability Groups on SQL with Microsoft NAV
I have planned to do setup AlwaysOn High Availability Groups for SQL with primary & one secondary. My question is how to connect with Microsoft Navision Application & during failover how connection will get changed to connect with secondary db as primary.
I have planned to do setup AlwaysOn High Availability Groups for SQL with primary & one secondary. My question is how to connect with Microsoft Navision Application & during failover how connection will get changed to connect with secondary db as primary.
0
Answers
As mentioned by BlackTiger, this is a SQL feature.
We use this setup, and it works really well. It provides more stability, and also allows us to force external reports used in our Web Applications to read from the Secondary Node, to take load off the Primary Node.
All NAV Clients, connect to the availability group. When the Primary Node of the Availability Group goes down, it will automatically switch to the Secondary Node, making it available for write transactions.
Can you explain how it will get connect automatically as Server names are different.
Ex. Primary DB running Node 1 and Secondary DB running Node 2. If Node 1 get failover how Node 2 will get automatically connect. Is there any setup to be done in NAV ?
Compare it with network load balance (NLB) cluster for NAV. You use a DNS name or IP to connect to the NLB cluster and the NLB redirects you to one of the nodes. Clients do not connect to a node (application server) directly.
The SQL server fail over cluster works basically the same. You connect the NAV Service Tier (NST) to the cluster and not to a SQL node directly. So you don't have to configure anything special in NAV.
The cluster will redirect the NSTs to the active SQL node. After fail over the address of the cluster stays the same. The cluster will then redirect the NST to the other SQL server that has became the active node.
How does it react if the SQL servers and NAV Servers Nodes are on 2 different sites and the connection would breakdown, would both sites be able to continue to operate and when the connection is reactivated the data able to syncronize?