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 SQLAre you sure you want to cancel this migration?Select the databases that you want to migrate to Azure SQL.Active backup filesActive backup files (1 item)Active backup files ({0} items)All backups restoredAll fields are required.ApplyThe assessment of your SQL Server instance '{0}' failed.Assessment results for '{0}'Assessment in progressWe 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 resultsThis is a blocking issue that will prevent the database migration from succeeding.Authentication keyAuthentication key '{0}' has been refreshed.Authentication typeAuthentication keysAzure SQLAzure SQL Managed InstanceSQL Server on Azure Virtual MachinesTarget typeAzure Storage account to upload backupsAzure AD tenantBackup locationBackup start timeA 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 groupLast backup fileSelect a blob container value first.Blob container storage accountBlob containerSelect a resource group.Select a resource group value first.Azure Storage Blob Container detailsProvide the Azure Storage Blob Container that contains the backups.SubscriptionEnter target database name and select resource group, storage account and container for the selected source databases.Select a storage account value first.{0} out of {1} databases can be migratedCancelAn error occurred while canceling the migration.Cancel migrationMigration 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.CloseComplete cutoverCompleting 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 statusCopy key 1Copy key 2Copy migration detailsCopy 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} databaseCreateCreate newCreating resource groupCurrently restoring fileMigration cutoverCompleting cutoverAn 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 modeDetermine 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 linksMigrate to Azure SQLMigrate a SQL Server instance to Azure SQL.Azure SQL MigrationComparison of the actual amount of data read from the source and the actual amount of data uploaded to the target.Data uploaded / sizeDatabaseDatabase '{0}' already exists on the target managed instance '{1}'.An error occurred while accessing database details.Databases for migrationTo migrate to the Azure SQL target, choose a migration mode based on your downtime requirements.Migration modeApplication downtime will start when the migration starts.Offline migrationApplication downtime is limited to cutover at the end of migration.Online migrationDatabase Migration ServiceDatabase Migration Service authentication keysSuccessfully created a Database Migration Service.Database migration statusSelect the location of the database backups to use during migration.Database backupDatabase to be migratedDatabases ({0}/{1}){0}/{1} Databases selectedDatabases{0} day{0} daysDescriptionDetails copiedAny existing Azure Database Migration Service in the Azure portal do not appear in Azure Data Studio. Any Database Migration Service created in Azure Data Studio will not be visible in the Azure portal yet.Failed to provision a Database Migration Service. Wait a few minutes and then try again.DurationIf results were expected, verify the connection to the SQL Server instance.No backup filesEnter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL.ErrorMigrations failedFeedback on the migration experienceFile nameFinish timeFirst LSNFull backup filesWe have completed the assessment of your SQL Server instance '{0}'.{0} hr{0} hrsImpactName: {0}Type: {0}Impacted objectsInline migration{0} databases have warnings{0} database has warningsInstanceTo 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.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.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}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 ServiceStep 1: {0}Step 2: Use this key to register your integration runtimeStep 3: Click on 'Test connection' button to check the connection between Azure Database Migration Service and integration runtimeIssuesIssues ({0})Issue detailsKey 1 copiedKey 1Key 2 copiedKey 2Last LSNLast applied backup filesLast applied backup files taken onLast applied LSNLast backupLast scan completed: {0}Learn moreLearn more about things you need before starting a migration.LocationAzure SQL Managed InstanceMigrations completedDatabase migrations in progressMigrations not startedMigration statusMigration status filter{0} min{0} minsModeMore infoNameNames:Name of new resource groupMy database backups are in an Azure Storage Blob ContainerMy database backups are on a network shareNetwork shareStorage account detailsProvide the Azure Storage account where the backups will be uploaded to.Network share detailsProvide 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 storedPasswordEnter password.Network share path\\Servername.domainname.com\BackupfolderEnter 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 requestNoNo 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 location found.No managed instance found.No pending backups. Click refresh to check current status.Assessment results are unavailable.No storage account found.No subscription found.No virtual machine found.Failed to open the migration notebook.Object detailsOfflineOFFLINEOKOnlineDownload and install integration runtimeUser accountAzure account detailsAzure SQL Managed Instance or SQL Server on Azure Virtual MachineBackup location detailsThings you need before starting a migration:Provide a unique container for each target database. Databases affected: Select the operation you'd like to perform.RecommendationRefreshRefresh assessmentRefresh key 1Refresh key 2A resource group is a container that holds related resources for an Azure solution.No resource groups found.Resource groupContinue last migration attempt...Start with migration assessment again (recommended)Run migration workflow againRetry migrationAn error occurred while retrying the migration.Resource group createdSave and closeCancelNextSaved assessment resultSearchSearch for migrations{0} secSelect 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 migrationSelect the databases to migrate.Click on SQL Server instance or any of the databases on the left to view its details.To continue, select a target database.ServerEnsure 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 runtimeLoading Migration ServicesAuthentication keysAuthentication keys used to connect to the self-hosted integration runtime nodeCloseAzure Database Migration ServiceSelf-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.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 ServiceAzure 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 nodeShow statusSize (MB)SizeAzure region for your Azure SQL targetAzure SQL Managed Instance (PaaS)To migrate to Azure SQL Managed Instance (PaaS), view assessment results and select one or more databases.To migrate to SQL Server on Azure Virtual Machine (IaaS), view assessment results and select one or more databases.Your Azure SQL target resource nameResource group for your Azure SQL targetSubscription name for your Azure SQL targetSQL Server on Azure Virtual Machine (IaaS)Source configurationSource credentialsSource database nameSource databasesEnter 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 serverSource versionSQL migration assessmentSQL Managed InstanceSQL Server instanceSQL Virtual MachineStart migrationStart timeStatusAdd accountAdd your Azure account to view existing migrations and their status.CancelingCompletingCreatingStatus: AllStatus: CompletingStatus: FailedStatus: OngoingStatus: Succeeded{0} Errors){0}{0} Error){0} (FailedIn progressRefreshSucceeded{0} Warnings){0} Warning)Storage accountSubscriptionAzure storageAzure storage subscriptionDatabases for migrationAzure SQL Managed InstanceSummarySQL Server on Azure Virtual MachineTargetTarget nameTarget database nameTarget platformTarget serverTarget versionTest connectionTypeType:Select a unique name for this target databaseUsernameView allView/SelectWarningWarningsWarnings ({0})Warnings detailsDomain\usernameLink account{0} accounts linked{0} account linkedSelect an Azure account linked to Azure Data Studio, or link one now.Add a linked account and then try again.Azure accountBased 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 targetAn error occurred while assessing your databases.Azure SQL targetYes{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 GuidesTutorial: Migrate to Azure SQL Managed Instance (online)Migrate databases using Azure Data StudioTutorial: 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 migrationComplete cutoverCopy migration detailsDatabase detailsAzure SQL migration descriptionAzure SQL MigrationAzure SQL MigrationMigration Context MenuMigration TasksAzure SQL MigrationOpen Azure SQL migration notebooksNew support requestRetry migrationFeedbackMigrate to Azure SQLDatabase Migration Service detailsAzure SQL Target details