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
Why does Nodbc perform very slow on native database (Nav2009)
Klaassen
Member Posts: 1
After some strugles we succeeded in connecting DMS Document Management System with Nav2009R2 fdb database through NODBC, to enrich data in DMS (Content Central).
But performance is very bad. At the moment it is reading ca. 300 invoice header per hour.
We are using NO. to find recod in sale invoice header table using SELECT [fieldnames] FROM Sales Invoice Header WHERE No. = [invoice number]
Documents imported in DMS are enriched one by one through NODBC connection. NODBC logs in retrieves data logs out for each file in DMS.
Although field No. is first and only field in one of the index keys performance still is bad.
On server 2012 which runs DMS only NODBC is installed (no classic client installed, which isn't neccessary it´s not a workstation).
I used ODBC in the past to import financial data into excel sheets which worked fine even though these were flowfields.
Has someone any ideas how to increase performance. Loading history (several years) into DMS takes too much time this way.
But performance is very bad. At the moment it is reading ca. 300 invoice header per hour.
We are using NO. to find recod in sale invoice header table using SELECT [fieldnames] FROM Sales Invoice Header WHERE No. = [invoice number]
Documents imported in DMS are enriched one by one through NODBC connection. NODBC logs in retrieves data logs out for each file in DMS.
Although field No. is first and only field in one of the index keys performance still is bad.
On server 2012 which runs DMS only NODBC is installed (no classic client installed, which isn't neccessary it´s not a workstation).
I used ODBC in the past to import financial data into excel sheets which worked fine even though these were flowfields.
Has someone any ideas how to increase performance. Loading history (several years) into DMS takes too much time this way.
0