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

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

View File

@@ -792,11 +792,11 @@ L'operazione potrebbe richiedere qualche minuto.</target>
</trans-unit>
<trans-unit id="sql.migration.database.assessment.xevents.description">
<source xml:lang="en">For the selected databases, optionally provide extended event session files to assess ad-hoc or dynamic SQL queries or any DML statements initiated through the application data layer. {0}</source>
<target state="new">For the selected databases, optionally provide extended event session files to assess ad-hoc or dynamic SQL queries or any DML statements initiated through the application data layer. {0}</target>
<target state="translated">È possibile fornire file di sessioni degli eventi estesi per i database selezionati, al fine di valutare le query SQL dinamiche o ad hoc, o le eventuali istruzioni DML avviate attraverso il livello di dati dell'applicazione. {0}</target>
</trans-unit>
<trans-unit id="sql.migration.database.assessment.xevents.instructions">
<source xml:lang="en">Select a folder where extended events session files (.xel and .xem) are stored</source>
<target state="new">Select a folder where extended events session files (.xel and .xem) are stored</target>
<target state="translated">Seleziona una cartella in cui sono archiviati i file di sessione degli eventi estesi (.xel e .xem).</target>
</trans-unit>
<trans-unit id="sql.migration.database.assessment.xevents.link">
<source xml:lang="en">Learn more</source>
@@ -804,7 +804,7 @@ L'operazione potrebbe richiedere qualche minuto.</target>
</trans-unit>
<trans-unit id="sql.migration.database.assessment.xevents.title">
<source xml:lang="en">Assess extended event sessions</source>
<target state="new">Assess extended event sessions</target>
<target state="translated">Valutare le sessioni di eventi estesi</target>
</trans-unit>
<trans-unit id="sql.migration.database.backup.load.error">
<source xml:lang="en">An error occurred while accessing database details.</source>
@@ -1332,15 +1332,15 @@ L'operazione potrebbe richiedere qualche minuto.</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">Passaggio 2: Utilizzare le chiavi seguenti per registrare il runtime di integrazione</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">Passaggio 3: Fare clic sul pulsante 'Test connessione' per controllare la connessione tra il Servizio Migrazione del database di Azure e il runtime di integrazione</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">Passaggio 3: Fare clic sul pulsante Aggiorna sopra per controllare la connessione tra Servizio Migrazione del database di Azure e il runtime di integrazione</target>
</trans-unit>
<trans-unit id="sql.migration.issue.aria.label">
<source xml:lang="en">Blocking Issue: {0}</source>
@@ -2124,15 +2124,15 @@ L'operazione potrebbe richiedere qualche minuto.</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">Servizio Migrazione del database di Azure sfrutta il runtime di integrazione self-hosted di Azure Data Factory per gestire la connettività tra origine e destinazione e caricare i backup da una condivisione file di rete locale in Azure (se applicabile).</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">Seguire le istruzioni seguenti per configurare il runtime di integrazione self-hosted.</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">Configurare il runtime di integrazione</target>
</trans-unit>
<trans-unit id="sql.migration.service.container.loading.help">
<source xml:lang="en">Loading Migration Services</source>
@@ -2182,9 +2182,9 @@ L'operazione potrebbe richiedere qualche minuto.</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">Servizio Migrazione del database di Azure non è registrato. Servizio Migrazione del database di Azure '{0}' deve essere registrato con il runtime di integrazione self-hosted in qualsiasi nodo.
See below for registration instructions.</target>
Vedere di seguito per le istruzioni di registrazione.</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">Servizio Migrazione del database di Azure '{0}{0}' è connesso al runtime di integrazione self-hosted in esecuzione nei nodi. {1}
For improved performance and high availability, you can register additional nodes.</target>
Per migliorare le prestazioni e la disponibilità elevata, è possibile registrare nodi aggiuntivi.</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">Servizio Migrazione del database di Azure '{0}' è connesso al runtime di integrazione self-hosted in esecuzione nei nodi. {1}
For improved performance and high availability, you can register additional nodes. See below for registration instructions.</target>
Per migliorare le prestazioni e la disponibilità elevata, è possibile registrare nodi aggiuntivi. Per istruzioni sulla registrazione, vedere di seguito.</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">Immettere le informazioni seguenti per aggiungere un nuovo Servizio Migrazione del database di Azure. Per registrare il runtime di integrazione self-hosted, selezionare “I miei backup del database si trovano in una condivisione di rete” nella pagina precedente.</target>
</trans-unit>
<trans-unit id="sql.migration.services.dialog.title">
<source xml:lang="en">Create Azure Database Migration Service</source>