Validating database schema

When you design a table in Microsoft Dynamics NAV, you define the metadata for the table, such as the name and object ID, and the fields and their data types.This table definition describes the table that must be created in the SQL Server database to store business data.In snapshot replication, a new copy of the schema is sent to the Subscriber each time synchronization occurs.Therefore, all schema changes (not just those listed above) to previously published objects are automatically propagated with each synchronization.You typically use the development environment to synchronize the table schema during development while you are making changes to a specific table.In the development environment, you can synchronize table schema changes for a specific table or for all tables.For information about disabling the replication of schema changes, see Replicate Schema Changes.Keep the following considerations in mind when replicating schema changes.

For example, the Sync-NAVTenant cmdlet can be used by system administrators who automate the process of applying application updates and upgrades in a multitenant environment.

With non-destructive changes, you can synchronize the schema without any special data handling considerations.

However, if you make destructive changes to the table definition, such as removing a field, then you will be warned by the development environment when you try to save the changes, and you must specify how to handle the data when synchronizing the schema.

Replication supports a wide range of schema changes to published objects.

When you make any of the following schema changes on the appropriate published object at a Microsoft SQL Server Publisher, that change is propagated by default to all SQL Server Subscribers: Important Schema changes to tables must be made by using Transact-SQL or SQL Server Management Objects (SMO).

Search for validating database schema:

validating database schema-84

Depending on the size of the tables that you modify and the nature of changes, the schema synchronization process can take anywhere from several seconds to several hours (for example.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “validating database schema”