Why does BC (on prem) have multiple SQL tables where NAV had one?
We have like 5 Sales_Invoice_Line_fsdfdws8. 250GB DB, maybe split up for performance, dunno.
It makes SQL queries impossible, and I want to use SQL queries because I need reports over multiple different software and databases, servers. That is because we have basically 2 different ERP solutions for different subsidiaries.
Without SQL queries, how to do that? I guess I could join them together in a view, but that would need constant maintenance. Also some of these tables are somehow not queriable.
Answers
-
That is because of extension apps. Each tableextension object creates it's own database table.
If you need to query data, join what you need for your query.
If you want to backup data, don't care in what table the data is stored.
I assume there is information somewhere in the database as to which table extends which table of the base app.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 323 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
