diff --git a/resources/xlf/en/sql-migration.xlf b/resources/xlf/en/sql-migration.xlf index 46393aca889b..a36e280e42e2 100644 --- a/resources/xlf/en/sql-migration.xlf +++ b/resources/xlf/en/sql-migration.xlf @@ -66,16 +66,16 @@ This may take some time. - Azure SQL Target + Azure SQL target - Based on the assessment results, all {0} of your database(s) in an online state can be migrated to Azure SQL. + 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}'. - Refresh Assessment + Refresh assessment Choose your Azure SQL target @@ -93,16 +93,16 @@ This may take some time. Select 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 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 database(s). + To migrate to SQL Server on Azure Virtual Machine (IaaS), view assessment results and select one or more databases. View/Select - {0} of {1} Database(s) selected. + {0} of {1} databases selected. To continue, select a target database. @@ -111,7 +111,7 @@ This may take some time. Select the databases to migrate. - We have completed the assessment of your SQL Server Instance '{0}'. + We have completed the assessment of your SQL Server instance '{0}'. Assessment results for '{0}' @@ -126,10 +126,10 @@ This may take some time. Databases - SQL Server Instance + SQL Server instance - Azure Account + Azure account Select an Azure account linked to Azure Data Studio, or link one now. @@ -150,16 +150,16 @@ This may take some time. Azure AD tenant - The access token for selected account '{0}' is no longer valid. Select 'Link Account' and refresh the account, or select a different account. + The 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}' + An error occurred while accessing the selected account '{0}'. Select 'Link account' and refresh the account, or select a different account. Error '{1}' - Database Backup + Database backup - Select the location of your database backups to use for migration. + Select the location of the database backups to use during migration. My database backups are on a network share @@ -171,31 +171,31 @@ This may take some time. Network share details - Provide the network share location that contains backups and the user credentials that has read access to the share + Provide the network share location where the backups are stored, and the user credentials used to access the share. - Enter target database name for the selected source database(s). + Enter target database name for the selected source databases. - Network share location that contains backups. + Network share location where the backups are stored 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. + Windows user account with read access to the network share location Password - Enter password + Enter password. Storage account details - Provide the Azure storage account where backups will be uploaded to. + Provide the Azure Storage account where the backups will be uploaded to. Select a unique name for this target database @@ -210,7 +210,7 @@ This may take some time. Provide the Azure Storage Blob Container that contains the backups. - Enter target database name and select resource group, storage account and container for the selected source database(s). + Enter target database name and select resource group, storage account and container for the selected source databases. Select the subscription that contains the storage account. @@ -227,12 +227,12 @@ This may take some time. Application downtime is limited to cutover at the end of migration. - - Application downtime will start when the migration starts. - Offline migration + + Application downtime will start when the migration starts. + \\Servername.domainname.com\Backupfolder @@ -240,22 +240,22 @@ This may take some time. Domain\username - No subscription found + No subscription found. - No location found + No location found. - No storage account found + No storage account found. - No file shares found + No file shares found. - No blob containers found + No blob containers found. - No blob files found + No blob files found. To continue, select a valid subscription. @@ -291,10 +291,10 @@ This may take some time. 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 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 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). + 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. Select a resource group value first. @@ -312,7 +312,7 @@ This may take some time. 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 + No Database Migration Service found. Create a new one. Create new @@ -366,7 +366,7 @@ This may take some time. Step 3: Click on 'Test connection' button to check the connection between Azure Database Migration Service and integration runtime - Connection Status + Connection status Key 1 @@ -405,7 +405,7 @@ This may take some time. Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the node - {1} - No resource groups found + No resource groups found. To continue, select a valid resource group. @@ -423,10 +423,10 @@ This may take some time. Azure SQL Managed Instance - No managed instance found + No managed instance found. - No virtual machine found + No virtual machine found. A resource group is a container that holds related resources for an Azure solution. @@ -492,10 +492,10 @@ This may take some time. Type - User Account + User account - View All + View all Target @@ -507,10 +507,10 @@ This may take some time. Close - Data Uploaded/Size + Data uploaded / size - Copy Throughput (MBPS) + Copy throughput (MBPS) New support request @@ -531,7 +531,7 @@ This may take some time. SQL Server on Azure Virtual Machine - Database(s) for migration + Databases for migration Azure storage subscription @@ -540,13 +540,13 @@ This may take some time. Azure storage - Network Share + Network share - Blob Container + Blob container - Last Backup File + Last backup file Blob container resource group @@ -555,16 +555,16 @@ This may take some time. Blob container storage account - Source Database(s) + Source databases Mode - Backup Location + Backup location - Azure Storage Account to Upload Backups + Azure Storage account to upload backups Self-hosted integration runtime node @@ -579,7 +579,7 @@ This may take some time. {0} databases - Select the operation you'd like to perform + Select the operation you'd like to perform. Inline migration @@ -588,7 +588,7 @@ This may take some time. SQL migration assessment - Failed to open the migration notebook + Failed to open the migration notebook. Azure SQL Migration @@ -600,22 +600,22 @@ This may take some time. Migrate to Azure SQL - Migrate SQL Server instance to Azure SQL. + Migrate a SQL Server instance to Azure SQL. - Database Migration Status + Database migration status Assessment rules for Azure SQL Managed Instance - See the list of rules used to determine whether your SQL Server instance can be migrated to Azure SQL Managed Instance. + Assessment rules used to determine the feasibility of migrating your SQL Server instance to Azure SQL Managed Instance. - Help Articles and Video Links + Help articles and video links - Things you need before starting migration: + Things you need before starting a migration: Azure account details @@ -627,19 +627,19 @@ This may take some time. Backup location details - Database migration in progress + Database migrations in progress - Migration failed + Migrations failed - Migration completed + Migrations completed Completing cutover - Migration not started + Migrations not started Show status @@ -678,7 +678,7 @@ This may take some time. Target version - Migration Status + Migration status Migration status filter @@ -696,7 +696,7 @@ This may take some time. Last applied backup files taken on - Active Backup files + Active backup files An error occurred while refreshing the migration status. @@ -729,13 +729,13 @@ This may take some time. Cancel migration - Active Backup files (1 item) + Active backup files (1 item) - Active Backup files ({0} items) + Active backup files ({0} items) - Copy Migration Details + Copy migration details Details copied @@ -750,13 +750,13 @@ This may take some time. No - No backup files to show + No backup files - If results were expected, reconfirm the connection to the SQL Server Instance. + If results were expected, verify the connection to the SQL Server instance. - Completing cutover without restoring all the backup(s) may result in a data loss. + Completing cutover without restoring all the backups 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. @@ -768,16 +768,16 @@ This may take some time. 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. ​​Create a final transaction log backup and store it on the network share. - 2. Take a final differential or backup of the transaction log and store it in the Azure Storage Blob Container. + 2. Create a final transaction log differential or backup 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 all log backups have been restored on the target database. The "Log backups 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. + 3. Verify that all backups have been restored on the target database. The "Log backups pending restore" value should be zero. Last file restored: {0} @@ -789,7 +789,7 @@ This may take some time. Log backups pending restore: {0} - I confirm there are no additional log backup(s) to provide and want to complete cutover. + I confirm there are no additional log backups to provide and want to complete cutover. Cutover in progress for database '{0}' @@ -843,7 +843,7 @@ This may take some time. Duration - Azure SQL Target + Target type SQL Managed Instance @@ -852,16 +852,16 @@ This may take some time. SQL Virtual Machine - Azure SQL Target Name + Target name Migration mode - Start Time + Start time - Finish Time + Finish time {0} ( @@ -939,13 +939,13 @@ This may take some time. -- unavailable -- - Source Configuration + Source configuration - Source Credentials + Source credentials - Enter the credentials for the source SQL Server instance. These credentials will be used while migrating database(s) to Azure SQL. + Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Server @@ -963,7 +963,7 @@ This may take some time. Databases for migration - Select database(s) that you want to migrate to Azure SQL + Select the databases that you want to migrate to Azure SQL. OFFLINE @@ -984,13 +984,13 @@ This may take some time. Warnings - Impacted Objects + Impacted objects Object details - Assessment Results + Assessment results Type: @@ -1005,25 +1005,25 @@ This may take some time. Recommendation - More Info + More info - Target Platform + Target platform - Warnings Details + Warnings details - Issue Details + Issue details - Click on SQL Server Instance or any of the databases on the left to view its details. + Click 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 Machine + No issues found for migrating to SQL Server on Azure Virtual Machine. - No issues found for migrating to SQL Server on Azure SQL Managed Instance + No issues found for migrating to SQL Server on Azure SQL Managed Instance. Type: {0} @@ -1035,7 +1035,7 @@ This may take some time. Databases ({0}/{1}) - {0}/{1} Databases Selected + {0}/{1} Databases selected Issues ({0}) @@ -1044,7 +1044,7 @@ This may take some time. Warnings ({0}) - Authentication Type + Authentication type Refresh diff --git a/resources/xlf/en/sql.xlf b/resources/xlf/en/sql.xlf index e1e769fe67ad..4df847194f9f 100644 --- a/resources/xlf/en/sql.xlf +++ b/resources/xlf/en/sql.xlf @@ -3573,7 +3573,7 @@ Error: {1} Results grid - Max row count for filtering/sorting has been exceeded. To update it, you can go to User Settings and change the setting: 'queryEditor.results.inMemoryDataProcessingThreshold' + Max row count for filtering/sorting has been exceeded. To update it, navigate to User Settings and change the setting: 'queryEditor.results.inMemoryDataProcessingThreshold'