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
- 267 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
Transaction Speed
RChurchill
Member Posts: 55
Hi,
At the moment we are running 3.70 with a native database. When we run some very heavy batch processes we run them on the same server as the database connected locally and the speed and performance increases a lot.
We are going to migrate to sql with a later version of navision (probably NAV 2009). We have never run navision with sql before and would like to know if the above principal would still apply. Should (can) we run heavy processes on the same server as the sql database in order to speed things up.
Also the administrator is looking at setting up a clustered Microsoft SQL*Server back-end with shared application servers replicated in the two data centres. Any advice or experiences that can be shared on this set up would be invaluable.
Many thanks in advance
Rob
At the moment we are running 3.70 with a native database. When we run some very heavy batch processes we run them on the same server as the database connected locally and the speed and performance increases a lot.
We are going to migrate to sql with a later version of navision (probably NAV 2009). We have never run navision with sql before and would like to know if the above principal would still apply. Should (can) we run heavy processes on the same server as the sql database in order to speed things up.
Also the administrator is looking at setting up a clustered Microsoft SQL*Server back-end with shared application servers replicated in the two data centres. Any advice or experiences that can be shared on this set up would be invaluable.
Many thanks in advance
Rob
0
Comments
use transaction log replacation
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n