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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Specific installation in three layers
RMarc
Member Posts: 36
Hi all,
I need our help!!
One of my customers want to move the SQL database off-site and leave within Dynamics NAV client's and Navision Service Tier.
The middle layer and the database are connected by a tunnel of 10 MB.
I have doubts about whether this type of installation is possible and will work well, ie if users will not notice slow to work with Navision.
Thanks in advance!!
I need our help!!
One of my customers want to move the SQL database off-site and leave within Dynamics NAV client's and Navision Service Tier.
The middle layer and the database are connected by a tunnel of 10 MB.
I have doubts about whether this type of installation is possible and will work well, ie if users will not notice slow to work with Navision.
Thanks in advance!!
0
Comments
I'd be concerned in your situation too. Whilst I haven't look too deeply into this and can't really say what to expect as far as performance would go, I think the following two points should be important to you in making the decision:
Firstly, how many concurrent users does the site have? Obviously performance will vary depending on this number. If they are a fairly large site then personally I would straight out say no to them doing this.
Secondly, if you HAVE to go down this path, I believe the Service Tier should be kept on the side of the WAN that the database is on. Most of the processing should be done between the database and service tiers, and the client really only displays the information. With that setup the performance shouldn't be anywhere near as bad as if it is kept where it is.
That said, I haven't looked into this scenario in too much detail, so I'd wait for some more input. But logically this is how a 3-tier program should operate, all the heavy stuff is done between database and 'business layer' (NAV Service), and the lighter interaction/display is done between client and 'business layer'.