Why does BC (on prem) have multiple SQL tables where NAV had one?

Miklos_Hollender
Miklos_Hollender Member Posts: 1,629
in NAV Three Tier

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.

Best Answer

  • vaprog
    vaprog Member Posts: 1,173
    Answer ✓

    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.

Answers

  • vaprog
    vaprog Member Posts: 1,173
    Answer ✓

    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.

  • Miklos_Hollender
    Miklos_Hollender Member Posts: 1,629

    Thank you! So this means if I do not need the extension data in a query, report, then it should be safe to use the original table only.

Categories