ckaczor/azuredatastudio
1
0
Fork 0
mirror of https://github.com/ckaczor/azuredatastudio.git synced 2026-02-16 10:58:30 -05:00
Code Issues Packages Projects Releases Wiki Activity

[Loc] update to source files prior to split (#23031)

Browse Source
This commit is contained in:
Alex Ma
2023-05-08 10:50:18 -07:00
committed by GitHub
parent 9c22620032
commit 4c10133ae9
22 changed files with 260 additions and 260 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
resources/xlf/es/sql-migration.es.xlf
View File

@@ -1332,15 +1332,15 @@ Esta operación puede tardar varios minutos.</target>
</trans-unit>
<trans-unit id="sql.migration.ir.setup.step2">
<source xml:lang="en">Step 2: Use the keys below to register your integration runtime</source>
<target state="new">Step 2: Use the keys below to register your integration runtime</target>
<target state="translated">Paso 2: Use las claves siguientes para registrar el entorno de ejecución de integración</target>
</trans-unit>
<trans-unit id="sql.migration.ir.setup.step3">
<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>
<target state="new">Step 3: Click on the 'Test connection' button to check the connection between Azure Database Migration Service and integration runtime</target>
<target state="translated">Paso 3: Haga clic en el botón "Prueba de conexión" para comprobar la conexión entre Azure Database Migration Service y el entorno de ejecución de integración</target>
</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>
<target state="new">Step 3: Click on the Refresh button above to check the connection between Azure Database Migration Service and integration runtime</target>
<target state="translated">Paso 3: Haga clic en el botón "Actualizar" para comprobar la conexión entre Azure Database Migration Service y el entorno de ejecución de integración</target>
</trans-unit>
<trans-unit id="sql.migration.issue.aria.label">
<source xml:lang="en">Blocking Issue: {0}</source>
@@ -2124,15 +2124,15 @@ Esta operación puede tardar varios minutos.</target>
</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 handle connectivity between source and target and upload backups from an on-premises network file share to Azure (if applicable).</source>
<target state="new">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).</target>
<target state="translated">Azure Database Migration Service aprovecha el entorno de ejecución de integración autohospedado de Azure Data Factory para controlar la conectividad entre el origen y el destino, y cargar copias de seguridad de un recurso compartido de archivos de red local en Azure (si procede).</target>
</trans-unit>
<trans-unit id="sql.migration.service.container.container.description2">
<source xml:lang="en">Follow the instructions below to set up self-hosted integration runtime.</source>
<target state="new">Follow the instructions below to set up self-hosted integration runtime.</target>
<target state="translated">Siga estas instrucciones para configurar un entorno de ejecución de integración autohospedado.</target>
</trans-unit>
<trans-unit id="sql.migration.service.container.heading">
<source xml:lang="en">Set up integration runtime</source>
<target state="new">Set up integration runtime</target>
<target state="translated">Configuración del entorno de ejecución de integración</target>
</trans-unit>
<trans-unit id="sql.migration.service.container.loading.help">
<source xml:lang="en">Loading Migration Services</source>
@@ -2182,9 +2182,9 @@ Esta operación puede tardar varios minutos.</target>
<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>
<target state="new">Azure Database Migration Service is not registered. Azure Database Migration Service '{0}' needs to be registered with self-hosted integration runtime on any node.
<target state="translated">Azure Database Migration Service no está registrado. Azure Database Migration Service "{0}" debe registrarse con entorno de ejecución de integración autohospedado en cualquier nodo.
See below for registration instructions.</target>
Consulte la información siguiente para ver las instrucciones de registro.</target>
</trans-unit>
<trans-unit id="sql.migration.service.prompt">
<source xml:lang="en">{0} (change)</source>
@@ -2194,17 +2194,17 @@ See below for registration instructions.</target>
<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>
<target state="new">Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on node(s) - {1}
<target state="translated">Azure Database Migration Service "{0}" está conectado a un entorno de ejecución de integración autohospedado que se ejecuta en nodos: {1}
For improved performance and high availability, you can register additional nodes.</target>
Para mejorar el rendimiento y la alta disponibilidad, puede registrar nodos adicionales.</target>
</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>
<target state="new">Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on node(s) - {1}
<target state="translated">Azure Database Migration Service "{0}" está conectado a un entorno de ejecución de integración autohospedado que se ejecuta en nodos: {1}
For improved performance and high availability, you can register additional nodes. See below for registration instructions.</target>
Para mejorar el rendimiento y la alta disponibilidad, puede registrar nodos adicionales. Consulte la información siguiente para ver las instrucciones de registro.</target>
</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>
@@ -2220,7 +2220,7 @@ For improved performance and high availability, you can register additional node
</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>
<target state="new">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.</target>
<target state="translated">Escriba la información siguiente para agregar una nueva instancia de Azure Database Migration Service. Para registrar el entorno de ejecución de integración autohospedado, seleccione "Mis copias de seguridad de base de datos están en un recurso compartido de red" en la página anterior.</target>
</trans-unit>
<trans-unit id="sql.migration.services.dialog.title">
<source xml:lang="en">Create Azure Database Migration Service</source>