ckaczor/azuredatastudio
1
0
Fork 0
mirror of https://github.com/ckaczor/azuredatastudio.git synced 2026-01-14 01:25:37 -05:00
Code Issues Packages Projects Releases Wiki Activity

[Loc] final update to localization before code complete (#22956)

Browse Source
This commit is contained in:
Alex Ma
2023-05-03 17:16:12 -07:00
committed by GitHub
parent 13a791d14e
commit e76e6df49c
1 changed files with 24 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
resources/xlf/en/sql-migration.xlf
View File

@@ -995,10 +995,13 @@ This may take some time.</source>
<source xml:lang="en">Step 1: {0}</source>
</trans-unit>
<trans-unit id="sql.migration.ir.setup.step2">
<source xml:lang="en">Step 2: Use this key to register your integration runtime</source>
<source xml:lang="en">Step 2: Use the keys below to register your integration runtime</source>
</trans-unit>
<trans-unit id="sql.migration.ir.setup.step3">
<source xml:lang="en">Step 3: Click on 'Test connection' button to check the connection between Azure Database Migration Service and integration runtime</source>
<source xml:lang="en">Step 3: Click on the 'Test connection' button to check the connection between Azure Database Migration Service and integration runtime</source>
</trans-unit>
<trans-unit id="sql.migration.ir.setup.step3.alternate">
<source xml:lang="en">Step 3: Click on the Refresh button above to check the connection between Azure Database Migration Service and integration runtime</source>
</trans-unit>
<trans-unit id="sql.migration.issue.aria.label">
<source xml:lang="en">Blocking Issue: {0}</source>
@@ -1586,13 +1589,13 @@ This may take some time.</source>
<source xml:lang="en">Ensure that the service account running the source SQL Server instance has read privileges on the network share.</source>
</trans-unit>
<trans-unit id="sql.migration.service.container.container.description1">
<source xml:lang="en">Azure Database Migration Service leverages Azure Data Factory's self-hosted integration runtime to upload backups from on-premises network file share to Azure.</source>
<source xml:lang="en">Azure Database Migration Service leverages Azure Data Factory's self-hosted integration runtime to handle connectivity between source and target and upload backups from an on-premises network file share to Azure (if applicable).</source>
</trans-unit>
<trans-unit id="sql.migration.service.container.container.description2">
<source xml:lang="en">Follow the instructions below to setup self-hosted integration runtime.</source>
<source xml:lang="en">Follow the instructions below to set up self-hosted integration runtime.</source>
</trans-unit>
<trans-unit id="sql.migration.service.container.heading">
<source xml:lang="en">Setup integration runtime</source>
<source xml:lang="en">Set up integration runtime</source>
</trans-unit>
<trans-unit id="sql.migration.service.container.loading.help">
<source xml:lang="en">Loading Migration Services</source>
@@ -1627,11 +1630,23 @@ This may take some time.</source>
<trans-unit id="sql.migration.service.not.ready">
<source xml:lang="en">Azure Database Migration Service is not registered. Azure Database Migration Service '{0}' needs to be registered with self-hosted integration runtime on any node.</source>
</trans-unit>
<trans-unit id="sql.migration.service.not.ready.below">
<source xml:lang="en">Azure Database Migration Service is not registered. Azure Database Migration Service '{0}' needs to be registered with self-hosted integration runtime on any node.
See below for registration instructions.</source>
</trans-unit>
<trans-unit id="sql.migration.service.prompt">
<source xml:lang="en">{0} (change)</source>
</trans-unit>
<trans-unit id="sql.migration.service.ready">
<source xml:lang="en">Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the node - {1}</source>
<source xml:lang="en">Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on node(s) - {1}
For improved performance and high availability, you can register additional nodes.</source>
</trans-unit>
<trans-unit id="sql.migration.service.ready.below">
<source xml:lang="en">Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on node(s) - {1}
For improved performance and high availability, you can register additional nodes. See below for registration instructions.</source>
</trans-unit>
<trans-unit id="sql.migration.service.selection.location.msg">
<source xml:lang="en">Please select the location of your database backup files before continuing.</source>
@@ -1642,6 +1657,9 @@ This may take some time.</source>
<trans-unit id="sql.migration.services.container.description">
<source xml:lang="en">Enter the information below to add a new Azure Database Migration Service.</source>
</trans-unit>
<trans-unit id="sql.migration.services.container.description.network">
<source xml:lang="en">Enter the information below to add a new Azure Database Migration Service. To register self-hosted integration runtime, select 'My database backups are on a network share' on the previous page.</source>
</trans-unit>
<trans-unit id="sql.migration.services.dialog.title">
<source xml:lang="en">Create Azure Database Migration Service</source>
</trans-unit>