({0} error)

({0} errors)

({0} warning)

({0} warnings)

(Unavailable) {0}

(for {0} assessed databases)

(new) {0}

-- unavailable --

0 tables found on source database.

1. Stop all incoming transactions to the source database.

2. Create a final transaction log differential or backup and store it in the Azure Storage Blob Container.

3. Verify that all backups have been restored on the target database. The "Log backups pending restore" value should be zero.

A SQL Managed Instance migration cutover to the Business Critical service tier can take significantly longer than General Purpose because three secondary replicas have to be seeded for Always On High Availability group. The duration of the operation depends on the size of the data. Seeding speed in 90% of cases is 220 GB/hour or higher.

A hub of migration articles that provides step-by-step guidance for migrating and modernizing your data assets in Azure.

A resource group is a container that holds related resources for an Azure solution.

A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public).

A step-by-step tutorial to migrate databases from a SQL Server instance (on-premises or Azure Virtual Machines) to Azure SQL Database.

A step-by-step tutorial to migrate databases from a SQL Server instance (on-premises or Azure Virtual Machines) to Azure SQL Managed Instance with minimal downtime.

A step-by-step tutorial to migrate databases from a SQL Server instance (on-premises) to SQL Server on Azure Virtual Machines with minimal downtime.

A time-out was encountered while validating a resource connection. Learn more: https://aka.ms/dms-migrations-troubleshooting.

Active backup files

Active backup files (1 item)

Active backup files ({0} items)

Add a linked account and then try again.

Add account

Add your Azure account to view existing migrations and their status.

All backups restored

All database migrations

All fields are required.

All steps completed with the following error(s):{0}{1}

All steps succeeded.

An Azure SQL Managed Instance, SQL Server on Azure Virtual Machine, or Azure SQL Database to migrate your database(s) to.

An Azure account (not required for assessment or SKU recommendation functionality)

An error has occured while refreshing the migrations list.

An error occurred while accessing database details.

An error occurred while assessing the server '{0}'.

An error occurred while canceling the migration.

An error occurred while connecting to target migration database.

An error occurred while connecting to the target server.

An error occurred while deleting the migration.

An error occurred while generating SKU recommendations for the server '{0}'.

An error occurred while initiating cutover.

An error occurred while loading account subscriptions. Please check your Azure connection and try again.

An error occurred while loading available Azure account tenants.

An error occurred while loading available Azure accounts.

An error occurred while loading available database migration services. Please check your Azure connection and try again.

An error occurred while loading available resource groups. Please check your Azure connection and try again.

An error occurred while loading locations. Please check your Azure connection and try again.

An error occurred while refreshing the migration service creation status.

An error occurred while refreshing the migration status.

An error occurred while refreshing the migrations list. Please check your linked Azure connection and click refresh to try again.

An error occurred while restarting the migration.

An error occurred while starting the certificate migration: '{0}'

An unexpected error occurred while assessing the server '{0}'.{3}Message: {1}{3}stack: {2}

Application downtime is limited to cutover at the end of migration.

Application downtime will start when the migration starts.

Apply

Are you sure you want to cancel this migration?

Are you sure you want to delete this migration?

Ascending

Assess extended event sessions

Assessment in progress

Assessment results

Assessment results and recommendations

Assessment results are unavailable.

Assessment results for '{0}'

Authentication key '{0}' has been refreshed.

Authentication keys

Authentication keys used to connect to the self-hosted integration runtime node

Authentication type

Azure AD tenant

Azure Database Migration Guides

Azure Database Migration Service

Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on node(s) - {1} For improved performance and high availability, you can register additional nodes.

Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on node(s) - {1} For improved performance and high availability, you can register additional nodes. See below for registration instructions.

Azure Database Migration Service is not registered. Azure Database Migration Service '{0}' needs to be registered with self-hosted integration runtime on any node.

Azure Database Migration Service is not registered. Azure Database Migration Service '{0}' needs to be registered with self-hosted integration runtime on any node. See below for registration instructions.

Azure Database Migration Service leverages Azure Data Factory's self-hosted integration runtime to handle connectivity between source and target and upload backups from an on-premises network file share to Azure (if applicable).

Azure Database Migration Service name.

Azure Database Migration Service orchestrates database migration activities and tracks their progress. You can select an existing Database Migration Service if you have created one previously, or create a new one below.

Azure SQL

Azure SQL Database

Azure SQL Database Server

Azure SQL Managed Instance

Azure SQL Migration

Azure SQL target

Azure SQL target selected as default.

Azure Storage Blob Container details

Azure Storage account to upload backups

Azure account

Azure configuration

Azure recommendation (PREVIEW)

Azure recommendation collects and analyzes performance data and then recommends an appropriate sized target in Azure for your workload.

Azure recommendation has been applied using the provided data. Import or collect additional data to refine the recommendation.

Azure recommendation is not available. Click “Get Azure recommendation” button below

Azure recommendation requires performance data of SQL server instance to provide target recommendation. Enable performance data collection to receive the target recommendation for the databases you want to migrate. The longer this will be enabled the better the recommendation. You can disable performance data collection at any time.

Azure recommendation will be displayed once data collection is complete.

Azure region for your Azure Database Migration Service. Only regions that contain a service will be shown.

Azure region for your Azure Database Migration Service. This should be the same region as your target Azure SQL.

Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown.

Azure storage

Azure storage connectivity

Azure storage subscription

Backup location

Backup size (MB)

Backup start time

Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL.

Below is the target storage configuration required to meet your storage performance needs.

Blob container

Blob container resource group

Blob container storage account

Blocked

Blocking Issue: {0}

Browse

Business critical

CPU requirement

Cancel

Cancel migration

Canceled

Canceling

Cancelled

Cannot connect to the database due to invalid OwnerUri (Parameter 'OwnerUri')

Cannot retrieve saved session. Try again by selecting new session.

Certificate migration

Certificates Migration

Certificates migration completed successfully. Please click Next to proceed with the migration.

Certificates migration has not been run for the current configuration. Please run and complete the certificates migration to continue.

Certificates migration progress details:

Certificates migration results:

Certificates migration was canceled. Please run and complete the certificates migration to continue.

Certificates must be migrated before proceeding with the database migration otherwise a failure will occur. {0} about manually migrating TDE certificates.

Change scale factor if you want the Azure recommendation to be a percentage larger or smaller than you current workload.

Check back periodically for updated recommendations by pressing the 'Refresh recommendation' button.

Check this option to skip assessment and continue the migration.

Choose how you want to provide performance data

Choose your Azure SQL target

Clear

Click on SQL Server instance or any of the databases on the left to view its details.

Click the button below to import or collect database performance data.

Click to view error details

Collect performance data now

Comparison of the actual amount of data read from the source and the actual amount of data uploaded to the target.

Complete cutover

Completed

Completing

Completing cutover without restoring all the backups may result in a data loss.

Completing migration

Connect

Connection error: {0}

Connection error:{0} {1}

Connection status

Connection was successful but did not find any target databases.

Connection was successful. Target databases found: {0}

Copy duration

Copy finished

Copy key 1

Copy key 2

Copy migration details

Copy migration results

Copy results

Copy start

Copy throughput

Copy throughput (MBPS)

Copy validation results

Copying

Create

Create Azure Database Migration Service

Create new

Create new migration service

Create new resource group

Creating

Creating resource group

Currently restoring file

Cutover in progress for database '{0}'

Dashboard

Data IOPS requirement

Data collection for Azure recommendations has been stopped.

Data collection in progress. Generating initial recommendations...

Data collection still in progress. Refining existing recommendations...

Data movement throughput achieved during the migration of your database backups to Azure. This is the rate of data transfer, calculated by data read divided by duration of backups migration to Azure.

Data read

Data source configuration

Data storage requirement

Data uploaded / size

Data written

Data: {0}, Log: {1}, tempdb: {2}

Database

Database '{0}' already exists on the target managed instance '{1}'.

Database Migration Service

Database Migration Service authentication keys

Database mapping error (Error code: {0}) was found between '{1}' and '{2}' databases. The source database collation '{3}' does not match the target database collation '{4}'. Please select or re-create a target database with the same collation as the source database.

Database mapping error. Missing target databases to migrate. Please configure the target server connection and click connect to collect the list of available database migration targets.

Database mapping error. Source database '{0}' is not mapped to a target database. Please select a target database to migrate to.

Database mapping error. Target database '{0}' cannot be selected to as a migration target for database '{1}'. Target database '{2}' is already selected as a migration target for database '{3}'. Please select a different target database.

Database migration status

Database migrations completed

Database migrations completing cutover

Database migrations failed

Database migrations in progress

Database to be migrated

Databases

Databases ({0}/{1})

Databases for assessment

Databases for migration

Databases that are not ready for migration to Azure SQL Database can be migrated to SQL Server on Azure Virtual Machines. Alternatively, review assessment results for Azure SQL Managed Instance migration readiness.

Databases that are not ready for migration to Azure SQL Managed Instance can be migrated to SQL Server on Azure Virtual Machines. Alternatively, review assessment results for Azure SQL Database migration readiness.

Databases that are not ready for migration to Azure SQL Managed Instance or Azure SQL Database can be migrated to SQL Server on Azure Virtual Machines.

Default database

Delete migration

Description

Details copied

Detected files

Determine the migration readiness of your SQL Server instances, identify a recommended Azure SQL target, and complete the migration of your SQL Server instance to Azure SQL Managed Instance, SQL Server on Azure Virtual Machines or Azure SQL Database.

Differential database

Differential file

Differential partial

Dimension

Do you want to retry the failed table migrations?

Domain\username

Done

Download and install integration runtime

Duration

Dynamic range

Edit

Edit parameters

Edit recommendation parameters

Elastic recommendation uses an alternate recommendation model which utilizes personalized price-performance profiling against existing on-cloud customers.

Enable elastic recommendation

Enable preview features

Enabling this option will include the latest hardware generations that have significantly improved performance and scalability. These SKUs are currently in Preview and may not yet be available in all regions.

Encrypted database selected.

Ensure that the provided database name(s) do not already exist on the target SQL Server on Azure Virtual Machine.

Ensure that the service account running the source SQL Server instance has read privileges on the network share.

Enter a valid name for the Migration Service.

Enter a valid name for the target database.

Enter target database name and select resource group, storage account and container for the selected source databases.

Enter the SQL Authentication credentials used to connect to SQL Server instance {0}. These credentials will be used to connect to the SQL Server instance and identify valid backup files.

Enter the SQL Authentication credentials used to connect to SQL Server instance {0}. These credentials will be used to connect to the SQL Server instance from the self-hosted integration runtime.

Enter the Windows Authentication credentials used to connect to SQL Server instance {0}. These credentials will be used to connect to the SQL Server instance and identify valid backup files.

Enter the Windows Authentication credentials used to connect to SQL Server instance {0}. These credentials will be used to connect to the SQL Server instance from the self-hosted integration runtime.

Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL.

Enter the information below to add a new Azure Database Migration Service.

Enter the information below to add a new Azure Database Migration Service. To register self-hosted integration runtime, select 'My database backups are on a network share' on the previous page.

Enter the information below to edit the recommendation parameters.

Enter the target password

Enter the target user name

Error

Error loading migrations list

Error migrating certificate for database {0}. {1}

Error opening migration details dialog

Error opening migration service dialog

Error opening migration target

Error(s) occurred while collecting performance data for the server '{0}'. If these issues persist, try restarting the data collection process: {1}

Export my certificates and private keys to the target.

Failed

Failed to open the migration notebook.

Failed to provision a Database Migration Service. Wait a few minutes and then try again.

Feedback

Feedback on the migration experience

File

File name

File status

Filter migration results

Filter table migration results

Filter table migration results using keywords

Filter tables

Filter the migration list by Database Migration Service

Finish time

First LSN

Folder

Folder name

Follow the instructions below to set up self-hosted integration runtime.

For each database below, click Edit to select the tables to migrate from source to target. Then, before clicking Next, validate the provided configuration by clicking 'Run validation'.

For target servers running SQL Server 2014 or below, you must store your database backups in an Azure Storage Blob Container instead of uploading them using the network share option. Additionally, you must store the backup files as page blobs, as block blobs are supported only for targets running SQL Server 2016 or later. Learn more: {0}

For the selected databases, optionally provide extended event session files to assess ad-hoc or dynamic SQL queries or any DML statements initiated through the application data layer. {0}

Full backup file(s)

Gen5

General purpose

Get Azure recommendation

Has rows

Help articles and video links

Host caching

Hyperscale

I already have the performance data

I confirm there are no additional log backups to provide and want to complete cutover.

I give consent to use my credentials for accessing the certificates.

I have already migrated my certificates and private keys to the target.

IO latency requirement

If results were expected, verify the connection to the SQL Server instance.

Impact

Impacted objects

In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration.

In progress

Initial recommendations will automatically refresh in approximately {0} minute(s).

Initializing

Inline migration

Instance

Integration runtime connectivity

Invalid scale factor. Enter a positive integer value.

Invalid user account format. Example: {0}

Issue details

Issues

Issues ({0})

Key 1

Key 1 copied

Key 2

Key 2 copied

Known issues, limitations, and troubleshooting

Last LSN

Last applied LSN

Last applied backup file(s)

Last applied backup taken on

Last backup file

Last file restored: {0}

Last refreshed: {0}

Last restored file time

Last scan completed: {0}

Last uploaded file

Last uploaded file time

Learn more

Learn more about things you need before starting a migration.

Learn more: https://aka.ms/dms-migrations-troubleshooting.

Link account

Loading Migration Services

Loading database table list..

Loading tables list...

Local SSD

Location

Log backups pending restore: {0}

Log storage requirement

Logs IOPS requirement

Make sure to migrate the database schema from source to target by using the {0} or the {1} in Azure Data Studio before selecting the list of tables to migrate.

Managed instance restore state

Map selected source databases to target databases for migration

Memory optimized premium-series

Memory requirement

Migrate '{0}' to Azure SQL

Migrate a SQL Server instance to Azure SQL.

Migrate certificates

Migrate databases using Azure Data Studio

Migrate to Azure SQL

Migrating the certificates from the following databases:

Migration canceled

Migration cannot be restarted.

Migration completed successfully.

Migration completed with the following error(s):{0}{1}

Migration cutover

Migration error details

Migration error(s))

Migration is currently in progress and cannot be deleted.

Migration is not in progress and cannot be canceled.

Migration is not in progress and cannot be cutover.

Migration mode

Migration service component could not start. {0}

Migration status

Migration status details

Migration status filter

Migration status: {0}{1}{2}

Migrations

Mode

More info

My database backups are in an Azure Storage Blob Container

N/A

Name

Name of new resource group

Name of the source database

Name of the source server

Name: {0}

Names:

Network share connectivity: '{0}'

New migration

New support request

No Azure SQL database servers found.

No Azure SQL databases found.

No Database Migration Service found. Create a new one.

No Migration Services found. To continue, create a new one.

No SKU recommendations were generated, as there were no SKUs which could satisfy the performance characteristics of your source. Try selecting a different target platform, adjusting recommendation parameters, selecting a different set of databases to assess, or changing the recommendation model.

No backup files

No blob containers found.

No blob files found.

No blob folders found.

No encrypted database selected.

No file shares found.

No issues found for migrating to Azure SQL Database.

No issues found for migrating to Azure SQL Managed Instance.

No issues found for migrating to SQL Server on Azure Virtual Machine.

No locations found.

No managed instances found.

No pending backups. Click refresh to check current status.

No recommendation available

No resource groups found.

No storage accounts found.

No subscriptions found.

No virtual machines found.

None

Not applicable

Not started

Not sure which Azure SQL target is right for you? Learn more

Number of stripes

OFFLINE

Object details

Offline

Offline migration

Online

Online migration

Open

Parallel copy type

Partial

Pending

Pending differential backups

Percentage utilization

Percentile of data points to be used during aggregation of the performance data.

Perform the following steps before you complete cutover.

Physical partitions

Place tempdb on the local ephemeral SSD (default D:\) drive

Please enter a network path where SQL Server will export the certificates. Also verify that SQL Server service has write access to this path and the current user should have administrator privileges on the computer where this network path is.

Please resolve any errors before retrying the migration.

Please select 1 or more databases to assess for migration

Please select target database tables to migrate to. At least one database with one table is required.

Please select the location of your database backup files before continuing.

Premium-series

Preparing

Previous certificates migration results:

Provide a unique container for each target database. Databases affected:

Provide the Azure Storage Blob Container that contains the backups.

Queued

Queued files

Read-only

Read/write

Ready for cutover

Rebuilding indexes

Recommendation

Recommendation parameters

Recommendation reason

Recommendation target storage configuration

Recommendations

Recommended configuration

Recommended storage configuration

Refine Azure recommendation

Refresh

Refresh assessment

Refresh key 1

Refresh key 2

Refresh recommendation

Resource group

Resource group created

Resource group for your Azure Database Migration Service.

Resource group for your Azure SQL target. Only resource groups that contain a service will be shown.

Resource group for your Azure SQL target. Only resource groups that contain a target eligible for migration will be shown.

Restart data collection

Restart migration wizard

Restore completed

Restore finish date

Restore paused

Restore percent completed

Restore plan size (MB)

Restore start date

Restore status

Restored

Restored files

Restored size (MB)

Restoring

Restoring files

Resume previously saved session

Retriable

Retry migration

Revalidate unsuccessful steps

Rows copied

Rows read

Run migration workflow again

Run validation

Running

Running the performance collection for a longer period of time helps ensure a more accurate recommendation.

SELECT sp.name as login, sp.type_desc as login_type, sp.default_database_name, case when sp.is_disabled = 1 then 'Disabled' else 'Enabled' end as status FROM sys.server_principals sp LEFT JOIN sys.sql_logins sl ON sp.principal_id = sl.principal_id WHERE sp.type NOT IN ('G', 'R') AND sp.type_desc IN ('SQL_LOGIN', 'WINDOWS_LOGIN') ORDER BY sp.name;

SQL Database

SQL Database Projects extension

SQL Managed Instance

SQL Server dacpac extension

SQL Server instance

SQL Server on Azure VM

SQL Server on Azure Virtual Machine

SQL Server on Azure Virtual Machines

SQL Virtual Machine

SQL data files

SQL log files

SQL migration assessment

SQL tempdb

Save and close

Save assessment report

Save recommendation report

Saved session

Scale factor

Searching backups

Select

Select Database Migration Service

Select a Database Migration Service

Select a Database Migration Service that is connected to a node.

Select a Database Migration Service to monitor migrations.

Select a blob container value first.

Select a folder on your local drive where performance data will be saved

Select a folder on your local drive where previously collected performance data was saved

Select a folder where extended events session files (.xel and .xem) are stored

Select a location

Select a resource group

Select a resource group value first.

Select a resource group.

Select a storage account value first.

Select a subscription

Select a target database

Select a target server.

Select a tenant

Select a unique name for this target database

Select a valid Database Migration Service.

Select an Azure account and your target {0}.

Select an Azure account linked to Azure Data Studio, or link one now.

Select tables

Select tables for migration

Select tables for {0}

Select target Azure SQL Type

Select the databases that you want to assess for migration to Azure SQL.

Select the databases that you want to migrate to Azure SQL.

Select the databases to migrate.

Select the location of the database backups to use during migration.

Select the operation you'd like to perform.

Select the target database where you would like to migrate your source database to. You can choose a target database for only one source database.

Select your target Azure Subscription and your target SQL Server on Azure Virtual Machine for your target.

Select your target Azure subscription and your target Azure SQL Managed Instance.

Self-hosted integration runtime node

Server

Server objects

Service component crashed.

Service provider could not be initialized.

Set up integration runtime

Show status

Sign into Azure and select an account

Size (MB)

Skipped

Skipped files

Some steps are still running.

Sort

Source configuration

Source credentials

Source database

Source database connectivity: '{0}'

Source database name

Source databases

Source name

Source properties

Source server

Source version

Start

Start a new session

Start migration

Start time

Start validation

Status

Step 1: {0}

Step 2: Use the keys below to register your integration runtime

Step 3: Click on the 'Test connection' button to check the connection between Azure Database Migration Service and integration runtime

Step 3: Click on the Refresh button above to check the connection between Azure Database Migration Service and integration runtime

Step details

Step status: {0}

Step status: {0}{1}{2}

Steps

Stop data collection

Stop validation

Storage

Storage account

Subscription

Subscription name for your Azure Database Migration Service

Subscription name for your Azure Database Migration Service.

Subscription name for your Azure SQL target

Succeeded

Successful

Successfully created a Database Migration Service.

Successfully saved assessment report to {0}.

Successfully saved recommendation report to {0}.

Summary

TDE certificate migration must be successful before continuing.

Table migration status details

Table migration status: {0}

Table name

Table selection

Tables missing on target: {0}

Tables selected

Target

Target database

Target database connectivity: '{0}'

Target database name

Target deployment type

Target instance '{0}' may not be able to access storage account '{1}'. Ensure that the subnet of the target instance is whitelisted on the storage account, and if applicable, that the private endpoint is in the same virtual network as the target server.

Target instance '{0}' may not be able to access storage accounts '{1}'. Ensure that the subnet of the target instance is whitelisted on the storage accounts, and if applicable, that the private endpoints are on the same virtual network as the target server.

Target name

Target password

Target platform

Target server

Target server '{0}' may not be able to access storage account '{1}'. Ensure that the subnet of the target server is whitelisted on the storage account.

Target server '{0}' may not be able to access storage accounts '{1}'. Ensure that the subnet of the target server is whitelisted on the storage accounts.

Target table does not exist

Target table is not empty.

Target type

Target user name

Target version

Test connection

The Azure SQL Migration extension for Azure Data Studio provides capabilities to assess, get right-sized Azure recommendations and migrate SQL Server databases to Azure.

The SQL database server '{0}' is unavailable for migration because it is currently in the '{1}' state. To continue, select an available SQL database server.

The assessment of your SQL Server instance '{0}' failed.

The azure resource target type [SQL Managed Instance, SQL Virtual Machine, SQL Database]

The current status of the migration

The cutover process cannot start until all the migrations are done. To return the latest file status, refresh your browser window.

The duration of the migration

The fininish time for the migration

The following error occurred while retrieving registration information for Azure Database Migration Service '{0}'. Please click refresh and try again. Error: '{1}'.

The managed instance '{0}' is unavailable for migration because it is currently in the '{1}' state. To continue, select an available managed instance.

The migration failed with the following errors:

The start time for the migration

The target database name

The target server name

The virtual machine '{0}' is unavailable for migration because the SQL Server IaaS Agent extension is currently in '{1}' mode instead of Full mode. Learn more: https://aka.ms/sql-iaas-extension

The virtual machine '{0}' is unavailable for migration because the underlying virtual machine is not running. Please make sure it is powered on before retrying.

There are multiple databases with the same backup location selected. Ensure that backup files from different databases are stored in separate folders.

Things you need before starting your Azure SQL migration:

This is a blocking issue that will prevent the database migration from succeeding.

To continue, enter a valid target password.

To continue, enter a valid target user name.

To continue, select a blob container where all the backup files are page blobs for source database '{0}', as block blobs are supported only for targets running SQL Server 2016 or later. Learn more: https://aka.ms/dms-migrations-troubleshooting

To continue, select a target.

To continue, select a valid Azure SQL Database server.

To continue, select a valid Azure account.

To continue, select a valid backup folder for source database '{0}'.

To continue, select a valid blob container for source database '{0}'.

To continue, select a valid last backup file for source database '{0}'.

To continue, select a valid location.

To continue, select a valid managed instance.

To continue, select a valid resource group for source database '{0}'.

To continue, select a valid resource group.

To continue, select a valid storage account for source database '{0}'.

To continue, select a valid storage account.

To continue, select a valid subscription.

To continue, select a valid virtual machine.

To migrate an encrypted database successfully you need to provide access to the encryption certificates or migrate certificates manually before proceeding with the migration. {0}.

To migrate to Azure SQL Database, view assessment results and select one or more databases.

To migrate to Azure SQL Managed Instance, view assessment results and select one or more databases.

To migrate to SQL Server on Azure Virtual Machine, view assessment results and select one or more databases.

To migrate to the Azure SQL target, choose a migration mode based on your downtime requirements.

Total tables

Transaction log

Tutorial: Migrate to Azure SQL Managed Instance (online)

Tutorial: Migrate to SQL Server on Azure SQL Database (offline)

Tutorial: Migrate to SQL Server on Azure Virtual Machines (online)

Type

Type:

Type: {0}

Unknown

Unrestorable files

Update

Uploading full backup

Uploading log backup(s)

Used parallel copies

User account

User name

Validation check canceled

Validation check error{0}Database:{1}{0}Error: {2} - {3}

Validation check error{0}Source database: {1}{0}File share path: {2}{0}Error: {3} - {4}

Validation check error{0}Source database: {1}{0}Target database: {2}{0}Error: {3} - {4}

Validation completed successfully.

Validation completed successfully. Please click Next to proceed with the migration.

Validation completed with the following error(s):{0}{1}

Validation has not been run for the current configuration. Please run and validate the migration settings to continue.

Validation status: {0}

Validation status: {0}{1}{2}

Validation step details

Validation steps

Validation was canceled with the following error(s):{0}{1}

Validation was canceled. Please run and validate the migration settings to continue.

Value

View details

View/Select

Waiting

Waiting for {0} component to start.

Warning

Warnings

Warnings ({0})

Warnings details

We are assessing the databases in your SQL Server instance {0} to identify the right Azure SQL target. This may take some time.

We are running the following steps:

We are validating the following:

We have completed the assessment of your SQL Server instance '{0}'.

We ran the following steps:

We recommend migrating your databases(s) to the Azure SQL target before starting the login migration to avoid failures in the process. Nevertheless, you can run this migration process whenever want you want if your goal is to update the user mapping for recently migrated databases. If the source and database names are not the same, then it is possible that some permissions may not be applied properly.

When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported.

Yes

You can also choose to select this data from an existing folder, if you have already collected it previously.

You have given Azure Data Studio access to migrate the encryption certificates and database.

You have not given Azure Data Studio access to migrate the encryption certificates.

You must click the '{0}' button before proceeding to the next page of the wizard.

Your Azure Database Migration Service resource name

Your Azure SQL target resource name

Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets).

[There are no assessment results to validate readiness of your database migration. By checking this box, you acknowledge you want to proceed migrating your database to the desired Azure SQL target.]

{0}

{0} (change)

{0} (requires credentials refresh)

{0} ({1} vCPU)

{0} - 1 error

{0} - {1} - {2} vCore

{0} - {1} - {2} vCore - {3} GB

{0} - {1} errors

{0} - {1} vCore

{0} GB

{0} IOPS

{0} MB

{0} Recommendations

{0} TB

{0} Transparent Data Encryption enabled databases selected for migration. {1}

{0} account linked

{0} accounts linked

{0} cores

{0} database

{0} database has warnings

{0} databases

{0} databases have warnings

{0} day

{0} days

{0} hr

{0} hrs

{0} min

{0} mins

{0} ms

{0} of {1}

{0} of {1} completed

{0} of {1} databases selected

{0} of {1} tables selected

{0} out of {1} selected database(s) is using transparent data encryption.

{0} recommendation available

{0} recommendations available

{0} sec

{0} x {1}

{0}%

{0}/{1} databases can be migrated without issues

{0}/{1} databases selected

{0}/{1} migrating logins displayed

{0}th percentile

{0}{1}{2}

An error occurred while starting the migration: '{0}'

Starting migration for database {0} to {1} - {2}

({0} KB)

Done downloading {0}

Downloading {0}

Extracted {0} ({1}/{2})

Failed to download binaries for {0}. Use the following link to troubleshoot: {1}

Failed to download binaries for {0}. Use this [link to troubleshoot]({1}).

Failed to start {0}: {1}

Installed {0}

Installing {0} Service

Installing {0} to {1}

Starting {0}

{0} Started

Azure SQL Migration

Azure SQL migration description

Feedback

Migrate to Azure SQL

Migration Tasks

New support request

Open Azure SQL migration notebooks

Refresh