Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Database open: Server Name
FDickschat
Member Posts: 380
My question is: In the Database open Dialog, what exactly is the "Server Name" and could I use an alias instead of the real server name?
Let me explain the question:
(NAV 2009 SP1 Classic (30212), SQL Server 2005 Enterprise x64, no named instances, only 1 Sql server installed on the box)
A client of mine would like to take away the burden of changing the Server Name from the End Users in case the Primary Server goes down and the secondary has to take over (Client is still evaluating Log shipping / DB Mirroring, Clustering is currently out of scope). If this happens all users will need to change the servername in the client. Also on all NAS and on some 3rd party tools this needs to be changed.
The client would like to use some kind of alias on all clients accessing the DB which could be changed centrally if desaster strikes. Then the only thing left for the end users would be to restart the client and NAV would automatically connect to the secondary server.
The idea of the customer was to create a DNS alias which is used from the clients as the servername but this does not work. Example:
Primary Server Name: SERVER1
Secondary Server Name: SERVER2
DNS Alias: NAV (points to SERVER1)
Using NAV as a servername does work and the Nav Client connects to SERVER1. But when you reopen the database open dialog the name NAV has been replaced with SERVER1. So somehow the client was able to resolve the name NAV into SERVER1.
The second test was with a DNS host entry with the same IP as SERVER1 but gave the same result as test 1.
This is where my question comes in: What exactly is the "Server Name" and how could the above request be solved? A sql cluster would probably solve this, am I correct?
Thanks for your help.
Let me explain the question:
(NAV 2009 SP1 Classic (30212), SQL Server 2005 Enterprise x64, no named instances, only 1 Sql server installed on the box)
A client of mine would like to take away the burden of changing the Server Name from the End Users in case the Primary Server goes down and the secondary has to take over (Client is still evaluating Log shipping / DB Mirroring, Clustering is currently out of scope). If this happens all users will need to change the servername in the client. Also on all NAS and on some 3rd party tools this needs to be changed.
The client would like to use some kind of alias on all clients accessing the DB which could be changed centrally if desaster strikes. Then the only thing left for the end users would be to restart the client and NAV would automatically connect to the secondary server.
The idea of the customer was to create a DNS alias which is used from the clients as the servername but this does not work. Example:
Primary Server Name: SERVER1
Secondary Server Name: SERVER2
DNS Alias: NAV (points to SERVER1)
Using NAV as a servername does work and the Nav Client connects to SERVER1. But when you reopen the database open dialog the name NAV has been replaced with SERVER1. So somehow the client was able to resolve the name NAV into SERVER1.
The second test was with a DNS host entry with the same IP as SERVER1 but gave the same result as test 1.
This is where my question comes in: What exactly is the "Server Name" and how could the above request be solved? A sql cluster would probably solve this, am I correct?
Thanks for your help.
Frank Dickschat
FD Consulting
FD Consulting
0
Comments
In the database open dialog as the server name NAVTest1 is used. NAV finds the DB server and connects ok. After the connection is made the database open dialog shows SERVER1 again.
In the database open dialog as the server name NAVTest2 is used. NAV finds the DB server and connects ok. After the connection is made the database open dialog shows SERVER1 again.
In both cases SSMS connects to the alias and shows the alias as the server name.
Obviously NAV still resolves the real server name somehow. Does anyone have any other idea?
FD Consulting