Verifying the M3 DMP Database changes after migration

Each DmpX and DMPEmpty database has a Cycle table to handle the history of transactions made to the version.

A new column named VersionSchema is added to the DmpVersion.DBVersion table as well. This field serves as a link to the provision database and allows the application to retrieve the necessary connection information to establish a database connection.

All databases continue to use dbo as a default schema and retain the existing users with their corresponding permissions. Database Properties displays the list of users and roles for the selected database, along with their assigned permissions, confirming that existing user accounts and access rights remain unchanged.

All DMP database fields with ID as a prefix or postfix follow the case ID (for example, BaseListID and KeyID).This casing matches the M3 Appservices casing and is crucial if the database setup uses BIN2 collation.

A new provision database is created to manage information for all tenants when multiple tenants are configured. The provision database Collation matches the collation of the DmpX databases.

The provision database contains a tenants table storing Tenant ID, database connection details, and credentials, enabling the application to connect to the appropriate tenant database.