Book Image

Administrating Microsoft Dynamics 365 Business Central Online

By : Andrey Baludin
Book Image

Administrating Microsoft Dynamics 365 Business Central Online

By: Andrey Baludin

Overview of this book

This book features all the information you need to get started with administrating Microsoft Dynamics 365 Business Central Online. It contains detailed information about the admin portal and cloud migration process, all based on real usage experience. The book starts by covering the data migration process for developers, which will show you how to organize the data without code. You’ll also learn how the admin portal can be useful if you want to export a database copy, restore a backup, and set up telemetry to get detailed information about the call stack and operation statuses. As you progress, you’ll learn how to check your Business Central SaaS environment details, create new and different types of environments, and notifications, and keep your cloud data within limits. Later, you’ll explore how to set up cloud migration from an on-premise environment to SaaS, run the migration, upgrade data, and fix problems if something goes wrong. By the end of this book, you’ll be able to create new production and sandbox environments, restore them from backups, analyze environment telemetry, and confidently migrate your data to the cloud.
Table of Contents (15 chapters)
Part 1: Dynamics 365 Business Central Admin Center
Part 2: Dynamics 365 Business Central Cloud Migration Tool

Issues in the course of implementation

I created a copy of the customer's production database and started replication.

First issue

The first issue I met was that on-premises databases were in Azure SQL. From the migration admin's point of view, it looked perfect. You don't need to install Integration Runtime and setup runs faster. We were happy until the migration finished and we opened the migrated company in the cloud. The source database had a Cyrillic collation and the destination database had Latin. All Cyrillic text transformed into ??? characters, and after communicating with different people, I realized that there is no way to migrate different collations this way. We had to migrate to the on-premises SQL Server first. I know that this problem still exists because I've heard the same problem raised by colleagues at conferences.

After the migration to SQL Server on-premises, replication finished successfully and no more issues occurred. We decided...