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. Migrate '{0}' to Azure SQL Are you sure you want to cancel this migration? 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 can be migrated to SQL Server on Azure Virtual Machines. Assessment results Assessment results and recommendations This is a blocking issue that will prevent the database migration from succeeding. Authentication key Authentication key '{0}' has been refreshed. Authentication type Authentication keys Azure SQL Azure SQL Database 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 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. 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. 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 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 cannot be retried. The cutover process cannot start until all the migrations are done. To return the latest file status, refresh your browser window. Close Complete cutover 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. Connection status Copy key 1 Copy key 2 Copy migration details 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 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. 2. Create a final transaction log backup and store it on the network share. 3. Verify that all backups have been restored on the target database. The "Log backups pending restore" value should be zero. 3. Verify that all log 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 or SQL Server on Azure Virtual Machines. Help articles and video links Migrate to Azure SQL Migrate a SQL Server instance to Azure SQL. Azure SQL Migration 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}'. Select the databases that you want to assess for migration to Azure SQL. Databases for assessment An error occurred while accessing database details. Ensure that your backups were taken with the WITH CHECKSUM option. 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. Database migration status Select the location of the database backups to use during migration. Database backup Ensure that the Azure Storage account does not use a private endpoint. Status Database to be migrated Databases ({0}/{1}) {0}/{1} databases selected Databases {0} day {0} days Description Details copied 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 Database migrations failed Feedback on the migration experience File name Finish time First LSN Full backup files 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 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. Invalid network share location format. Example: {0} 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 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 as an Azure SQL target 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 Issues Issues ({0}) Issue details Key 1 copied Key 1 Key 2 copied Key 2 Last LSN Last applied backup files Last applied backup files taken on Last applied LSN Last backup Last scan completed: {0} Learn more Learn more about things you need before starting a migration. Location 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 Migration status Migration status filter {0} min {0} mins Mode More info N/A Name Names: Name of new resource group My database backups are in an Azure Storage Blob Container My database backups are on a network share Network share Storage account details Provide the Azure Storage account where the backups will be uploaded to. Network share details Provide the network share location where the backups are stored, and the user credentials used to access the share. Network share path for your database backups. The migration process will automatically retrieve valid backup files from this network share. Network share location where the backups are stored Password Enter password. Network share path \\Servername.domainname.com\Backupfolder Enter target database name and network share path information for the selected source databases. Windows user account with read access to the network share location. Windows user account with read access to the network share location (new) {0} New support request No No blob containers found. No blob files found. No file shares found. No issues found for migrating to SQL Server on 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. Assessment results are unavailable. No storage accounts found. No subscriptions found. No virtual machines found. Failed to open the migration notebook. Object details Offline OFFLINE OK Online Download and install integration runtime User account Azure account details Azure SQL Managed Instance or SQL Server on Azure Virtual Machine Backup location details Things you need before starting a 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: '{0}'. Please check your linked Azure connection and click refresh to try again. A resource group is a container that holds related resources for an Azure solution. No resource groups found. Resource group Resume previously saved session Run migration workflow again Retry migration An error occurred while retrying the migration. Resource group created Save and close Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Cancel Next Saved session Search Search for migrations {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 databases to assess for migration Select the databases to migrate. 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. 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. 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 Close Azure Database Migration Service Self-hosted integration runtime node -- unavailable -- Azure Database Migration Service "{0}" details:` 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} 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) Size {0} recommendations available Azure configuration Business critical {0} - {1} vCore Gen5 General purpose {0} - {1} - {2} vCore {0} - {1} - {2} vCore - {3} GB Premium-series Memory optimized premium-series {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 Generating Azure recommendations using provided performance data... Select a folder on your local drive where previously collected performance data was saved Start Starting performance data collection... 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 database in Azure for your workload. Data collection still in progress. Refining existing recommendations... Data collection for Azure recommendations has been stopped. Stopping performance data collection... 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 Azure SQL Database {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 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 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. Recommendation reason Recommendations - Last refreshed: {0} Loading... {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 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 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 and identify valid backup files. Source server Source version SQL migration assessment SQL Database SQL Managed Instance SQL Server instance SQL Virtual Machine Start migration Start a new session Start time Status Add account Add your Azure account to view existing migrations and their status. Canceling Completing Creating Status: All Status: Completing Status: Failed Status: Ongoing Status: Succeeded {0} Errors) {0} {0} Error) {0} ( Failed In progress Refresh Select a Database Migration Service to monitor migrations. Succeeded {0} Warnings) {0} Warning) Storage account Subscription Azure storage Azure storage subscription Databases for migration Azure SQL Managed Instance Summary SQL Server on Azure Virtual Machine Target Target name Target database name Target platform Target server Target version Test connection Type Type: (Unavailable) {0} Select a unique name for this target database Username All database migrations View/Select 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 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 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, or selecting a different set of databases to assess. Select an Azure account and your target {0}. Azure SQL target Yes {0} of {1} databases selected 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) 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 Virtual Machines (online) An error occurred while starting the migration: '{0}' Starting migration for database {0} to {1} - {2} Cancel migration Complete cutover Copy migration details Database details Azure SQL migration description Azure SQL Migration Azure SQL Migration Migration Context Menu Migration Tasks Azure SQL Migration Open Azure SQL migration notebooks New support request Refresh Retry migration Feedback Migrate to Azure SQL Database Migration Service details Azure SQL Target details