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
- 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
NAV database replication via SQL for read-access website
rsaritzky
Member Posts: 469
Hi all,
Has anyone used SQL Server Replication to create an "image" of the NAV database for outside query access? We have a high-volume website where the NAV database is being queried, and the website support team is concerned that the read queries will cause a performance issue. The database is fairly large (75 users, 135GB).
There are also transactions that are not read-only, e.g. orders are submitted to NAV, so we're not sure if/how certain web services (e.g. the read-only services) could be published in the replicated database and the read-write services published from the "primary" database. Since the replicated database is a copy of the primary database, the web service publish tokens would be the same.
Any ideas/opinions would be appreciated.
Has anyone used SQL Server Replication to create an "image" of the NAV database for outside query access? We have a high-volume website where the NAV database is being queried, and the website support team is concerned that the read queries will cause a performance issue. The database is fairly large (75 users, 135GB).
There are also transactions that are not read-only, e.g. orders are submitted to NAV, so we're not sure if/how certain web services (e.g. the read-only services) could be published in the replicated database and the read-write services published from the "primary" database. Since the replicated database is a copy of the primary database, the web service publish tokens would be the same.
Any ideas/opinions would be appreciated.
Ron
0