Azure SQL MigrationAzure SQL migration descriptionOpen Azure SQL migration notebooksAzure SQL MigrationMigration TasksAzure SQL MigrationMigrate to Azure SQLFeedbackNew support requestMigration Context MenuComplete cutoverDatabase detailsAzure SQL Target detailsDatabase Migration Service detailsCopy migration detailsCancel migrationMigrate '{0}' to Azure SQLThis is a blocking issue that will prevent the database migration from succeeding.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.Azure SQL TargetBased on the assessment results, all {0} of your database(s) in an online state can be migrated to Azure SQL.An error occurred while assessing the server '{0}'.Choose your Azure SQL targetAzure SQL Managed Instance (PaaS)SQL Server on Azure Virtual Machine (IaaS)Select your target Azure subscription and your target Azure SQL Managed InstanceSelect your target Azure Subscription and your target SQL Server on Azure Virtual Machine for your target.To migrate to Azure SQL Managed Instance (PaaS), view assessment results and select one or more database(s).To migrate to SQL Server on Azure Virtual Machine (IaaS), view assessment results and select one or more database(s).View/Select{0} of {1} Database(s) selected.To continue, select a target database.Select the databases to migrate.We have completed the assessment of your SQL Server Instance '{0}'.Assessment results for '{0}'{0} out of {1} databases can be migratedDatabases that are not ready for migration to Azure SQL Managed Instance can be migrated to SQL Server on Azure Virtual Machines.DatabasesSQL Server InstanceAzure AccountSelect an Azure account linked to Azure Data Studio, or link one now.Add a linked account and then try again.Link account{0} account linked{0} accounts linkedAzure AD tenantThe access token for selected account '{0}' is no longer valid. Select 'Link Account' and refresh the account, or select a different account.An error occurred while accessing the selected account '{0}'. Select 'Link Account' and refresh the account, or select a different account. Error '{1}'Database BackupSelect the location of your database backups to use for migration.My database backups are on a network shareMy database backups are in an Azure Storage Blob ContainerNetwork share detailsProvide the network share location that contains backups and the user credentials that has read access to the shareNetwork share location that contains backups.Ensure that the service account running the source SQL Server instance has read privileges on the network share.Windows user account with read access to the network share location.PasswordEnter passwordStorage account detailsProvide the Azure storage account where backups will be uploaded to.Select a unique name for this target databaseDatabase '{0}' already exists on the target managed instance '{1}'.Select the subscription that contains the storage account.Migration modeTo migrate to the Azure SQL target, choose a migration mode based on your downtime requirements.Online migrationApplication downtime is limited to cutover at the end of migration.Application downtime will start when the migration starts.Offline migrationNo subscription foundNo location foundNo storage account foundNo file shares foundNo blob containers foundNo blob files foundTo continue, select a valid subscription.To continue, select a valid location.To continue, select a valid storage account.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 blob container for source database '{0}'.To continue, select a valid last backup file for source database '{0}'.Invalid network share location format. Example: {0}Invalid user account format. Example: {0}Enter a valid name for the target database.Provide a unique container for each target database. Databases affected: 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 file(s).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 file(s).Select a resource group value first.Select a storage account value first.Select a blob container value first.Azure Database Migration ServiceAzure 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 oneCreate newSelect a valid Database Migration Service.Select a Database Migration Service that is connected to a node.Authentication keysAzure Database Migration Service "{0}" details:`Any 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.Database Migration Service authentication keysCreate Azure Database Migration ServiceEnter 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 identifying valid backup file(s).Loading Migration ServicesSetup integration runtimeAzure Database Migration Service leverages Azure Data Factory's self-hosted integration runtime to upload backups from on-premises network fie share to Azure.Follow the instructions below to setup self-hosted integration runtime.Step 1: {0}Download and install integration runtimeStep 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 runtimeConnection StatusKey 1Key 2Key 1 copiedKey 2 copiedRefresh key 1Refresh key 2Copy key 1Copy key 2Authentication keyAuthentication key '{0}' has been refreshed.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}No resource groups found To continue, select a valid resource group.Enter a valid name for the Migration Service.No Migration Services found. To continue, create a new one.An error occurred while refreshing the migration service creation status.Azure SQL Managed InstanceNo managed instance foundNo virtual machine foundA resource group is a container that holds related resources for an Azure solution.OK(new) {0}Test connectionSuccessfully created a Database Migration Service.Failed to provision a Database Migration Service. Wait a few minutes and then try again.ApplyCreating resource groupResource group createdName of new resource groupLearn moreLearn more about things you need before starting a migration.SubscriptionStorage accountResource groupNameLocationRefreshCreateCancelTypeUser AccountView AllTargetAzure SQLCloseData Uploaded/SizeCopy Throughput (MBPS)New support requestSummaryAzure SQL Managed InstanceSQL Server on Azure Virtual MachineDatabase(s) for migrationAzure storage subscriptionAzure storageNetwork ShareBlob ContainerLast Backup FileBlob container resource groupBlob container storage accountSource Database(s)ModeBackup LocationAzure Storage Account to Upload BackupsSelf-hosted integration runtime nodeDatabase to be migrated{0} database{0} databasesSelect the operation you'd like to performInline migrationSQL migration assessmentFailed to open the migration notebookAzure SQL MigrationDetermine 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.Migrate to Azure SQLMigrate SQL Server instance to Azure SQL.Database Migration StatusAssessment rules for Azure SQL Managed InstanceSee the list of rules used to determine whether your SQL Server instance can be migrated to Azure SQL Managed Instance.Help Articles and Video LinksThings you need before starting migration:Azure account detailsAzure SQL Managed Instance or SQL Server on Azure Virtual MachineBackup location detailsDatabase migration in progressMigration failedMigration completedCompleting cutoverMigration not startedShow status{0} database has warnings{0} databases have warningsFeedback on the migration experienceMigration cutoverComplete cutoverSource database nameSource serverSource versionTarget database nameTarget serverTarget versionMigration StatusMigration status filterFull backup filesLast applied LSNLast applied backup filesLast applied backup files taken onActive Backup filesAn error occurred while refreshing the migration status.An error occurred while canceling the migration.StatusBackup start timeFirst LSNLast LSNThe cutover process cannot start until all the migrations are done. To return the latest file status, refresh your browser window.Azure SQL Managed InstanceSQL Server on Azure Virtual MachinesCancel migrationActive Backup files (1 item)Active Backup files ({0} items)Copy Migration DetailsDetails copiedAre you sure you want to cancel this migration?YesNoCompleting cutover without restoring all the backup(s) may result in a data loss.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.Perform the following steps before you complete cutover.1. Stop all incoming transactions to the source database.2. Take a final backup of the transaction log and store it in the network share location.2. Take a final differential or backup of the transaction log and store it in the Azure Storage Blob Container.3. Verify that your backup(s) have been restored on the target database. The "Log backup(s) pending restore" value should be zero.3. Verify that your backup(s) have been restored on the target database. The "Log backup(s) pending restore" value should be zero.Last file restored: {0}Last scan completed: {0}Log backups pending restore: {0}I confirm there are no additional log backup(s) to provide and want to complete cutover.Cutover in progress for database '{0}'Migration is not in progress and cannot be canceled.Migration is not in progress and cannot be cutover.File nameSizeNo pending backups. Click refresh to check current status.Search for migrationsOnlineOfflineDatabaseDatabase Migration ServiceDurationAzure SQL TargetSQL Managed InstanceSQL Virtual MachineAzure SQL Target NameMigration modeStart TimeFinish Time{0} ({0}In progressSucceededCreatingCompletingCancelingFailed{0} Warning){0} Warnings){0} Error){0} Errors){0} hrs{0} hr{0} days{0} day{0} mins{0} min{0} secAzure Database Migration ServiceCloseSelf-hosted integration runtime nodeAuthentication keysAuthentication keys used to connect to the self-hosted integration runtime node-- unavailable --Source ConfigurationSource CredentialsEnter the credentials for the source SQL Server instance. These credentials will be used while migrating database(s) to Azure SQL.ServerUsernameSize (MB)Last backupDatabases for migrationSelect database(s) that you want to migrate to Azure SQLOFFLINEIssuesSearchInstanceWarningsImpacted ObjectsObject detailsAssessment ResultsType:Names:DescriptionRecommendationMore InfoTarget PlatformWarnings DetailsIssue DetailsClick on SQL Server Instance or any of the databases on the left to view its details.No issues found for migrating to SQL Server on Azure Virtual MachineNo issues found for migrating to SQL Server on Azure SQL Managed InstanceType: {0}Name: {0}Databases ({0}/{1}){0}/{1} Databases SelectedIssues ({0})Warnings ({0})Authentication TypeRefreshStarting migration for database {0} to {1} - {2}An error occurred while starting the migration: '{0}'