An error occurred while accessing the selected account '{0}' and tenant '{1}'. Select 'Link account' and refresh the account, or select a different account. Error '{2}'

The access token for selected account '{0}' and tenant '{1}' is no longer valid. Select 'Link account' and refresh the account, or select a different account.

Migration service component could not start. {0}

Service component crashed.

Service provider could not be initialized.

Migrate '{0}' to Azure SQL

Are you sure you want to cancel this migration?

Are you sure you want to delete this migration?

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;

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

{0} (requires credentials refresh)

Active backup files

Active backup files (1 item)

Active backup files ({0} items)

All backups restored

All fields are required.

Apply

(for {0} assessed databases)

Assessment results for '{0}'

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

Assessment in progress

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

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.

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.

Assessment results

Assessment results and recommendations

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

Authentication key '{0}' has been refreshed.

Authentication type

Authentication keys

Azure SQL

Azure SQL Database Server

Azure SQL Managed Instance

SQL Server on Azure Virtual Machines

SQL Server on Azure VM

Target type

Azure Storage account to upload backups

Azure AD tenant

Browse

Folder name

Open

Backup size (MB)

File name

Number of stripes

Restore finish date

Restore start date

Restore status

File status

Backup location

Backup start time

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.

Folder

Blob container resource group

Last backup file

Select a blob container value first.

Blob container storage account

Blob container

Select a resource group.

Select a resource group value first.

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.

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

Azure Storage Blob Container details

Provide the Azure Storage Blob Container that contains the backups.

Subscription

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

Select a storage account value first.

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

Cancel

An error occurred while canceling the migration.

Cancel migration

Migration is not in progress and cannot be canceled.

Migration is not in progress and cannot be cutover.

Migration is currently in progress and cannot be deleted.

Migration cannot be retried.

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

Complete cutover

We ran the following steps:

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

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

Connect

Connection status

Copy key 1

Copy key 2

Copy migration details

Canceled

Cancelled

Copy finished

Copying

Failed

In progress

Preparing

Queued

Rebuilding indexes

Succeeded

Copy throughput (MBPS)

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.

{0} databases

{0} database

Create

Create new

Create new migration service

Create new resource group

Creating resource group

Currently restoring file

Migration cutover

Database migrations completing cutover

An error occurred while initiating cutover.

Perform the following steps before you complete cutover.

Cutover in progress for database '{0}'

Last file restored: {0}

Log backups pending restore: {0}

An error occurred while refreshing the migration status.

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.

Migration mode

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.

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

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.

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.

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) to SQL Server on Azure Virtual Machines with minimal downtime.

Azure Database Migration Guides

Tutorial: Migrate to Azure SQL Managed Instance (online)

Migrate databases using Azure Data Studio

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

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

Help articles and video links

Migrate to Azure SQL

Migrate a SQL Server instance to Azure SQL.

Azure SQL Migration

Data source configuration

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

Data uploaded / size

Database

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

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

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

Databases for assessment

An error occurred while accessing database details.

An error occurred while connecting to target migration database.

Connection error:{0} {1}

Loading database table list..

Loading tables list...

The duration of the migration

The fininish time for the migration

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.

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

Migration mode

Application downtime will start when the migration starts.

Offline migration

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

Online migration

Database Migration Service

Database Migration Service authentication keys

Successfully created a Database Migration Service.

The start time for the migration

Database migration status

Database migration status: {0}

The target database name

The target server name

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

0 tables found on source database.

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

SQL Server dacpac extension

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.

SQL Database Projects extension

Migration status

The current status of the migration

Refresh

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'.

Table selection

Source database

Select tables

Target database

Database to be migrated

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

Databases ({0}/{1})

{0}/{1} databases selected

Databases

{0} day

{0} days

Default database

An error occurred while deleting the migration.

Delete migration

Description

Details copied

Refresh

Total tables

Cancelled

Failed

Server objects

Filter table migration results using keywords

Filter table migration results

In progress

Server objects

Successful

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

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

Your Azure Database Migration Service resource name

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

Subscription name for your Azure Database Migration Service

Duration

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

No backup files

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

Error

Click to view error details

Migration error(s))

Migration error details

Clear

Migration status details

Database migrations failed

Feedback on the migration experience

Detected files

Last restored file time

Last uploaded file time

Last uploaded file

Managed instance restore state

Pending differential backups

Queued files

Restore percent completed

Restore plan size (MB)

Restored files

Restored size (MB)

Restoring files

Skipped files

Unrestorable files

File name

Finish time

First LSN

Full backup file(s)

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

{0} hr

{0} hrs

Impact

Name: {0}

Type: {0}

Impacted objects

Inline migration

{0} databases have warnings

{0} database has warnings

Instance

To continue, select a valid Azure account.

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 backup folder for source database '{0}'.

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

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

To continue, select a valid location.

To continue, select a valid managed instance.

Select a valid Database Migration Service.

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

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

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

To continue, select a valid resource group.

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

Enter a valid name for the Migration Service.

To continue, select a valid Azure SQL Database server.

To continue, select a valid storage account.

To continue, select a valid subscription.

Enter a valid name for the target database.

Invalid user account format. Example: {0}

To continue, select a valid virtual machine.

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.

No Database Migration Service found. Create a new one.

Azure Database Migration Service

Step 1: {0}

Step 2: Use this key to register your integration runtime

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

Blocking Issue: {0}

Issues

Issues ({0})

Issue details

Key 1 copied

Key 1

Key 2 copied

Key 2

Last LSN

Last applied backup file(s)

Last applied backup taken on

Last applied LSN

Last scan completed: {0}

Learn more

Learn more about things you need before starting a migration.

Error loading migrations list

Location

Source database

Target database

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.

Map selected source databases to target databases for migration

Select a target database

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

Database migrations completed

Database migrations in progress

Ascending

Sort

Migration status

Migration status filter

{0} min

{0} mins

Table name

To continue, enter a valid target password.

To continue, enter a valid target user name.

Mode

More info

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

All steps succeeded.

Some steps are still running.

Step status: {0}

Copy results

Step details

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

Steps

N/A

Name

Names:

Name of new resource group

My database backups are in an Azure Storage Blob Container

(new) {0}

New support request

No blob containers found.

No blob files found.

No blob folders found.

No file shares found.

No issues found for migrating to Azure SQL Managed Instance.

No issues found for migrating to Azure SQL Database.

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.

Assessment results are unavailable.

No Azure SQL databases found.

No Azure SQL database servers found.

No storage accounts found.

No subscriptions found.

No virtual machines found.

Failed to open the migration notebook.

{0}/{1} migrating logins displayed

Object details

Offline

OFFLINE

Online

Error opening migration details dialog

Error opening migration service dialog

Error opening migration target

Download and install integration runtime

Dynamic range

None

Physical partitions

Target password

Enter the target password

User account

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

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).

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

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

Things you need before starting your Azure SQL migration:

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

Select the operation you'd like to perform.

Recommendation

Refresh

Refresh assessment

Refresh key 1

Refresh key 2

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

An error has occured while refreshing the migrations list.

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

No resource groups found.

Resource group

Restart migration wizard

None

Queued

Restored

Restoring

Skipped

Database

Differential database

Differential file

Differential partial

File

Partial

Transaction log

Unknown

Restoring

Blocked

Cancelled

Completed

Completing migration

Failed

Initializing

None

Not started

Restore completed

Restore paused

Searching backups

Waiting

Resume previously saved session

Run migration workflow again

Retry migration

An error occurred while retrying the migration.

Resource group created

Run validation

We are running the following steps:

Save assessment report

Successfully saved assessment report to {0}.

Save and close

Save recommendation report

Successfully saved recommendation report to {0}.

Cancel

Saved session

Filter migration results

{0} sec

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

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

Please select 1 or more logins for migration

Select the databases to migrate.

Select tables for migration

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

Apply

Clear

Azure Database Migration Service

Filter the migration list by Database Migration Service

Select a Database Migration Service

Sign into Azure and select an account

Select a location

Select a resource group

Select a Database Migration Service

Select a subscription

Select a tenant

An error occurred while loading available Azure accounts.

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

Select a target server.

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

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

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

Select target Azure SQL Type

An error occurred while loading available Azure account tenants.

Azure Database Migration Service

Select Database Migration Service

To continue, select a target.

Server

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

Azure Database Migration Service leverages Azure Data Factory's self-hosted integration runtime to upload backups from on-premises network file share to Azure.

Follow the instructions below to setup self-hosted integration runtime.

Setup integration runtime

Loading Migration Services

Authentication keys

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

Azure Database Migration Service

Self-hosted integration runtime node

-- unavailable --

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

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

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

{0} (change)

Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the node - {1}

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

An error occurred while refreshing the migration service creation status.

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

Create Azure Database Migration Service

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

Azure Database Migration Service name.

Resource group for your Azure Database Migration Service.

Subscription name for your Azure Database Migration Service.

Azure SQL target selected as default.

Self-hosted integration runtime node

Show status

Size (MB)

{0} GB

{0} MB

{0} TB

{0} recommendations available

{0} recommendation available

Azure configuration

Business critical

Gen5

General purpose

Hyperscale

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

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

Premium-series

Memory optimized premium-series

{0} - {1} vCore

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

{0} x {1}

{0} ({1} vCPU)

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

Choose how you want to provide performance data

Collect performance data now

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

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.

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

I already have the performance data

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

Start

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

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

Data collection in progress. Generating initial recommendations...

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

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

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

Data collection for Azure recommendations has been stopped.

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

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

Azure recommendation will be displayed once data collection is complete.

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

{0} cores

CPU requirement

Data IOPS requirement

Data storage requirement

{0} GB

Get Azure recommendation

IO latency requirement

{0} IOPS

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

Log storage requirement

Logs IOPS requirement

Memory requirement

Azure SQL Managed Instance

{0} ms

Recommendation parameters

Edit parameters

Edit recommendation parameters

Enable elastic recommendation

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

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.

Percentage utilization

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

Scale factor

Invalid scale factor. Enter a positive integer value.

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

Enter the information below to edit the recommendation parameters.

Update

{0}%

{0}th percentile

Azure recommendation (PREVIEW)

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

To migrate to Azure SQL Database, 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.

Recommendation reason

Recommendations

Last refreshed: {0}

{0} Recommendations

Value

Recommended configuration

Refine Azure recommendation

Refresh recommendation

Your Azure SQL target resource name

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

Restart data collection

Source properties

SQL data files

SQL log files

SQL tempdb

Azure SQL Database

Stop data collection

Dimension

{0} GB

Subscription name for your Azure SQL target

Target deployment type

Recommendation target storage configuration

Host caching

Not applicable

None

Read-only

Read/write

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

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

Local SSD

Recommended storage configuration

Storage

View details

SQL Server on Azure Virtual Machine

Source configuration

Source credentials

Source database name

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 from the self-hosted integration runtime.

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 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 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.

Source server

Source version

SQL migration assessment

SQL Database

SQL Managed Instance

SQL Server instance

SQL Virtual Machine

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}

Known issues, limitations, and troubleshooting

Copy duration

Copy start

Copy throughput

Data read

Data written

Parallel copy type

Rows copied

Rows read

Table name

Used parallel copies

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.

Source database

Name of the source database

Source name

Name of the source server

Start migration

Start a new session

Start time

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

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

Canceled

Failed

Pending

Running

Succeeded

Status

Add account

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

Canceled

Canceling

Completing

Creating

({0} errors)

({0} error)

Failed

In progress

Ready for cutover

Refresh

Restoring

Retriable

Select a Database Migration Service to monitor migrations.

Status

Succeeded

Uploading full backup

Uploading log backup(s)

{0}

({0} warnings)

({0} warning)

Storage account

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.

Subscription

Azure storage

Azure storage subscription

Databases for migration

Azure SQL Managed Instance

Summary

Azure SQL Database

SQL Server on Azure Virtual Machine

Feedback

Migrate to Azure SQL

New migration

New support request

Dashboard

Migrations

Table migration status details

Table migration status: {0}

Tables missing on target: {0}

Select tables for {0}

{0} of {1} tables selected

{0} of {1}

Edit

Filter tables

Has rows

Table name

Update

Cancel

Target

Target database

Target name

Target database name

Target platform

Target server

Tables selected

Target table does not exist

Target table is not empty.

Target version

Edit

Migrate certificates

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

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

Databases

Status

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

Copy migration results

Done

Migrating the certificates from the following databases:

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:

Previous certificates migration results:

Retry migration

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

{0}{1}{2}

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

Migration canceled

Migration completed successfully.

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

No encrypted database selected.

You have chosen to manually migrate certificates.

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

{0} of {1} completed

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

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}.

Export my certificates and private key to the target.

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

I don't want Azure Data Studio to export the certificates.

You must migrate the certificates before proceeding with the migration otherwise the migration will fail. {0}.

Certificate migration

Encrypted database selected.

Test connection

Type

Type:

(Unavailable) {0}

Select a unique name for this target database

User name

Target user name

Enter the target user name

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

Status

Validation steps

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

Copy validation results

Done

We are validating the following:

Validation step details

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

Start validation

Validation status: {0}

{0}{1}{2}

{0} - {1} errors

{0} - 1 error

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

Stop validation

Validation check canceled

Validation completed successfully.

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}

Network share connectivity: '{0}'

Integration runtime connectivity

Source database connectivity: '{0}'

Azure storage connectivity

Target database connectivity: '{0}'

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

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

Running validation

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

Canceled

Failed

Pending

Running

Succeeded

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

All database migrations

View/Select

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.

Warning

Warnings

Warnings ({0})

Warnings details

Domain\username

Link account

{0} accounts linked

{0} account linked

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

Add a linked account and then try again.

Azure account

An error occurred while connecting to the target server.

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

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

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

Check this option to skip assessment and continue the migration.

[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.]

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

Choose your Azure SQL target

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

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

No recommendation available

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.

Connection was successful but did not find any target databases.

Connection error: {0}

Connection was successful. Target databases found: {0}

Select an Azure account and your target {0}.

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 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 (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. Source database '{0}' is not mapped to a target database. Please select a target database to migrate to.

Azure SQL target

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

Yes

Do you want to retry the failed table migrations?

Please resolve any errors before retrying the migration.

The migration failed with the following errors:

{0} of {1} databases selected

{0} of {1}

Waiting for {0} component to start.

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

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

Downloading {0}

Done downloading {0}

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}).

({0} KB)

Downloading {0}

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

Failed to start {0}: {1}

Installing {0} Service

Installing {0} to {1}

Installed {0}

{0} Started

Starting {0}

Azure SQL migration description

Azure SQL Migration

Migration Tasks

Azure SQL Migration

Open Azure SQL migration notebooks

New support request

Refresh

Feedback

Migrate to Azure SQL