According to Microsoft, a schema migration capability that is now widely accessible in Azure Database Migration Service (DMS) makes data movement easier by automatically including schemas, tables, indexes, views, and other database objects. Microsoft intends to guarantee consistency across source and target databases and lessen manual labor with this functionality.
Because of this integrated method, administrators no longer have to manually build all database objects on the new Azure SQL Database before moving the data over, including stored procedures, schemas, and indexes. In addition to saving a great deal of time, this will significantly lower the possibility of human error, which can be problematic during complicated migrations.
Users can now transfer missing schema objects along with specific tables or all tables at once using the new schema migration capability. Additionally, the Redmond behemoth notes that the feature is exclusive to migrations to Azure SQL Database.
The user must have SHIR version 5.37.8767.4 or higher installed in order to use the new capability, and the source SQL Server needs db_owner rights in order to provide comprehensive access. Additionally, according to the announcement, the target Azure SQL DB user has to hold four distinct server-level roles, such as ##MS_DatabaseManager## and ##MS_LoginManager##, which grant the user the ability to add and remove databases and logins.
The feature cannot function without the aforementioned permissions. Instead of employing the dbmanager database-level role, it suggests using the ##MS_DatabaseManager## server role. Users can create databases, manage logins, and browse all catalog views once these capabilities are granted.
High-level rights can probably be withdrawn after migration; however, Microsoft doesn't specify how long you'll need to grant them. This can lessen the likelihood of security incidents brought on by giving broad permissions. See the instructions in Microsoft's announcement for further information on how to use this feature.