Microsoft Dynamics NAV 2013 R2 separates tables that describe the application from the tables that contain business data. Depending on your deployment scenario, you can choose to store all Microsoft Dynamics NAV tables in one database, or you can export the application tables to a dedicated database.
The application tables are system tables that define the application. Other system tables remain in the business data database.
Application Database versus Business Data Databases
The application database contains tables that describe your application. The data that users enter in your application is stored in the business data database because this data is specific to their company. Optionally, you can create multiple business data databases, such as if you want to support your customers as tenants. The information about the application that is shared by all tenants is stored in the dedicated application database.
When you have exported the application tables to a separate database, you can no longer access the business database from the Microsoft Dynamics NAV Development Environment. This is because the metadata for the tables in the business database is stored in the application database and modified in that database.
For example, if you want to modify a report, and your solution is used by 25 customers, you modify the report in the application database. When each customer then accesses the report, they see the modified report.
Distribution of the System Tables in Each Database
The following table describes which system tables are moved to the application database when you run the Export-NAVApplication cmdlet and which tables remain in the business data database.
|Application database||Business data database|
Client Add-in Resources
Object Metadata Snapshot
Page Data Personalization
Report List Translation
User Default Style Sheet