diff --git a/i18n/ads-language-pack-de/CHANGELOG.md b/i18n/ads-language-pack-de/CHANGELOG.md index 2793c1d12a36..4a06c9eb75f2 100644 --- a/i18n/ads-language-pack-de/CHANGELOG.md +++ b/i18n/ads-language-pack-de/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-de" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-de/package.json b/i18n/ads-language-pack-de/package.json index eefc11ddf6ea..542af07d10c9 100644 --- a/i18n/ads-language-pack-de/package.json +++ b/i18n/ads-language-pack-de/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-de", "displayName": "German Language Pack for Azure Data Studio", "description": "Language pack extension for German", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-de/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-de/translations/extensions/Microsoft.mssql.i18n.json index 8a92961bcd85..a8429b7a2b0e 100644 --- a/i18n/ads-language-pack-de/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-de/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "Dateigruppen", "objectManagement.databaseProperties.filegrowthLimitError": "Die Dateivergrößerung darf die maximale Dateigröße für eine Datei nicht überschreiten.", "objectManagement.databaseProperties.filesText": "Dateien", - "objectManagement.optionsSectionHeader": "Dateien", + "objectManagement.filesSectionHeader": "Dateien", "objectManagement.databaseProperties.filestreamFilesText": "Filestream-Dateien", "objectManagement.filterSectionTitle": "Filter", "objectManagement.findText": "Suchen", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "Betriebsmodus (Tatsächlich)", "objectManagement.databaseProperties.requestedOperationModeText": "Betriebsmodus (Angefordert)", "objectManagement.optimizeAdHocWorkloadsLabel": "Ad-hoc-Workloads optimieren", + "objectManagement.optionsSectionHeader": "Optionen", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "Ursprünglicher Dateiname", "objectManagement.overwriteExistingBackups": "Alle vorhandenen Sicherungssätze überschreiben", "objectManagement.backupOverwriteMedia": "Medium überschreiben", diff --git a/i18n/ads-language-pack-de/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-de/translations/extensions/Microsoft.notebook.i18n.json index 05c9e43ec43d..d1fda1fb6973 100644 --- a/i18n/ads-language-pack-de/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-de/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "Durchsuchen", - "configurePython.installationType": "Installationstyp", - "configurePython.newInstall": "Neue Python-Installation", "configurePythyon.noVersionsFound": "Keine unterstützten Python-Versionen gefunden.", "configurePython.descriptionWithoutKernel": "Für Notebook-Kernel ist die Konfiguration einer Python-Runtime und die Installation von Abhängigkeiten erforderlich.", - "configurePython.locationTextBoxText": "Python-Installationsspeicherort", - "configurePython.pythonConfigured": "Python-Runtime konfiguriert!", + "configurePython.locationTextBoxText": "Python-Speicherort", "configurePython.selectFileLabel": "Auswählen", "configurePython.descriptionWithKernel": "Für den \"{0}\"-Kernel ist die Konfiguration einer Python-Runtime und die Installation von Abhängigkeiten erforderlich.", - "configurePython.existingInstall": "Vorhandene Python-Installation verwenden", + "configurePythyon.existingInstance": "{0} (aktuelle Python-Instanz)", "configurePythyon.customPathLabel": "{0} (Benutzerdefiniert)", - "configurePythyon.defaultPathLabel": "{0} (Standard)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "Ein Notebook-Pfad ist erforderlich." }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "Aktive Python-Notebooksitzungen werden heruntergefahren, um sie zu aktualisieren. Möchten Sie jetzt fortfahren?", "msgWaitingForInstall": "Aktuell wird eine weitere Python-Installation ausgeführt. Es wird auf den Abschluss des Vorgangs gewartet.", - "msgPythonRunningError": "Eine vorhandene Python-Installation kann nicht überschrieben werden, während Python ausgeführt wird. Schließen Sie alle aktiven Notebooks, bevor Sie fortfahren.", - "dontAskAgain": "Nicht mehr fragen", - "msgDownloadPython": "Lokales Python für die Plattform \"{0}\" wird nach \"{1}\" heruntergeladen.", - "msgPythonDownloadPending": "Das Python-Paket wird heruntergeladen.", "msgGetPythonUserDirFailed": "Fehler beim Abrufen des Python-Benutzerpfads: {0}", "msgPackageRetrievalFailed": "Fehler beim Abrufen der Liste installierter Pakete: {0}", - "msgPythonDirectoryError": "Fehler beim Erstellen des Python-Installationsverzeichnisses.", - "msgPythonDownloadError": "Fehler beim Herunterladen des Python-Setups.", - "msgPythonUnpackError": "Fehler beim Entpacken des Python-Pakets.", "msgTaskName": "Notebook-Abhängigkeiten werden installiert.", "msgDependenciesInstallationFailed": "Fehler beim Installieren von Notebook-Abhängigkeiten: {0}", "msgInstallPkgStart": "Notebook-Abhängigkeiten werden installiert. Weitere Informationen finden Sie in der Aufgabenansicht.", - "no": "Nein", "msgInstallPkgFinish": "Die Installation von Notebook-Abhängigkeiten ist abgeschlossen.", - "msgInstallPkgProgress": "Notebook-Abhängigkeiten werden installiert.", - "msgPythonDownloadComplete": "Der Python-Download ist abgeschlossen.", - "msgPythonVersionUpdatePrompt": "Python {0} ist jetzt in Azure Data Studio verfügbar. Die aktuelle Python-Version (3.6.6) wird ab Dezember 2021 nicht mehr unterstützt. Möchten Sie jetzt auf Python {0} aktualisieren?", - "msgPythonVersionUpdateWarning": "Python {0} wird installiert und ersetzt Python 3.6.6. Einige Pakete sind möglicherweise nicht mehr mit der neuen Version kompatibel oder müssen neu installiert werden. Ein Notizbuch wird erstellt, damit Sie alle PIP-Pakete neu installieren können. Möchten Sie das Update jetzt fortsetzen?", - "msgPythonUnpackPending": "Python-Paket entpacken", - "yes": "Ja" + "msgInstallPkgProgress": "Notebook-Abhängigkeiten werden installiert." }, "dist/jupyter/jupyterServerManager": { "shutdownError": "Fehler beim Herunterfahren des Notebook-Servers: {0}" diff --git a/i18n/ads-language-pack-de/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-de/translations/extensions/Microsoft.sql-migration.i18n.json index 91aa3975a226..ee4b26fca703 100644 --- a/i18n/ads-language-pack-de/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-de/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "Ein Cutover der Migration einer verwalteten SQL-Instanz kann auf der Dienstebene \"Unternehmenskritisch\" erheblich länger dauern als auf \"Universell\", da für drei sekundäre Replikate eine Always On-Hochverfügbarkeitsgruppe angelegt werden muss. Die Dauer des Vorgangs hängt von der Größe der Daten ab. Die Seedinggeschwindigkeit ist in 90 % der Fälle 220 GB/Stunde oder höher.", "sql.migration.dashboard.help.description.dmsGuide": "Ein Hub mit Artikeln zur Migration, die Schritt-für-Schritt-Anleitungen für die Migration und Modernisierung Ihrer Datenressourcen in Azure bereitstellen.", "sql.migration.resource.group.description": "Eine Ressourcengruppe ist ein Container, der zugehörige Ressourcen für eine Azure-Lösung enthält.", + "sql.migration.target.provisioning.template.display.limit": "Für eine einzelne ARM-Vorlage gilt eine Bereitstellungsbeschränkung von maximal 50 Azure SQL-Datenbanken. Die Vorlage für die ersten 50 Datenbanken wird unten angezeigt. Um alle Vorlagen anzuzeigen, speichern Sie die JSON-Vorlagendatei in einem lokalen Speicher oder Azure Blob Storage.", "sql.migration.pre.req.2": "Eine oder mehrere SQL Server-Quelldatenbanken, die lokal oder auf SQL Server auf einer Azure-VM oder einem beliebigen virtuellen Computer in der Cloud (privat, öffentlich) ausgeführt werden.", "sql.migration.dashboard.help.description.sqldb": "Ein Tutorial, das Schritt für Schritt erklärt, wie Sie Datenbanken von einer SQL Server-Instanz (vor Ort oder Azure Virtual Machines) zu Azure SQL Database migrieren.", "sql.migration.dashboard.help.description.mi": "Ein Tutorial, das Sie mit einer Schritt-für-Schritt-Anleitung dabei unterstützt, Datenbanken aus einer SQL Server-Instanz (lokal oder Azure Virtual Machines) mit minimaler Downtime zu Azure SQL Managed Instance zu migrieren.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "Alle Sicherungen wiederhergestellt", "sql.migration.view.all": "Alle Datenbankmigrationen", "sql.migration.all.fields.required": "Alle Felder müssen ausgefüllt werden.", + "sql.ir.version.mismatch": "Alle Knoten müssen die gleiche Version aufweisen, um konfiguriert zu werden.", "sql.migration.all.source.tables.empty": "Alle Quelltabellen sind leer. Für die Datenmigration ist keine Tabelle zur Auswahl verfügbar. Sie sind jedoch für die Schemamigration verfügbar, wenn sie nicht auf dem Ziel vorhanden sind.", "sql.migration.unavailable.source.tables.heading": "Alle unten aufgeführten Tabellen sind leer. Für die Datenmigration ist keine Tabelle zur Auswahl verfügbar. Wenn sie jedoch auf dem Ziel nicht vorhanden sind, ist die Schemamigration verfügbar.", "sql.migration.missing.tables.heading": "Alle unten aufgeführten Tabellen fehlen auf dem Ziel. Um die Daten in diesen Tabellen zu migrieren, wählen Sie oben die Option \"Schema migrieren\" aus.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "Möchten Sie diese Migration abbrechen?", "sql.delete.migration.confirmation": "Möchten Sie die Migration wirklich löschen?", "sql.migration.migration.list.ascending.label": "Aufsteigend", - "sql.migration.database.assessment.xevents.title": "Erweiterte Ereignissitzungen bewerten", + "sql.migration.database.assessment.xevents.title": "Ad-hoc- oder dynamisches SQL bewerten", "sql.migration.assessed.dbs.label": "Bewertete Datenbanken: {0}", "sql.migration.assessment.findings.label": "Bewertungsergebnisse", "sql.migration.assessment.in.progress": "Bewertung wird durchgeführt", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Azure-Dienst zur Datenbankmigration", "sql.migration.service.ready": "Azure Database Migration Service \"{0}\" ist mit einer selbstgehosteten Integration Runtime verbunden, die auf Knoten ausgeführt wird – {1}\r\n\r\nUm die Leistung und Hochverfügbarkeit zu verbessern, können Sie zusätzliche Knoten registrieren.", "sql.migration.service.ready.below": "Azure Database Migration Service '{0}' ist mit einer selbstgehosteten Integration Runtime verbunden, die auf einem oder mehreren Knoten ausgeführt wird – {1}\r\n\r\nFür bessere Leistung und Hochverfügbarkeit können Sie zusätzliche Knoten registrieren. Anweisungen zur Registrierung finden Sie unten.", + "sql.migration.service.ready.without.nodes": "Azure Database Migration Service „{0}“ ist mit einer selbstgehosteten Integration Runtime verbunden, die auf den folgenden Knoten ausgeführt wird", "sql.migration.service.header": "Details zum Azure Database Migration Service \"{0}\":", "sql.migration.service.not.ready": "Azure Database Migration Service ist nicht registriert. Azure Database Migration Service \"{0}\" muss bei selbstgehosteten Integration Runtime auf jedem Knoten registriert werden.", "sql.migration.service.not.ready.below": "Azure Database Migration Service ist nicht registriert. Azure Database Migration Service '{0}' muss mit einer selbstgehosteten Integration Runtime auf einem beliebigen Knoten registriert werden.\r\n\r\nAnweisungen zur Registrierung finden Sie unten.", + "sql.migration.ir.container.description": "Azure Database Migration Service nutzt die selbstgehostete Integration Runtime von Azure Data Factory, um Sicherungen von der lokalen Netzwerk-Dateifreigabe in Azure hochzuladen. Basierend auf der Auswahl auf der vorherigen Seite müssen Sie eine selbstgehostete Integration Runtime einrichten.", "sql.migration.service.container.container.description1": "Azure Database Migration Service nutzt die selbstgehostete Integration Runtime von Azure Data Factory, um die Konnektivität zwischen Quelle und Ziel zu verarbeiten und Sicherungen von einer lokalen Netzwerkdateifreigabe in Azure hochzuladen (falls zutreffend).", "sql.migration.services.name": "Name des Azure Database Migration Service.", "sql.migration.ir.page.description": "Azure Database Migration Service orchestriert Datenbankmigrationsaktivitäten und verfolgt deren Fortschritt. Sie können einen bestehenden Datenbankmigrationsdienst auswählen, wenn Sie zuvor einen erstellt haben, oder unten einen neuen erstellen.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Azure-Region für Ihre Azure Database Migration Service. Es werden nur Regionen angezeigt, die einen Dienst enthalten.", "sql.migration.services.location": "Azure-Region für Ihren Azure Database Migration Service. Dies sollte die gleiche Region sein wie Ihre Ziel-Azure SQL.", "sql.migration.sku.location": "Azure-Region für Ihr Azure SQL-Ziel. Es werden nur Regionen angezeigt, die ein für die Migration geeignetes Ziel enthalten.", + "sql.migration.storage.account.location": "Azure-Region für Ihr Speicherkonto. Es werden nur Regionen angezeigt, die ein Speicherkonto enthalten.", "sql.migration.summary.azure.storage": "Azure-Speicher", "sql.migration.validate.ir.validation.result.label.storage": "Azure-Speicherkonnektivität", "sql.migration.summary.azure.storage.subscription": "Azure-Speicherabonnement", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "Größe der Sicherungsdatei (MB)", "sql.migration.backup.start.time": "Startzeitpunkt für Sicherung", "sql.migration.wizard.sku.all": "Basierend auf den Bewertungsergebnissen können alle {0} Ihrer Datenbanken in einem Onlinezustand zu Azure SQL migriert werden.", + "sql.migration.target.provisioning.description": "Unten finden Sie das ARM-Skript für die empfohlene Ziel-SKU. Sie können das Skript als Vorlage speichern.", "sql.migration.sku.targetStorageConfiguration.info": "Unten finden Sie die Zielspeicherkonfiguration, die zur Erfüllung Ihrer Speicherleistungsanforderungen erforderlich ist.", "sql.migration.blob.container.title": "Blobcontainer", "sql.migration.blob.container.label": "Blob-Container-Ressourcengruppe", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "Klicken Sie, um Details zum Fehler anzuzeigen", "sql.migration.service.details.button.label": "Schließen", "sql.migration.close": "Schließen", + "sql.migration.target.provisioning.close": "Schließen", "sql.migration.sku.azureRecommendation.collectData.method": "Leistungsdaten jetzt sammeln", "sql.login.migration.collecting.target.logins.failed": "Fehler beim Erfassen der Zielanmeldung. Fehlercode: {0}", "sql.migration.status.collectioncompleted": "Sammlung abgeschlossen", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "Ein Cutover ohne Wiederherstellung aller Sicherungen kann zu Datenverlusten führen.", "sql.migration.restore.status.completing.migration": "Migration wird abgeschlossen", "sql.migration.save.close.popup": "Konfiguration gespeichert. Die Leistungsdatensammlung wird weiterhin im Hintergrund ausgeführt. Sie können die Sammlung beenden, wenn Sie möchten.", + "sql.migration.configure.ir": "Integration Runtime konfigurieren", + "sql.ir.configure.manually": "Manuell konfigurieren ", + "sql.ir.configure.powershellscript": "Konfigurieren mithilfe eines PowerShell-Skripts ", "sql.migration.connection.label": "Verbinden", "sql.migration.community.support.description": "Verbindung mit der Microsoft-Community herstellen", "sql.migration.wizard.target.connection.error": "Verbindungsfehler: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "Beschreibung", "sql.migration.details.title": "Details", "sql.migration.details.copied": "Details kopiert", + "sql.migration.validate.ir.error.message": "Details zu „{0}“ sind obligatorisch und fehlen.", "sql.migration.field.label.deteected.files": "Erkannte Dateien", "sql.migration.dashboard.description": "Ermitteln Sie die Migrationsbereitschaft Ihrer SQL Server-Instanzen, identifizieren Sie ein empfohlenes Azure SQL-Ziel, und schließen Sie die Migration Ihrer SQL Server-Instanz zu Azure SQL Managed Instance, SQL Server auf Azure Virtual Machines oder Azure SQL-Datenbank ab.", "sql.migration.restore.backuptype.differentialdatabase": "Differenzielle Datenbank", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "Geben Sie die Anmeldeinformationen für die Windows-Authentifizierung ein, die zum Herstellen einer Verbindung mit SQL Server-Instanz {0}verwendet werden. Diese Anmeldeinformationen werden verwendet, um eine Verbindung mit der SQL Server-Instanz herzustellen und gültige Sicherungsdateien zu identifizieren.", "sql.migration.source.details.windowAuth.db": "Geben Sie die Windows-Authentifizierungsdaten ein, die für die Verbindung zur SQL Server-Instanz {0} verwendet werden. Diese Anmeldeinformationen werden für die Verbindung mit der SQL Server-Instanz von der selbst gehosteten Integrationslaufzeit aus verwendet.", "sql.migration.enter.your.sql.cred": "Geben Sie die Anmeldeinformationen für die Quelle der SQL Server-Instanz ein. Diese Anmeldeinformationen werden beim Migrieren von Datenbanken zu Azure SQL verwendet.", + "sql.migration.select.storage.account.heading": "Geben Sie unten die Details ein, um das Azure Storage-Konto auszuwählen und das Skript als Vorlage zu speichern.", "sql.migration.services.container.description": "Geben Sie die folgenden Informationen ein, um einen neuen Azure Database Migration Service hinzuzufügen.", "sql.migration.services.container.description.network": "Geben Sie die folgenden Informationen ein, um eine neue Azure Database Migration Service hinzuzufügen. Um die selbstgehostete Integration Runtime zu registrieren, wählen Sie auf der vorherigen Seite \"Meine Datenbanksicherungen befinden sich auf einer Netzwerkfreigabe\" aus.", "sql.migration.sku.parameters.text": "Geben Sie unten die Informationen ein, um die Empfehlungsparameter zu bearbeiten.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "Fehler: Azure SQL Managed Instance unterstützt maximal {0} Benutzerdatenbanken pro Instanz. Wählen Sie {0} oder weniger Datenbanken aus, um den Vorgang fortzusetzen.", "sql.login.migration.migrate.server.roles.and.set.permissions": "Das Einrichten von Benutzerzuordnungen wurde abgeschlossen.\r\n\r\nAktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berechtigungen festgelegt. Dies nimmt einige Zeit in Anspruch.", "sql.login.migration.establish.user.mappings.failed": "Fehler beim Einrichten von Benutzerzuordnungen.", + "sql.ir.powershellscript": "Skript ausführen ", + "sql.ir.executing.powershellscript": "Die Ausführung wurde gestartet, und das geöffnete PowerShell-Fenster wird überwacht. ", "sql.migration.support.resources.description": "Dokumentation erkunden", "sql.migration.tde.wizard.optionads": "Exportieren Sie meine Zertifikate und privaten Schlüssel in das Ziel.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "Fehler beim Migrieren von {0} Anmeldungen zu {1} „{2}“", "sql.migration.notebook.open.error": "Fehler beim Öffnen des Migrationsnotebooks.", "sql.migration.dms.provision.failed": "Fehler beim Bereitstellen eines Database Migration Service. Warten Sie einige Minuten, und versuchen Sie es dann erneut.", + "sql.migration.target.provisioning.save.template.fail": "Fehler beim Speichern der ARM-Vorlage", + "sql.migration.target.provisioning.upload.template.fail": "Fehler beim Hochladen der ARM-Vorlage", "sql.migration.tab.button.feedback.description": "Feedback", "sql.migration.tab.button.feedback.label": "Feedback", "sql.migration.feedback.issue.title": "Feedback zur Migrationserfahrung", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "Befolgen Sie die nachstehenden Anweisungen, um selbst gehostete Integration Runtime einzurichten.", "sql.migration.database.table.selection.description": "Klicken Sie unten für jede Datenbank auf Bearbeiten, um die Tabellen auszuwählen, die von der Quelle zum Ziel migriert werden sollen. Überprüfen Sie dann die angegebene Konfiguration, bevor Sie auf „Weiter“ klicken, indem Sie auf „Validierung ausführen“ klicken.", "sql.migration.sql.vm.page.blob.info": "Für Zielserver, auf denen SQL Server 2014 oder niedriger ausgeführt wird, müssen Sie Ihre Datenbanksicherungen in einem Azure Storage Blob Container speichern, anstatt sie mithilfe der Netzwerkfreigabeoption hochzuladen. Darüber hinaus müssen Sie die Sicherungsdateien als Seitenblobs speichern, da Blockblobs nur für Ziele unterstützt werden, die SQL Server 2016 oder höher ausführen. Weitere Informationen: {0}", - "sql.migration.database.assessment.xevents.description": "Stellen Sie für die ausgewählten Datenbanken optional Sitzungsdateien für erweiterte Ereignisse bereit, um Ad-hoc- oder dynamische SQL-Abfragen oder DML-Anweisungen zu bewerten, die über die Anwendungsdatenschicht initiiert wurden. {0}", + "sql.migration.database.assessment.xevents.description": "Stellen Sie für die ausgewählten Datenbanken optional Sitzungsdateien für erweiterte Ereignisse bereit, um Ad-hoc- oder dynamische SQL-Abfragen oder DML-Anweisungen zu bewerten, die über die Anwendungsdatenschicht initiiert wurden.", "sql.migration.full.backup.files": "Vollständige Sicherungsdatei(en)", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "Allgemein", + "sql.migration.target.provisioning.generate.template": "Vorlage generieren", "sql.migration.status.generatingscript": "Skript wird generiert", "sql.migration.status.generatingcompleted": "Generieren des Skripts abgeschlossen", "sql.migration.sku.get.recommendation": "Azure-Empfehlung abrufen", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "Ich bestätige, dass keine zusätzlichen Protokollsicherungen zur Verfügung stehen und der Cutover abgeschlossen werden soll.", "sql.migration.tde.wizard.optionadsconfirm": "Ich stimme zu, dass meine Anmeldeinformationen für den Zugriff auf die Zertifikate verwendet werden dürfen.", "sql.migration.tde.wizard.optionmanual": "Ich habe meine Zertifikate und privaten Schlüssel bereits zum Ziel migriert.", + "sql.ir.local.ir.definition": "Ich möchte die selbstgehostete Integration Runtime auf einem anderen Windows-Computer einrichten, der nicht mein lokaler Computer ist.", "sql.migration.sku.io.memory.requirement": "E/A-Latenzanforderung", + "sql.ir.ip.address": "IP-Adresse", + "sql.ir.config.type": "IR-Konfigurationstyp", + "sql.ir.ir.version": "IR-Version", "sql.migration.empty.table.subtext": "Wenn Ergebnisse erwartet wurden, überprüfen Sie die Verbindung mit der SQL Server-Instanz.", "sql.migration.wizard.cancel.reason.others.input.box.note": "Wenn Sie andere ausgewählt haben, schreiben Sie bitte eine kurze Notiz.", "sql.migration.impact": "Auswirkung", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "Bewertung in Azure SQL importieren", "sql.migration.sku.import.performance.data": "Leistungsdaten importieren", "sql.migration.sku.import.performance.data.dialog.description": "Importieren Sie diese Datendatei aus einem vorhandenen Ordner, wenn Sie diese Daten bereits mit dem Datenmigrations-Assistenten gesammelt haben.", + "sql.ir.important": "Wichtig", "sql.migration.database.migration.migration.mode.tool.tip": "In Azure Database Migration Service können Sie Ihre Datenbanken offline oder online migrieren. Bei einer Offline-Migration beginnt die Downtime der Anwendung, wenn die Migration beginnt. Um die Downtime auf die Zeit zu begrenzen, die Sie benötigen, um nach der Migration auf die neue Umgebung umzuschalten, verwenden Sie eine Online-Migration.", "sql.migration.tde.validation.requirements.message": "Damit die Zertifikatmigration erfolgreich ist, müssen Sie alle unten aufgeführten Anforderungen erfüllen.\r\n\r\nKlicken Sie auf \"Überprüfung ausführen\", um zu überprüfen, ob die Anforderungen erfüllt sind.", "sql.migration.copy.status.inprogress": "In Bearbeitung", @@ -484,6 +506,8 @@ "sql.login.migration.type": "Anmeldetyp", "sql.migration.sku.logs.iops.requirement": "IOPS-Anforderung für Protokolle", "sql.migration.field.label.mi.restore.state": "Wiederherstellungsstatus der verwalteten Instanz", + "sql.ir.manual.ir.collapsed": "Manuelle IR-Konfiguration reduziert", + "sql.ir.manual.ir.expanded": "Manuelle IR-Konfiguration erweitert", "sql.migration.map.target.heading": "Zuordnen ausgewählter Quelldatenbanken zu Zieldatenbanken für die Migration", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "Speicheroptimierte Premium-Serie", "sql.migration.sku.memory.requirement": "Arbeitsspeicheranforderungen", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "Neue Migration", "sql.migration.newSupportRequest": "Neue Supportanfrage", "sql.migration.saved.assessment.next": "Weiter", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "Universell der nächsten Generation", "sql.migration.no": "Nein", "sql.migration.no.sqldatabaseserver.found": "Es wurden keine Azure SQL-Datenbank-Server gefunden.", "sql.migration.no.sqldatabase.found": "Es wurden keine Azure SQL-Datenbanken gefunden.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Für die Migration zu SQL Server auf dem virtuellen Azure-Computer wurden keine Probleme gefunden.", "sql.migration.no.location.found": "Keine Speicherorte gefunden.", "sql.migration.no.managedInstance.found": "Keine verwalteten Instanzen gefunden.", + "sql.ir.no.node.found": "Kein Knoten gefunden.", "sql.migration.no.pending.backups": "Keine ausstehenden Sicherungen. Klicken Sie auf \"Aktualisieren\", um den aktuellen Status zu prüfen.", "sql.migration.cancel.feedback.no.reason.selected": "Kein Grund ausgewählt", "sql.migration.wizard.sku.error.noRecommendation": "Keine Empfehlung verfügbar", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "Keine Abonnements gefunden.", "sql.migration.select.target.label": "Kein Ziel ausgewählt. Wählen Sie ein Ziel aus, um die Bewertungszusammenfassung anzuzeigen.", "sql.migration.no.virtualMachine.found": "Keine VMs gefunden.", + "sql.ir.node.name": "Knotenname", "sql.migration.restore.status.none": "Keine", "sql.migration.restore.backupset.status.none": "Keine", "sql.migration.parallel.copy.type.none": "Keine", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "Nicht bereit", "sql.migration.restore.status.not.started": "Nicht gestartet", "sql.login.migration.steps.not.started": "Nicht gestartet", + "sql.ir.recommended.link": "Hinweis: Empfehlungen zur selbstgehosteten Integration Runtime", "sql.migration.backup.file.number.of.stripes": "Anzahl von Bereichsstreifen", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "OK", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "Gesammelte Objekte", "sql.migration.offline": "Offline", "sql.migration.database.migration.mode.offline.label": "Offlinemigration", + "sql.ir.powershellscript.definition": "Nach der Ausführung in PowerShell lädt das unten gezeigte eindeutige Skript die selbstgehostete Integration Runtime herunter, installiert sie und registriert sie beim Azure Database Migration Service. PowerShell muss auf dem Zielcomputer installiert sein.", "sql.migration.online": "Online", "sql.migration.database.migration.mode.online.label": "Onlinemigration", "sql.migration.open": "Öffnen", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "Bitte wählen Sie den Speicherort Ihrer Datenbanksicherungsdateien aus, bevor Sie fortfahren.", "sql.migration.cancel.feedback.reason.container.description": "Bitte nehmen Sie sich einen Moment Zeit, um uns den Grund für den Abbruch der Migration mitzuteilen. Dies hilft uns, die Erfahrung zu verbessern.", "sql.migration.port.label": "Port", + "sql.ir.powershell.script.saved": "PowerShell-Skript gespeichert", + "sql.ir.ps.script.collapsed": "PowerShell-Skript reduziert", + "sql.ir.ps.script.expanded": "PowerShell-Skript erweitert", "sql.migration.status.prefetchobjects": "Objekte vorab abrufen", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "SSD Premium", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "SSD Premium v2", "sql.migration.sku.azureConfiguration.premiumSeries": "Premium-Serie", "sql.migration.copy.status.preparingforcopy": "Wird vorbereitet", + "sql.ir.powershell.prereq": "Voraussetzung: Benötigen Sie PowerShell mit Ausführungsberechtigungen als Administrator. ", "sql.login.migration.status.page.previous.button.title": "Zurück (deaktiviert)", "sql.migration.tde.migrate.results.heading.previous": "Vorherige Zertifikatmigrationsergebnisse:", "sql.migration.provide.unique.containers": "Geben Sie einen eindeutigen Container für jede Zieldatenbank an. Betroffene Datenbanken: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "Fehler beim Aktualisieren der Anmeldeliste vom Ziel.", "sql.login.migration.refresh.login.data.successful": "Die Anmeldeliste wurde erfolgreich aktualisiert. Gefundene Quellanmeldungen {0}, gefundene Zielanmeldungen {1}", "sql.migration.resourceGroups": "Ressourcengruppe", + "sql.migration.storage.account.resource.group.label": "Ressourcengruppe", "sql.migration.rg.created": "Ressourcengruppe erstellt", "sql.migration.services.resource.group": "Ressourcengruppe für Ihren Azure Database Migration Service.", "sql.migration.dms.resource_group": "Ressourcengruppe für Ihr Azure SQL-Ziel. Es werden nur Ressourcengruppen angezeigt, die einen Dienst enthalten.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "SQL-Protokolldateien", "sql.migration.sql.assessment.notebook.title": "SQL-Migrationsbewertung", "sql.migration.sku.sql.temp": "SQL tempdb", + "sql.migration.target.provisioning.save": "Speichern", + "sql.migration.target.provisioning.title": "Vorlage speichern", "sql.migration.save.close": "Speichern und schließen", "sql.migration.save.assessment.report": "Bewertungsbericht speichern", "sql.migration.save.recommendation.report": "Empfehlungsbericht speichern", + "sql.ir.save.script": "Skript speichern", + "sql.migration.target.upload.to.azure": "Speichern in Azure-Blob-Container", "sql.migration.saved.assessment.result": "Gespeicherte Sitzung", "sql.migration.sku.parameters.scale.factor": "Skalierungsfaktor", "sql.migration.schema.data": "Schema und Daten", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "Sicherungen werden durchsucht", "sql.migration.wizard.troubleshooting": "Weitere Schritte zur Problembehandlung finden Sie unter folgendem Link: https://aka.ms/dms-migrations-troubleshooting.", "sql.migration.select": "Auswählen", + "sql.migration.select.storage.account.title": "Azure Storage-Konto auswählen", "sql.migration.select.service.title": "Database Migration Service auswählen", "sql.migration.select.service.prompt": "Database Migration Service auswählen", "sql.migration.select.service.select.a.service": "Database Migration Service auswählen", "sql.migration.invalid.migration.service.offline.error": "Wählen Sie einen Database Migration Service aus, der mit einem Knoten verbunden ist.", "sql.migration.status.select.service.MESSAGE": "Wählen Sie eine Database Migration Service aus, um Migrationen zu überwachen.", + "sql.migration.select.storage.select.a.storage.account": "Speicherkonto auswählen", "sql.migration.blob.container.select": "Wählen Sie zuerst einen BLOB-Containerwert aus.", "sql.migration.sku.import.performance.data.dialog.open.folder": "Ordner auswählen", "sql.migration.sku.import.performance.data.dialog.helper.message": "Wählen Sie einen Ordner auf Ihrem lokalen Laufwerk aus.", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "Validierung beenden", "sql.migration.sku.azureRecommendation.stop.popup": "Leistungsdatensammlung wird beendet...", "sql.migration.sku.targetStorageConfiguration.storage": "Speicher", - "sql.migration.storage.account": "Speicherkonto", + "sql.migration.select.storage.account.label": "Speicherkonto", + "sql.migration.storage.account.details.label": "Speicherkonto", "sql.migration.network.share.azure.header": "Speicherkontodetails", "sql.migration.subscription": "Abonnement", "sql.migration.blob.storage.subscription.label": "Abonnement", "sql.migration.dms.subscription": "Abonnementname für Ihren Azure Database Migration Service", "sql.migration.services.subscription": "Abonnementname für Ihren Azure Database Migration Service.", "sql.migration.sku.subscription": "Abonnementname für Ihr Azure SQL-Ziel", + "sql.migration.storage.account.subscription": "Abonnementname für Ihr Speicherkonto", "sql.migration.state.succeeded": "Erfolgreich", "sql.migration.tde.validation.status.succeeded": "Erfolgreich", "sql.migration.copy.status.succeeded": "Erfolgreich", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "Zieltyp", "sql.migration.username.label": "Zielbenutzername", "sql.migration.target.version": "Zielversion", + "sql.migration.target.provisioning.save.template.success": "Vorlage erfolgreich gespeichert", + "sql.migration.target.provisioning.upload.template.success": "Vorlage erfolgreich hochgeladen", "sql.migration.test.connection": "Verbindung testen", "sql.migration.dashboard.help.description.migrateUsingADS": "Die Azure SQL Migrationserweiterung für Azure Data Studio bietet Funktionen zum Bewerten, Abrufen der passenden Azure-Empfehlungen und migrieren von SQL Server-Datenbanken zu Azure.", "sql.migration.sqldb.not.ready": "Der SQL-Datenbank-Server „{0}“ ist für die Migration nicht verfügbar, da er sich derzeit im Zustand „{1}“ befindet. Wählen Sie einen verfügbaren SQL-Datenbank-Server aus, um fortzufahren.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "Protokollsicherung/en wird/werden hochgeladen.", "sql.migration.sqldb.column.usedparallelcopies": "Verwendete parallele Kopien", "sql.migration.path.user.account": "Benutzerkonto", + "sql.migration.network.share.user.account.label": "Benutzerkonto", "sql.migration.username": "Benutzername", + "sql.migration.database.assessment.qds.label": "Mit Abfragedatenspeicher (diese Option ist für Microsoft SQL Server 2016 und höher verfügbar)", + "sql.migration.database.assessment.xevents.label": "Erweiterte Ereignissitzungen verwenden", "sql.migration.starting.login": "Überprüfen und Migrieren der Anmeldungen ist in Bearbeitung", "sql.login.migration.establish.user.mappings": "Das Überprüfen und Migrieren von Anmeldungen wurde abgeschlossen.\r\n\r\nBenutzerzuordnungen werden eingerichtet.", "sql.migration.starting.login.failed": "Fehler beim Überprüfen und Migrieren von Anmeldungen.", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "Wir haben die folgenden Schritte ausgeführt:", "sql.login.migration.wizard.target.data.migration.warning": "Wir empfehlen, Ihre Datenbanken vor Beginn der Benutzernamenmigration zum Azure SQL-Ziel zu migrieren, um Fehler während des Prozesses zu vermeiden. Unabhängig davon können Sie diesen Migrationsprozess jederzeit durchführen, wenn Sie die Benutzerzuordnung für kürzlich migrierte Datenbanken aktualisieren möchten.\r\n\r\nWenn die Namen von Quelle und Datenbank nicht übereinstimmen, werden einige Berechtigungen möglicherweise nicht richtig angewendet.", "sql.migration.blob.storage.folder.info": "Stellen Sie beim Hochladen von Datenbanksicherungen in Ihren Blobcontainer sicher, dass Sicherungsdateien aus verschiedenen Datenbanken in separaten Ordnern gespeichert werden. Nur der Stamm des Containers und die Ordner auf höchstens einer Ebene werden unterstützt.", + "sql.ir.local.ir.setup.note": "Wenn Sie auf „Skript ausführen“ klicken, lädt das folgende PowerShell-Skript automatisch selbstgehostete Integration Runtime-Software herunter, installiert sie und registriert sie bei Ihrem Azure Database Migration Service. Um den Verbindungsstatus der IR zu überprüfen, wechseln Sie zurück zum vorherigen Bildschirm, und aktualisieren Sie. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "Wo möchten Sie gesammelte Daten speichern?", "sql.migration.network.share.windows.user.label": "Windows-Benutzerkonto mit Lesezugriff auf den Speicherort der Netzwerkfreigabe", "sql.migration.network.share.windows.user.info": "Windows-Benutzerkonto mit Lesezugriff auf den Speicherort der Netzwerkfreigabe.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Ihr Azure Database Migration Service-Ressourcenname", "sql.migration.sku.resource": "Name der Azure SQL-Zielressource", "sql.migration.sku.resource.port": "Ihre Azure SQL-Portnummer der Zielressource: 0 – 65535", + "sql.migration.storage.account.blob.container": "Name Ihres Blobcontainers", + "sql.migration.storage.account": "Geben Sie einen Speicherkontonamen ein.", "sql.migration.pre.req.4": "Details zum Speicherort Ihrer Datenbanksicherung, entweder eine Netzwerkdateifreigabe oder ein Azure Blob Storage- Container (für Azure SQL-Datenbankziele nicht erforderlich).", "sql.migration.wizard.sku.assessment.error.detail": "[Es sind keine Bewertungsergebnisse vorhanden, um die Bereitschaft Ihrer Datenbankmigration zu überprüfen. Durch Aktivieren dieses Kontrollkästchens bestätigen Sie, dass Sie mit der Migration Ihrer Datenbank zum gewünschten Azure SQL-Ziel fortfahren möchten.]", "sql.migration.network.share.path.format": "\\\\Servername.Domaenenname.com\\Sicherungsordner", diff --git a/i18n/ads-language-pack-es/CHANGELOG.md b/i18n/ads-language-pack-es/CHANGELOG.md index e3e7f7dda7c1..10c69c6a8f74 100644 --- a/i18n/ads-language-pack-es/CHANGELOG.md +++ b/i18n/ads-language-pack-es/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-es" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-es/package.json b/i18n/ads-language-pack-es/package.json index 9476b33ada5d..d5185835a7d9 100644 --- a/i18n/ads-language-pack-es/package.json +++ b/i18n/ads-language-pack-es/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-es", "displayName": "Spanish Language Pack for Azure Data Studio", "description": "Language pack extension for Spanish", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-es/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-es/translations/extensions/Microsoft.mssql.i18n.json index a03ff6612b0a..172fda4124c9 100644 --- a/i18n/ads-language-pack-es/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-es/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "Grupos de archivos", "objectManagement.databaseProperties.filegrowthLimitError": "El crecimiento del archivo no puede ser mayor que el tamaño máximo de archivo de un archivo", "objectManagement.databaseProperties.filesText": "Archivos", - "objectManagement.optionsSectionHeader": "Archivos", + "objectManagement.filesSectionHeader": "Archivos", "objectManagement.databaseProperties.filestreamFilesText": "Archivos de secuencia de archivos", "objectManagement.filterSectionTitle": "Filtros", "objectManagement.findText": "Buscar", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "Modo de operación (real)", "objectManagement.databaseProperties.requestedOperationModeText": "Modo de operación (solicitado)", "objectManagement.optimizeAdHocWorkloadsLabel": "Optimizar cargas de trabajo ad hoc", + "objectManagement.optionsSectionHeader": "Opciones", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "Nombre de archivo original", "objectManagement.overwriteExistingBackups": "Sobrescribir todos los conjuntos de copia de seguridad existentes", "objectManagement.backupOverwriteMedia": "Sobrescribir medios", diff --git a/i18n/ads-language-pack-es/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-es/translations/extensions/Microsoft.notebook.i18n.json index a322dfecada0..a630d0c67316 100644 --- a/i18n/ads-language-pack-es/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-es/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "Examinar", - "configurePython.installationType": "Tipo de instalación", - "configurePython.newInstall": "Nueva instalación de Python", "configurePythyon.noVersionsFound": "No se ha encontrado ninguna versión de Python compatible.", "configurePython.descriptionWithoutKernel": "Los kernel del cuaderno requieren que se configure un entorno de ejecución de Python y que se instalen dependencias.", - "configurePython.locationTextBoxText": "Ubicación de la instalación de Python", - "configurePython.pythonConfigured": "El entorno de ejecución de Python se ha configurado.", + "configurePython.locationTextBoxText": "Ubicación de Python", "configurePython.selectFileLabel": "Seleccionar", "configurePython.descriptionWithKernel": "El kernel de \"{0}\" requiere que se configure un entorno de ejecución de Python y que se instalen dependencias.", - "configurePython.existingInstall": "Usar la instalación de Python existente", + "configurePythyon.existingInstance": "{0} (Instancia de Python actual)", "configurePythyon.customPathLabel": "{0} (personalizada)", - "configurePythyon.defaultPathLabel": "{0} (predeterminada)", "configurePythyon.dropdownPathLabel": "{0} ({1} de Python)" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "Se requiere una ruta de acceso del cuaderno" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "Las sesiones del cuaderno de Python activas se cerrarán para poder actualizarse. ¿Desea continuar ahora?", "msgWaitingForInstall": "Otra instalación de Python está actualmente en curso. Esperando a que se complete.", - "msgPythonRunningError": "No se puede sobrescribir una instalación de Python existente mientras Python se está ejecutando. Cierre los cuadernos activos antes de continuar.", - "dontAskAgain": "No volver a preguntar", - "msgDownloadPython": "Descargando Python local para la plataforma: {0} a {1}", - "msgPythonDownloadPending": "Descargando paquete de Python", "msgGetPythonUserDirFailed": "Se ha encontrado un error al obtener la ruta de acceso del usuario de Python: {0}", "msgPackageRetrievalFailed": "Se ha encontrado un error al intentar recuperar la lista de paquetes instalados: {0}", - "msgPythonDirectoryError": "Error al crear el directorio de instalación de Python", - "msgPythonDownloadError": "Error al descargar la configuración de Python", - "msgPythonUnpackError": "Error al desempaquetar el paquete de Python", "msgTaskName": "Instalando dependencias de Notebook", "msgDependenciesInstallationFailed": "Error al instalar las dependencias de Notebook: {0}", "msgInstallPkgStart": "Instalando dependencias de Notebook, consulte la vista Tareas para obtener más información", - "no": "No", "msgInstallPkgFinish": "La instalación de las dependencias de Notebook se ha completado", - "msgInstallPkgProgress": "La instalación de dependencias de Notebook está en curso", - "msgPythonDownloadComplete": "La descarga de Python está completa", - "msgPythonVersionUpdatePrompt": "Python {0} ya está disponible en Azure Data Studio. La versión actual de Python (3.6.6) dejará de recibir soporte en diciembre de 2021. ¿Le gustaría actualizar a Python {0} ahora?", - "msgPythonVersionUpdateWarning": "Se instalará Python {0} y reemplazará a Python 3.6.6. Es posible que algunos paquetes ya no sean compatibles con la nueva versión o que sea necesario volver a instalarlos. Se creará un cuaderno para ayudarle a reinstalar todos los paquetes de PIP. ¿Desea continuar con la actualización ahora?", - "msgPythonUnpackPending": "Desempaquetando paquete de Python", - "yes": "Sí" + "msgInstallPkgProgress": "La instalación de dependencias de Notebook está en curso" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "Error en el apagado del servidor de Notebook: {0}" diff --git a/i18n/ads-language-pack-es/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-es/translations/extensions/Microsoft.sql-migration.i18n.json index 5076e26d275c..f6f3b530b095 100644 --- a/i18n/ads-language-pack-es/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-es/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "La transición de SQL Managed Instance para el nivel de servicio crítico para la empresa puede tardar mucho más que De uso general, ya que deben inicializarse tres réplicas secundarias para el grupo de alta disponibilidad Always On. La duración de la operación depende del tamaño de los datos. La velocidad de inicio en el 90% de los casos es de 220 GB/hora o superior.", "sql.migration.dashboard.help.description.dmsGuide": "Sitio central de artículos de migración que proporciona instrucciones paso a paso para migrar y modernizar sus recursos de datos en Azure.", "sql.migration.resource.group.description": "Un grupo de recursos es un contenedor que tiene los recursos relacionados de una solución de Azure.", + "sql.migration.target.provisioning.template.display.limit": "Una sola plantilla de ARM tiene una limitación de implementación de un máximo de 50 bases de datos de Azure SQL. La plantilla de las primeras 50 bases de datos se muestra a continuación. Para ver todas las plantillas, guarde el archivo JSON de plantilla en un almacenamiento local o en Azure Blob Storage.", "sql.migration.pre.req.2": "Una(s) base(s) de datos SQL Server de origen que se ejecuta(n) localmente, o en SQL Server en Azure Virtual Machine o en cualquier máquina virtual que se ejecute en la nube (privada, pública).", "sql.migration.dashboard.help.description.sqldb": "Tutorial paso a paso para migrar bases de datos de una instancia de SQL Server (local o de Azure Virtual Machines) a Azure SQL Database.", "sql.migration.dashboard.help.description.mi": "Tutorial paso a paso para migrar bases de datos de una instancia de SQL Server (local o de Azure Virtual Machines) a Azure SQL Managed Instance con un tiempo de inactividad mínimo.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "Todas las copias de seguridad restauradas", "sql.migration.view.all": "Todas las migraciones de bases de datos", "sql.migration.all.fields.required": "Todos los campos son obligatorios.", + "sql.ir.version.mismatch": "Todos los nodos deben estar en la misma versión que se va a configurar", "sql.migration.all.source.tables.empty": "Todas las tablas de origen están vacías. No hay ninguna tabla disponible para seleccionar para la migración de datos. Pero están disponibles para la migración de esquemas si no existen en el destino.", "sql.migration.unavailable.source.tables.heading": "Todas las tablas siguientes están vacías. No hay ninguna tabla disponible para seleccionar para la migración de datos. Pero si no existen en el destino, la migración del esquema está disponible.", "sql.migration.missing.tables.heading": "Faltan todas las tablas siguientes en el destino. Para migrar los datos de estas tablas, seleccione la opción migrar esquema anterior.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "¿Seguro de que desea cancelar la migración?", "sql.delete.migration.confirmation": "¿Está seguro de que desea eliminar esta migración?", "sql.migration.migration.list.ascending.label": "Ascendente", - "sql.migration.database.assessment.xevents.title": "Evaluar sesiones de eventos extendidos", + "sql.migration.database.assessment.xevents.title": "Evaluar SQL ad hoc o dinámico", "sql.migration.assessed.dbs.label": "Bases de datos evaluadas: {0}", "sql.migration.assessment.findings.label": "Resultados de la evaluación", "sql.migration.assessment.in.progress": "Evaluación en curso", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Azure Database Migration Service", "sql.migration.service.ready": "Azure Database Migration Service \"{0}\" está conectado a un entorno de ejecución de integración autohospedado que se ejecuta en nodos: {1}\r\n\r\nPara mejorar el rendimiento y la alta disponibilidad, puede registrar nodos adicionales.", "sql.migration.service.ready.below": "Azure Database Migration Service \"{0}\" está conectado a un entorno de ejecución de integración autohospedado que se ejecuta en nodos: {1}\r\n\r\nPara mejorar el rendimiento y la alta disponibilidad, puede registrar nodos adicionales. Consulte la información siguiente para ver las instrucciones de registro.", + "sql.migration.service.ready.without.nodes": "Azure Database Migration Service \"{0}\" está conectado al entorno de ejecución de integración autohospedado que se ejecuta en los siguientes nodos", "sql.migration.service.header": "Detalles de Azure Database Migration Service \"{0}\":`", "sql.migration.service.not.ready": "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.", "sql.migration.service.not.ready.below": "Azure Database Migration Service no está registrado. Azure Database Migration Service \"{0}\" debe registrarse con integration runtime autohospedado en cualquier nodo.\r\n\r\nConsulte a continuación las instrucciones de registro.", + "sql.migration.ir.container.description": "Azure Database Migration Service aprovecha el entorno de ejecución de integración autohospedado de Azure Data Factory para cargar copias de seguridad desde un recurso compartido de archivos de red local en Azure. En función de las selecciones de la página anterior, deberá configurar un entorno de ejecución de integración autohospedado.", "sql.migration.service.container.container.description1": "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).", "sql.migration.services.name": "Nombre de Azure Database Migration Service.", "sql.migration.ir.page.description": "Azure Database Migration Service organiza las actividades de migración de bases de datos y realiza un seguimiento de su progreso. Puede seleccionar un Database Migration Service existente como objetivo de Azure SQL si ya creó uno anteriormente o crear uno nuevo a continuación.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Región de Azure para su servicio de Azure Database Migration Service. Solo se mostrarán las regiones que contienen un servicio.", "sql.migration.services.location": "Región de Azure para su Azure Database Migration Service. Debe ser la misma región que el Azure SQL de destino.", "sql.migration.sku.location": "Región de Azure para el destino de Azure SQL. Solo se mostrarán las regiones que contienen un destino apto para la migración.", + "sql.migration.storage.account.location": "Región de Azure para la cuenta de almacenamiento. Solo se mostrarán las regiones que contengan una cuenta de almacenamiento.", "sql.migration.summary.azure.storage": "Azure Storage", "sql.migration.validate.ir.validation.result.label.storage": "Conectividad de Azure Storage", "sql.migration.summary.azure.storage.subscription": "Suscripción de Azure Storage", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "Tamaño de copia de seguridad (MB)", "sql.migration.backup.start.time": "Hora de inicio de copia de seguridad", "sql.migration.wizard.sku.all": "Según los resultados de la evaluación, las {0} bases de datos en estado de conexión se pueden migrar a Azure SQL.", + "sql.migration.target.provisioning.description": "A continuación, se muestra el script de ARM para la SKU de destino recomendada. Puede guardar el script como plantilla.", "sql.migration.sku.targetStorageConfiguration.info": "A continuación se muestra la configuración de almacenamiento de destino necesaria para satisfacer sus necesidades de rendimiento de almacenamiento.", "sql.migration.blob.container.title": "Contenedor de blobs", "sql.migration.blob.container.label": "Grupo de recursos de contenedor de blobs", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "Haga clic para ver los detalles del error", "sql.migration.service.details.button.label": "Cerrar", "sql.migration.close": "Cerrar", + "sql.migration.target.provisioning.close": "Cerrar", "sql.migration.sku.azureRecommendation.collectData.method": "Recopilar datos de rendimiento ahora", "sql.login.migration.collecting.target.logins.failed": "Error al recopilar el inicio de sesión de destino, con código de error {0}", "sql.migration.status.collectioncompleted": "Recopilación de datos completada", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "Finalizar la transición sin restaurar todas las copias de seguridad puede provocar la pérdida de datos.", "sql.migration.restore.status.completing.migration": "Completando la migración", "sql.migration.save.close.popup": "Configuración guardada. La recopilación de datos de rendimiento seguirá ejecutándose en segundo plano. Puede detener la recopilación cuando desee.", + "sql.migration.configure.ir": "Configuración del entorno de ejecución de integración", + "sql.ir.configure.manually": "Configurar manualmente ", + "sql.ir.configure.powershellscript": "Configuración mediante el script de PowerShell ", "sql.migration.connection.label": "Conectar", "sql.migration.community.support.description": "Conectar con Microsoft Community", "sql.migration.wizard.target.connection.error": "Error de conexión: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "Descripción", "sql.migration.details.title": "Detalles", "sql.migration.details.copied": "Detalles copiados", + "sql.migration.validate.ir.error.message": "Los detalles de {0} son obligatorios; faltan estos detalles.", "sql.migration.field.label.deteected.files": "Archivos detectados", "sql.migration.dashboard.description": "Determine la preparación de la migración de sus instancias de SQL Server, identifique un destino de Azure SQL recomendado y complete la migración de la instancia de SQL Server a Azure SQL Managed Instance, SQL Server en Azure Virtual Machines o Azure SQL Database.", "sql.migration.restore.backuptype.differentialdatabase": "Base de datos diferencial", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "Escriba las credenciales de autenticación de Windows usadas para conectarse a la instancia de SQL Server {0}. Estas credenciales se usarán para conectarse a la instancia de SQL Server e identificar archivos de copia de seguridad válidos.", "sql.migration.source.details.windowAuth.db": "Escriba las credenciales de autenticación de Windows usadas para conectarse a SQL Server instancia {0}. Estas credenciales serán utilizadas para conectarse a la instancia de SQL Server desde el tiempo de ejecución de integración autohospedado.", "sql.migration.enter.your.sql.cred": "Escriba las credenciales para la instancia de SQL Server de origen. Estas credenciales se usarán al migrar las bases de datos a Azure SQL.", + "sql.migration.select.storage.account.heading": "Escriba los detalles siguientes para seleccionar la cuenta de Azure Storage y guardar el script como plantilla.", "sql.migration.services.container.description": "Escriba la información siguiente para agregar una nueva Azure Database Migration Service.", "sql.migration.services.container.description.network": "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.", "sql.migration.sku.parameters.text": "Escriba la información siguiente para editar los parámetros de recomendación.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "Error: Azure SQL Managed Instance admite un máximo de {0} bases de datos de usuario por instancia. Seleccione {0} o menos bases de datos para continuar.", "sql.login.migration.migrate.server.roles.and.set.permissions": "Se completó el establecimiento de asignaciones de usuario.\r\n\r\nActualmente, migrando roles de servidor, estableciendo asignaciones de servidor y estableciendo permisos. Esto tardará algún tiempo.", "sql.login.migration.establish.user.mappings.failed": "Error al establecer asignaciones de usuario", + "sql.ir.powershellscript": "Ejecutar script ", + "sql.ir.executing.powershellscript": "Se inició la ejecución y se supervisa la ventana de PowerShell abierta. ", "sql.migration.support.resources.description": "Explorar la documentación", "sql.migration.tde.wizard.optionads": "Exportar mis certificados y claves privadas al destino.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "Error al migrar los inicios de sesión de {0} a {1} \"{2}\"", "sql.migration.notebook.open.error": "No se pudo abrir el cuaderno de migración.", "sql.migration.dms.provision.failed": "No se pudo aprovisionar el Database Migration Service. Espere unos minutos y vuelva a intentarlo.", + "sql.migration.target.provisioning.save.template.fail": "No se pudo guardar la plantilla de ARM", + "sql.migration.target.provisioning.upload.template.fail": "No se pudo cargar la plantilla de ARM", "sql.migration.tab.button.feedback.description": "Comentarios", "sql.migration.tab.button.feedback.label": "Comentarios", "sql.migration.feedback.issue.title": "Comentarios sobre la experiencia de migración", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "Siga estas instrucciones para configurar un entorno de ejecución de integración autohospedado.", "sql.migration.database.table.selection.description": "Para cada base de datos a continuación, haz clic en Editar para seleccionar las tablas que se migrarán del origen al destino. A continuación, antes de hacer clic en Siguiente, valida la configuración proporcionada haciendo clic en \"Ejecutar validación\".", "sql.migration.sql.vm.page.blob.info": "Para los servidores de destino que ejecutan SQL Server 2014 o inferior, debe almacenar las copias de seguridad de la base de datos en un contenedor de Azure Storage Blob en lugar de cargarlas mediante la opción de recurso compartido de red. Además, debe almacenar los archivos de copia de seguridad como blobs en páginas, ya que los blobs en bloques solo se admiten para destinos que ejecutan SQL Server 2016 o posterior. Más información: {0}", - "sql.migration.database.assessment.xevents.description": "Para las bases de datos seleccionadas, puede proporcionar archivos de sesión de eventos extendidos para evaluar consultas SQL ad hoc o dinámicas, o cualquier instrucción DML iniciada a través de la capa de datos de la aplicación. {0}", + "sql.migration.database.assessment.xevents.description": "Para las bases de datos seleccionadas, puede proporcionar archivos de sesión de eventos extendidos para evaluar consultas SQL ad hoc o dinámicas, o cualquier instrucción DML iniciada a través de la capa de datos de la aplicación.", "sql.migration.full.backup.files": "Archivos de copia de seguridad completos", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "Uso general", + "sql.migration.target.provisioning.generate.template": "Generar plantilla", "sql.migration.status.generatingscript": "Generando script", "sql.migration.status.generatingcompleted": "Generación de script completada", "sql.migration.sku.get.recommendation": "Obtener recomendación de Azure", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "Confirmo que no hay copias de seguridad de registros adicionales para proporcionar y deseo completar la transición.", "sql.migration.tde.wizard.optionadsconfirm": "Doy mi consentimiento para usar mis credenciales para acceder a los certificados.", "sql.migration.tde.wizard.optionmanual": "Ya he migrado mis certificados y claves privadas al destino.", + "sql.ir.local.ir.definition": "Quiero configurar el entorno de ejecución de integración autohospedado en otra máquina Windows que no sea mi equipo local.", "sql.migration.sku.io.memory.requirement": "Requisito de latencia de E/S", + "sql.ir.ip.address": "Dirección IP", + "sql.ir.config.type": "Tipo de configuración de IR", + "sql.ir.ir.version": "Versión de IR", "sql.migration.empty.table.subtext": "Si esperaba ver resultados, compruebe la conexión a la instancia de SQL Server.", "sql.migration.wizard.cancel.reason.others.input.box.note": "Si seleccionó a otros usuarios, escriba una nota breve.", "sql.migration.impact": "Impacto", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "Importar la evaluación a Azure SQL", "sql.migration.sku.import.performance.data": "Importar datos de rendimiento", "sql.migration.sku.import.performance.data.dialog.description": "Importe este archivo de datos desde una carpeta existente, si ya lo ha recopilado mediante Data Migration Assistant.", + "sql.ir.important": "Importante", "sql.migration.database.migration.migration.mode.tool.tip": "En Azure Database Migration Service, puede migrar las bases de datos sin conexión o mientras están en línea. En una migración sin conexión, el tiempo de inactividad de la aplicación se inicia cuando se inicia la migración. Para limitar el tiempo de inactividad al tiempo que se tarda en pasar al nuevo entorno después de la migración, use una migración en línea.", "sql.migration.tde.validation.requirements.message": "Para que la migración del certificado tenga éxito, debe cumplir todos los requisitos que se indican a continuación.\r\n\r\nHaga clic en \"Ejecutar validación\" para comprobar que se cumplen los requisitos.", "sql.migration.copy.status.inprogress": "En curso", @@ -484,6 +506,8 @@ "sql.login.migration.type": "Tipo de inicio de sesión", "sql.migration.sku.logs.iops.requirement": "Requisito de IOPS de registros", "sql.migration.field.label.mi.restore.state": "Estado de restauración de la instancia administrada", + "sql.ir.manual.ir.collapsed": "Configuración manual de IR contraída", + "sql.ir.manual.ir.expanded": "Configuración manual de IR expandida", "sql.migration.map.target.heading": "Asigne las bases de datos de origen seleccionadas a las bases de datos de destino para la migración", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "Serie premium optimizada para memoria", "sql.migration.sku.memory.requirement": "Requisito de memoria", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "Nueva migración", "sql.migration.newSupportRequest": "Nueva solicitud de soporte técnico", "sql.migration.saved.assessment.next": "Siguiente", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "De uso general de próxima generación", "sql.migration.no": "No", "sql.migration.no.sqldatabaseserver.found": "No se encontraron servidores de base de datos de Azure SQL.", "sql.migration.no.sqldatabase.found": "No se encontraron bases de datos Azure SQL.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "No se encontraron problemas para migrar a SQL Server en la máquina virtual de Azure", "sql.migration.no.location.found": "No se han encontrado ubicaciones.", "sql.migration.no.managedInstance.found": "No se han encontrado instancias administradas.", + "sql.ir.no.node.found": "No se encontró ningún nodo", "sql.migration.no.pending.backups": "No hay copias de seguridad pendientes. Haga clic en actualizar para comprobar el estado actual.", "sql.migration.cancel.feedback.no.reason.selected": "No se seleccionó ningún motivo", "sql.migration.wizard.sku.error.noRecommendation": "No hay ninguna recomendación disponible.", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "No se han encontrado suscripciones.", "sql.migration.select.target.label": "No se seleccionó ningún destino. Seleccione el destino para ver el resumen de la evaluación.", "sql.migration.no.virtualMachine.found": "No se encontró ninguna máquina virtual.", + "sql.ir.node.name": "Nombre del nodo", "sql.migration.restore.status.none": "Ninguno", "sql.migration.restore.backupset.status.none": "Ninguno", "sql.migration.parallel.copy.type.none": "Ninguno", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "No está listo", "sql.migration.restore.status.not.started": "No iniciado", "sql.login.migration.steps.not.started": "No iniciado", + "sql.ir.recommended.link": "Nota: Consulte las recomendaciones de IR autohospedado", "sql.migration.backup.file.number.of.stripes": "Número de franjas", "sql.migration.offline.caps": "DESCONECTADO", "sql.migration.ok": "Aceptar", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "Objetos recopilados", "sql.migration.offline": "Sin conexión", "sql.migration.database.migration.mode.offline.label": "Migración sin conexión", + "sql.ir.powershellscript.definition": "Una vez ejecutado en PowerShell, el script único que se muestra a continuación se descargará, se instalará el entorno de ejecución de integración autohospedado y se registrará con Azure Database Migration Service. Deberá tener PowerShell instalado en la máquina de destino.", "sql.migration.online": "En línea", "sql.migration.database.migration.mode.online.label": "Migración en línea", "sql.migration.open": "Abrir", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "Seleccione la ubicación de los archivos de copia de seguridad de la base de datos antes de continuar.", "sql.migration.cancel.feedback.reason.container.description": "Dedique un momento a indicarnos el motivo de la cancelación de la migración. Esto nos ayudará a mejorar la experiencia.", "sql.migration.port.label": "Puerto", + "sql.ir.powershell.script.saved": "Script de PowerShell guardado", + "sql.ir.ps.script.collapsed": "Script de PowerShell contraído", + "sql.ir.ps.script.expanded": "Script de PowerShell expandido", "sql.migration.status.prefetchobjects": "Captura previa de objetos", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "SSD prémium", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "SSD prémium v2", "sql.migration.sku.azureConfiguration.premiumSeries": "Serie Prémium", "sql.migration.copy.status.preparingforcopy": "Preparando", + "sql.ir.powershell.prereq": "Requisito previo: necesita PowerShell con privilegios de ejecución como administrador. ", "sql.login.migration.status.page.previous.button.title": "Anterior (deshabilitado)", "sql.migration.tde.migrate.results.heading.previous": "Resultados anteriores de la migración de certificados:", "sql.migration.provide.unique.containers": "Proporcione un contenedor único para cada base de datos de destino. Bases de datos afectadas: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "Error al actualizar la lista de inicio de sesión desde el destino", "sql.login.migration.refresh.login.data.successful": "La actualización de la lista de inicio de sesión se realizó correctamente. Se encontraron inicios de sesión de origen {0}, inicios de sesión de destino encontrados {1}", "sql.migration.resourceGroups": "Grupo de recursos", + "sql.migration.storage.account.resource.group.label": "Grupo de recursos", "sql.migration.rg.created": "Grupo de recursos creado", "sql.migration.services.resource.group": "Grupo de recursos para su Azure Database Migration Service.", "sql.migration.dms.resource_group": "Grupo de recursos para el destino de Azure SQL. Solo se mostrarán los grupos de recursos que contienen un servicio.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "Archivos de registro de SQL", "sql.migration.sql.assessment.notebook.title": "Evaluación de la migración de SQL", "sql.migration.sku.sql.temp": "Tempdb de SQL", + "sql.migration.target.provisioning.save": "Guardar", + "sql.migration.target.provisioning.title": "Guardar plantilla", "sql.migration.save.close": "Guardar y cerrar", "sql.migration.save.assessment.report": "Guardar informe de la valoración", "sql.migration.save.recommendation.report": "Guardar informe de recomendaciones", + "sql.ir.save.script": "Guardar script", + "sql.migration.target.upload.to.azure": "Guardar contenedor de blobs de Azure", "sql.migration.saved.assessment.result": "Sesión guardada", "sql.migration.sku.parameters.scale.factor": "Factor de escala:", "sql.migration.schema.data": "Esquema y datos", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "Buscando copias de seguridad", "sql.migration.wizard.troubleshooting": "Consulte el vínculo para obtener más pasos de solución de problemas: https://aka.ms/dms-migrations-troubleshooting.", "sql.migration.select": "Seleccionar", + "sql.migration.select.storage.account.title": "Seleccionar cuenta de Azure Storage", "sql.migration.select.service.title": "Seleccionar Database Migration Service", "sql.migration.select.service.prompt": "Seleccionar Database Migration Service", "sql.migration.select.service.select.a.service": "Seleccionar Database Migration Service", "sql.migration.invalid.migration.service.offline.error": "Seleccione un Database Migration Service que esté conectado a un nodo.", "sql.migration.status.select.service.MESSAGE": "Seleccionar Database Migration Service para supervisar las migraciones.", + "sql.migration.select.storage.select.a.storage.account": "Seleccionar una cuenta de almacenamiento", "sql.migration.blob.container.select": "Seleccione primero un valor de contenedor de blobs.", "sql.migration.sku.import.performance.data.dialog.open.folder": "Seleccionar una carpeta", "sql.migration.sku.import.performance.data.dialog.helper.message": "Seleccione una carpeta en la unidad local", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "Detener validación", "sql.migration.sku.azureRecommendation.stop.popup": "Deteniendo la recopilación de datos de rendimiento...", "sql.migration.sku.targetStorageConfiguration.storage": "Almacenamiento", - "sql.migration.storage.account": "Cuenta de almacenamiento", + "sql.migration.select.storage.account.label": "Cuenta de almacenamiento", + "sql.migration.storage.account.details.label": "Cuenta de almacenamiento", "sql.migration.network.share.azure.header": "Detalles de la cuenta de almacenamiento", "sql.migration.subscription": "Suscripción", "sql.migration.blob.storage.subscription.label": "Suscripción", "sql.migration.dms.subscription": "Nombre de suscripción para su servicio de Azure Database Migration Service.", "sql.migration.services.subscription": "Nombre de suscripción para su Azure Database Migration Service.", "sql.migration.sku.subscription": "Nombre de la suscripción para su destino de Azure SQL", + "sql.migration.storage.account.subscription": "Nombre de suscripción de la cuenta de almacenamiento", "sql.migration.state.succeeded": "Correcto", "sql.migration.tde.validation.status.succeeded": "Correcto", "sql.migration.copy.status.succeeded": "Correcto", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "Tipo de destino", "sql.migration.username.label": "Nombre de usuario de destino", "sql.migration.target.version": "Versión de destino", + "sql.migration.target.provisioning.save.template.success": "La plantilla se guardó correctamente", + "sql.migration.target.provisioning.upload.template.success": "Plantilla cargada correctamente", "sql.migration.test.connection": "Conexión de prueba", "sql.migration.dashboard.help.description.migrateUsingADS": "La extensión de migración de Azure SQL para Azure Data Studio proporciona funcionalidades para evaluar, obtener recomendaciones de Azure del tamaño adecuado y migrar bases de datos de SQL Server a Azure.", "sql.migration.sqldb.not.ready": "El servidor de SQL Database \"{0}\" no está disponible para la migración porque actualmente se encuentra en el estado \"{1}\". Para continuar, seleccione un servidor de base de datos SQL disponible.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "Cargando copias de seguridad de registros", "sql.migration.sqldb.column.usedparallelcopies": "Copias en paralelo utilizadas", "sql.migration.path.user.account": "Cuenta de usuario", + "sql.migration.network.share.user.account.label": "Cuenta de usuario", "sql.migration.username": "Nombre de usuario", + "sql.migration.database.assessment.qds.label": "Utilizando el Almacén de datos de consultas (esta opción está disponible para Microsoft SQL Server 2016 y versiones posteriores)", + "sql.migration.database.assessment.xevents.label": "Utilizando la sesión de eventos extendidos", "sql.migration.starting.login": "Validación y migración de inicios de sesión en curso", "sql.login.migration.establish.user.mappings": "Se completó la validación y migración de inicios de sesión.\r\n\r\nEstableciendo asignaciones de usuario.", "sql.migration.starting.login.failed": "Error al validar y migrar inicios de sesión", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "Hemos ejecutado los pasos siguientes:", "sql.login.migration.wizard.target.data.migration.warning": "Se recomienda migrar las bases de datos al destino Azure SQL antes de iniciar la migración de inicio de sesión para evitar errores en el proceso. No obstante, puede ejecutar este proceso de migración siempre que quiera si su objetivo es actualizar la asignación de usuarios para las bases de datos migradas recientemente.\r\n\r\n Si los nombres de origen y de base de datos no son iguales, es posible que algunos permisos no se apliquen correctamente.", "sql.migration.blob.storage.folder.info": "Al cargar copias de seguridad de bases de datos en el contenedor de blobs, asegúrese de que los archivos de copia de seguridad de diferentes bases de datos se almacenan en carpetas independientes. Solo se admite la raíz del contenedor y las carpetas con un nivel máximo de profundidad.", + "sql.ir.local.ir.setup.note": "Al hacer clic en \"Ejecutar script\", el siguiente script de PowerShell descargará automáticamente el software del entorno de ejecución de integración autohospedado, lo instalará y lo registrará con su Azure Database Migration Service. Para comprobar el estado de conexión del entorno de ejecución de integración, vuelva a la pantalla anterior y actualice. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "¿Dónde desea guardar los datos recopilados?", "sql.migration.network.share.windows.user.label": "Cuenta de usuario de Windows con acceso de lectura a la ubicación del recurso compartido de red", "sql.migration.network.share.windows.user.info": "Cuenta de usuario de Windows con acceso de lectura a la ubicación del recurso compartido de red.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Nombre del recurso de Azure Database Migration Service", "sql.migration.sku.resource": "Nombre del recurso de destino de Azure SQL", "sql.migration.sku.resource.port": "Nombre del puerto del recurso de destino de Azure SQL: 0 - 65535", + "sql.migration.storage.account.blob.container": "Nombre del contenedor de blobs", + "sql.migration.storage.account": "Nombre de la cuenta de almacenamiento", "sql.migration.pre.req.4": "Los detalles de la ubicación de la copia de seguridad de la base de datos, ya sea un recurso compartido de archivos de red o un contenedor de Azure Blob Storage (no es necesario para los destinos de Azure SQL Database).", "sql.migration.wizard.sku.assessment.error.detail": "[No hay resultados de evaluación para validar la preparación de la migración de la base de datos. Al activar esta casilla, confirma que quiere continuar migrando la base de datos al destino de Azure SQL deseado.]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-fr/CHANGELOG.md b/i18n/ads-language-pack-fr/CHANGELOG.md index ed69c8d61278..24a9614e3d8a 100644 --- a/i18n/ads-language-pack-fr/CHANGELOG.md +++ b/i18n/ads-language-pack-fr/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-fr" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-fr/package.json b/i18n/ads-language-pack-fr/package.json index 9644a2984547..3a5f03aad5fe 100644 --- a/i18n/ads-language-pack-fr/package.json +++ b/i18n/ads-language-pack-fr/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-fr", "displayName": "French Language Pack for Azure Data Studio", "description": "Language pack extension for French", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.cms.i18n.json b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.cms.i18n.json index 11c5b470aeec..2d36b77eb9b5 100644 --- a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.cms.i18n.json +++ b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.cms.i18n.json @@ -133,7 +133,7 @@ "cms.connectionOptions.enclaveAttestationProtocol.description": "Spécifie un protocole pour attester une enclave côté serveur utilisée avec Always Encrypted avec des enclaves sécurisées", "cms.connectionOptions.enclaveAttestationUrl.description": "Spécifie un point de terminaison pour attester une enclave côté serveur utilisée avec Always Encrypted avec des enclaves sécurisées", "cms.connectionOptions.authType.description": "Spécifie la méthode d'authentification avec SQL Server", - "cms.connectionOptions.encrypt.categoryValues.strict": "Strict (supported for SQL Server 2022 and Azure SQL)", + "cms.connectionOptions.encrypt.categoryValues.strict": "Strict (pris en charge pour SQL Server 2022 et Azure SQL)", "cms.description": "Prise en charge de la gestion des serveurs de gestion centralisée SQL Server", "cms.connectionOptions.currentLanguage.description": "Nom d'enregistrement de la langue de SQL Server", "cms.connectionOptions.commandTimeout.description": "La durée (en secondes) d’attente de l’exécution d’une commande avant de mettre fin à la tentative et de générer une erreur.", diff --git a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.mssql.i18n.json index 8ac63fa128d1..f914832911a4 100644 --- a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "Groupes de fichiers", "objectManagement.databaseProperties.filegrowthLimitError": "La croissance du fichier ne peut pas être supérieure à la taille maximale d'un fichier.", "objectManagement.databaseProperties.filesText": "Fichiers", - "objectManagement.optionsSectionHeader": "Fichiers", + "objectManagement.filesSectionHeader": "Fichiers", "objectManagement.databaseProperties.filestreamFilesText": "Fichiers filestream", "objectManagement.filterSectionTitle": "Filtres", "objectManagement.findText": "Rechercher", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "Mode d’opération (réel)", "objectManagement.databaseProperties.requestedOperationModeText": "Mode d’opération (demandé)", "objectManagement.optimizeAdHocWorkloadsLabel": "Optimiser les charges de travail ad hoc", + "objectManagement.optionsSectionHeader": "Options", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "Nom de fichier d'origine", "objectManagement.overwriteExistingBackups": "Remplacer tous les jeux de sauvegarde existants", "objectManagement.backupOverwriteMedia": "Remplacez le support", @@ -678,7 +679,7 @@ "mssql.connectionOptions.enclaveAttestationUrl.description": "Spécifie un point de terminaison pour attester une enclave côté serveur utilisée avec Always Encrypted avec des enclaves sécurisées", "mssql.connectionOptions.authType.description": "Spécifie la méthode d'authentification avec SQL Server", "databasesListProperties.status": "État", - "mssql.connectionOptions.encrypt.categoryValues.strict": "Strict (supported for SQL Server 2022 and Azure SQL)", + "mssql.connectionOptions.encrypt.categoryValues.strict": "Strict (pris en charge pour SQL Server 2022 et Azure SQL)", "mssql.connectionOptions.currentLanguage.description": "Nom d'enregistrement de la langue de SQL Server", "mssql.executionPlan.expensiveOperationMetric": "Métrique par défaut à utiliser pour mettre en évidence une opération coûteuse dans les plans d’exécution de requêtes", "mssql.connectionOptions.commandTimeout.description": "La durée (en secondes) d’attente de l’exécution d’une commande avant de mettre fin à la tentative et de générer une erreur.", diff --git a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.notebook.i18n.json index fc3a115481e9..6bb659a66647 100644 --- a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "Parcourir", - "configurePython.installationType": "Type d'installation", - "configurePython.newInstall": "Nouvelle installation de Python", "configurePythyon.noVersionsFound": "Aucune version de Python prise en charge.", "configurePython.descriptionWithoutKernel": "Les noyaux de notebook nécessitent la configuration d'un runtime Python et l'installation de dépendances.", - "configurePython.locationTextBoxText": "Emplacement d'installation de Python", - "configurePython.pythonConfigured": "Runtime python configuré !", + "configurePython.locationTextBoxText": "Emplacement Python", "configurePython.selectFileLabel": "Sélectionner", "configurePython.descriptionWithKernel": "Le noyau ’{0}’ nécessite la configuration d'un runtime Python et l'installation de dépendances.", - "configurePython.existingInstall": "Utiliser l'installation existante de Python", + "configurePythyon.existingInstance": "{0} (instance Python actuelle)", "configurePythyon.customPathLabel": "{0} (Personnalisé)", - "configurePythyon.defaultPathLabel": "{0} (Par défaut)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "Le chemin du notebook est obligatoire" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "Les sessions de bloc-notes python actives seront arrêtées pour permettre la mise à jour. Voulez-vous continuer maintenant ?", "msgWaitingForInstall": "Une autre installation de Python est actuellement en cours. En attente de la fin de l'installation.", - "msgPythonRunningError": "Impossible de remplacer une installation Python existante quand Python est en cours d'exécution. Fermez tous les notebooks actifs avant de continuer.", - "dontAskAgain": "Ne plus me poser la question", - "msgDownloadPython": "Téléchargement de la version locale de Python pour la plateforme : {0} dans {1}", - "msgPythonDownloadPending": "Téléchargement du package Python", "msgGetPythonUserDirFailed": "Erreur pendant l'obtention du chemin de l'utilisateur Python : {0}", "msgPackageRetrievalFailed": "Erreur pendant la tentative de récupération de la liste des packages installés : {0}", - "msgPythonDirectoryError": "Erreur de création du répertoire d'installation de Python", - "msgPythonDownloadError": "Erreur de téléchargement du programme d'installation de Python", - "msgPythonUnpackError": "Erreur de décompression du bundle Python", "msgTaskName": "Installation des dépendances de notebook", "msgDependenciesInstallationFailed": "L'installation des dépendances de notebook a échoué avec l'erreur : {0}", "msgInstallPkgStart": "Installation des dépendances de notebook, consultez la vue Tâches pour plus d'informations", - "no": "Non", "msgInstallPkgFinish": "L'installation des dépendances de notebook est terminée", - "msgInstallPkgProgress": "L'installation des dépendances de notebook est en cours", - "msgPythonDownloadComplete": "Le téléchargement de Python est terminé", - "msgPythonVersionUpdatePrompt": "Python {0} est désormais disponible dans Azure Data Studio. La version actuelle de Python (3.6.6) n’est plus prise en charge en décembre 2021. Voulez-vous effectuer une mise à jour vers python {0} maintenant ?", - "msgPythonVersionUpdateWarning": "Python {0} sera installé et va remplacer python 3.6.6. Certains packages ne sont peut-être plus compatibles avec la nouvelle version ou doivent peut-être être réinstallés. Un bloc-notes va être créé pour vous aider à réinstaller tous les packages PIP. Voulez-vous continuer la mise à jour maintenant ?", - "msgPythonUnpackPending": "Décompression du package Python", - "yes": "Oui" + "msgInstallPkgProgress": "L'installation des dépendances de notebook est en cours" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "L'arrêt du serveur de notebook a échoué : {0}" diff --git a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.sql-migration.i18n.json index 37248577dc38..bae7b7ee1fd7 100644 --- a/i18n/ads-language-pack-fr/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-fr/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "Un basculement de la migration des SQL Managed Instances pour le niveau de service critique pour l'entreprise peut prendre beaucoup plus de temps que pour le niveau de service général, car trois répliques secondaires doivent être alimentées pour le groupe de haute disponibilité Always On. La durée de cette opération dépend de la taille des données. Dans 90 % des cas, la vitesse d'alimentation est de 220 Go/heure ou plus.", "sql.migration.dashboard.help.description.dmsGuide": "Hub d’articles de migration qui fournit des conseils détaillés sur la migration et la modernisation de vos ressources de données dans Azure.", "sql.migration.resource.group.description": "Un groupe de ressources est un conteneur qui inclut les ressources associées à une solution Azure.", + "sql.migration.target.provisioning.template.display.limit": "Un modèle ARM unique a une limite de déploiement de 50 bases de données Azure SQL maximum. Le modèle des 50 premières bases de données est affiché ci-dessous. Pour afficher tous les modèles, enregistrez le fichier JSON de modèle dans un stockage local ou un stockage Blob Azure.", "sql.migration.pre.req.2": "Une ou plusieurs bases de données SQL Server sources s’exécutant localement ou sur SQL Server sur une machine virtuelle Azure ou une machine virtuelle exécutée dans le cloud (privé, public).", "sql.migration.dashboard.help.description.sqldb": "Un didacticiel pas à pas pour migrer des bases de données d'une instance SQL Server (sur site ou Azure Virtual Machines) vers Azure SQL Database.", "sql.migration.dashboard.help.description.mi": "Didacticiel pas à pas permettant de migrer des bases de données d’une instance de SQL Server (machines virtuelles locales ou Azure) vers Azure SQL Managed Instance avec un temps d’arrêt minimal.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "Toutes les sauvegardes ont été restaurées.", "sql.migration.view.all": "Toutes les migrations de base de données", "sql.migration.all.fields.required": "Tous les champs sont requis.", + "sql.ir.version.mismatch": "Tous les nœuds doivent être sur la même version pour être configurés", "sql.migration.all.source.tables.empty": "Toutes les tables sources sont vides. Aucune table n’est disponible pour la migration des données. Mais ils sont disponibles pour la migration de schéma s’ils n’existent pas sur la cible.", "sql.migration.unavailable.source.tables.heading": "Toutes les tables ci-dessous sont vides. Aucune table n’est disponible pour la migration des données. Mais s’ils n’existent pas sur la cible, la migration de schéma est disponible.", "sql.migration.missing.tables.heading": "Toutes les tables ci-dessous sont manquantes dans la cible. Pour migrer les données de ces tables, sélectionnez l’option Migrer le schéma ci-dessus.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "Voulez-vous vraiment annuler cette migration ?", "sql.delete.migration.confirmation": "Voulez-vous vraiment supprimer cette migration ?", "sql.migration.migration.list.ascending.label": "Ordre croissant", - "sql.migration.database.assessment.xevents.title": "Évaluer les sessions d’événements étendues", + "sql.migration.database.assessment.xevents.title": "Évaluer SQL ad hoc ou dynamique", "sql.migration.assessed.dbs.label": "Bases de données évaluées : {0}", "sql.migration.assessment.findings.label": "Résultats de l’évaluation", "sql.migration.assessment.in.progress": "Évaluation en cours", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Service Azure Database Migration", "sql.migration.service.ready": "Azure Database Migration Service '{0}' est connecté au runtime d’intégration autohébergé exécuté sur le ou les nœuds - {1}\r\n\r\nPour améliorer les performances et la haute disponibilité, vous pouvez inscrire des nœuds supplémentaires.", "sql.migration.service.ready.below": "Azure Database Migration Service « {0} » est connecté au runtime d’intégration auto-hébergé exécuté sur le ou les nœuds : {1}\r\n\r\nPour une performance améliorée et une disponibilité élevée, vous pouvez inscrire des nœuds supplémentaires. Voir ci-dessous pour les instructions d’inscription.", + "sql.migration.service.ready.without.nodes": "Azure Database Migration Service « {0} » est connecté au runtime d'intégration auto-hébergé exécuté sur le(s) nœud(s) suivant(s)", "sql.migration.service.header": "Détails Azure Database Migration Service « {0} » :", "sql.migration.service.not.ready": "Azure Database Migration Service n’est pas inscrit. Azure Database Migration Service « {0} » doit être inscrit auprès d’un runtime d'intégration auto-hébergé sur n’importe quel nœud.", "sql.migration.service.not.ready.below": "Azure Database Migration Service n’est pas inscrit. Azure Database Migration Service « {0} » doit être inscrit auprès d’un runtime d'intégration auto-hébergé sur n’importe quel nœud.\r\n\r\nVoir ci-dessous pour les instructions d’inscription.", + "sql.migration.ir.container.description": "Azure Database Migration Service exploite Microsoft Integration Runtime d’Azure Data Factory pour télécharger des sauvegardes depuis le partage de fichiers réseau sur site vers Azure. Sur la base des sélections de la page précédente, vous devrez configurer Microsoft Integration Runtime.", "sql.migration.service.container.container.description1": "Azure Database Migration Service tire parti du runtime d’intégration auto-hébergé de Azure Data Factory pour gérer la connectivité entre la source et la cible, et charger des sauvegardes à partir d’un partage de fichiers réseau local vers Azure (le cas échéant).", "sql.migration.services.name": "Nom de Azure Database Migration Service.", "sql.migration.ir.page.description": "Azure Database Migration Service orchestre les activités de migration de base de données et suit leur progression. Vous pouvez sélectionner un Database Migration Service existant si vous en avez créé un précédemment, ou en créer un nouveau ci-dessous.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Région Azure pour votre Azure Database Migration Service. Seules les régions qui contiennent un service sont affichées.", "sql.migration.services.location": "Région Azure pour votre Azure Database Migration Service. Il doit s’agir de la même région que votre Azure SQL cible.", "sql.migration.sku.location": "Région Azure pour votre cible Azure SQL. Seules les régions qui contiennent une cible éligible pour la migration sont affichées.", + "sql.migration.storage.account.location": "Région Azure pour votre compte de stockage. Seules les régions qui contiennent un compte de stockage sont affichées.", "sql.migration.summary.azure.storage": "Stockage Azure", "sql.migration.validate.ir.validation.result.label.storage": "Connectivité du stockage Azure", "sql.migration.summary.azure.storage.subscription": "Abonnement au stockage Azure", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "Taille de sauvegarde (Mo)", "sql.migration.backup.start.time": "Heure de début de la sauvegarde", "sql.migration.wizard.sku.all": "En fonction des résultats de l’évaluation, toutes les {0} de vos bases de données dans un état en ligne peuvent être migrées vers Azure SQL.", + "sql.migration.target.provisioning.description": "Vous trouverez ci-dessous le script ARM pour la référence SKU cible recommandée. Vous pouvez enregistrer le script en tant que modèle.", "sql.migration.sku.targetStorageConfiguration.info": "Vous trouverez ci-dessous la configuration de stockage cible requise pour répondre à vos besoins en termes de performances de stockage.", "sql.migration.blob.container.title": "Conteneur d'objets blob", "sql.migration.blob.container.label": "Groupe de ressources du conteneur d’objets BLOB", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "Cliquez pour voir les détails de l'erreur", "sql.migration.service.details.button.label": "Fermer", "sql.migration.close": "Fermer", + "sql.migration.target.provisioning.close": "Fermer", "sql.migration.sku.azureRecommendation.collectData.method": "Collectez les données de performance maintenant", "sql.login.migration.collecting.target.logins.failed": "Échec de la collecte de la connexion cible avec le code d’erreur {0}", "sql.migration.status.collectioncompleted": "Collection terminée", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "L’exécution du basculement sans restaurer toutes les sauvegardes peut entraîner une perte de données.", "sql.migration.restore.status.completing.migration": "Exécution de la migration", "sql.migration.save.close.popup": "Configuration enregistrée. La collecte des données de performances continuera de s’exécuter en arrière-plan. Vous pouvez arrêter la collecte quand vous le souhaitez.", + "sql.migration.configure.ir": "Configurer Microsoft Integration Runtime", + "sql.ir.configure.manually": "Configurer manuellement ", + "sql.ir.configure.powershellscript": "Configurer à l’aide d’un script PowerShell ", "sql.migration.connection.label": "Connecter", "sql.migration.community.support.description": "Se connecter à la communauté Microsoft", "sql.migration.wizard.target.connection.error": "Erreur de connexion : {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "Description", "sql.migration.details.title": "Détails", "sql.migration.details.copied": "Détails copiés", + "sql.migration.validate.ir.error.message": "Les détails des {0} sont obligatoires et manquants.", "sql.migration.field.label.deteected.files": "Fichiers détectés", "sql.migration.dashboard.description": "Déterminez la préparation de la migration de vos instances de SQL Server, identifiez une cible de Azure SQL recommandée et terminez la migration de votre instance de SQL Server vers Azure SQL Managed Instance, SQL Server sur des machines virtuelles Azure ou Azure SQL Database.", "sql.migration.restore.backuptype.differentialdatabase": "Base de données différentielle", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "Entrez les informations d’identification d’authentification Windows utilisées pour se connecter à SQL Server instance {0}. Ces informations d’identification seront utilisées pour se connecter à l’instance SQL Server et identifier les fichiers de sauvegarde valides.", "sql.migration.source.details.windowAuth.db": "Entrez les informations d'identification d'authentification Windows utilisées pour se connecter à l'instance SQL Server {0}. Ces informations d'identification seront utilisées pour se connecter à l'instance SQL Server à partir du runtime d'intégration auto-hébergé.", "sql.migration.enter.your.sql.cred": "Entrez les informations d’identification de l’instance de SQL Server source. Ces informations d’identification seront utilisées lors de la migration des bases de données vers Azure SQL.", + "sql.migration.select.storage.account.heading": "Entrez les détails ci-dessous pour sélectionner le compte de stockage Azure et enregistrer le script en tant que modèle", "sql.migration.services.container.description": "Entrez les informations ci-dessous pour ajouter une nouvelle Azure Database Migration Service.", "sql.migration.services.container.description.network": "Entrez les informations ci-dessous pour ajouter une nouvelle Azure Database Migration Service. Pour inscrire le runtime d’intégration auto-hébergé, sélectionnez « Mes sauvegardes de base de données se trouvent sur un partage réseau » dans la page précédente.", "sql.migration.sku.parameters.text": "Entrez les informations ci-dessous pour modifier les paramètres de recommandation.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "Erreur : Azure SQL Managed Instance prend en charge un maximum de {0} bases de données utilisateur par instance. Sélectionnez {0} ou moins de bases de données pour continuer.", "sql.login.migration.migrate.server.roles.and.set.permissions": "Établissement des mappages d'utilisateurs terminé.\r\n\r\nActuellement, migration des rôles de serveur, établissement des mappages de serveur et définition des autorisations. Cela prendra un certain temps.", "sql.login.migration.establish.user.mappings.failed": "Échec de l’établissement du mappage d'utilisateur", + "sql.ir.powershellscript": "Exécuter le script ", + "sql.ir.executing.powershellscript": "L’exécution a démarré et surveille la fenêtre PowerShell ouverte. ", "sql.migration.support.resources.description": "Explorer la documentation", "sql.migration.tde.wizard.optionads": "Exportez mes certificats et clés privées vers la cible.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "Échec de la migration des connexions {0} vers {1} « {2} »", "sql.migration.notebook.open.error": "Échec de l’ouverture du bloc-notes de migration.", "sql.migration.dms.provision.failed": "Échec de la mise en service d’un Database Migration Service. Patientez quelques minutes, puis réessayez.", + "sql.migration.target.provisioning.save.template.fail": "Échec de l’enregistrement du modèle ARM", + "sql.migration.target.provisioning.upload.template.fail": "Échec du chargement du modèle ARM", "sql.migration.tab.button.feedback.description": "Commentaires", "sql.migration.tab.button.feedback.label": "Commentaires", "sql.migration.feedback.issue.title": "Commentaires sur l'expérience de la migration", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "Suivez les instructions ci-dessous pour configurer le runtime d’intégration auto-hébergé.", "sql.migration.database.table.selection.description": "Pour chaque base de données ci-dessous, cliquez sur Modifier pour sélectionner les tables à migrer de la source vers la cible. Puis, avant de cliquer sur Next, validez la configuration fournie en cliquant sur 'Run validation'.", "sql.migration.sql.vm.page.blob.info": "Pour les serveurs cibles exécutant SQL Server 2014 ou une version antérieure, vous devez stocker vos sauvegardes de base de données dans un conteneur Azure Storage Blob au lieu de les charger à l’aide de l’option de partage réseau. En outre, vous devez stocker les fichiers de sauvegarde sous forme d’objets blob de pages, car les objets blob de blocs sont pris en charge uniquement pour les cibles qui exécutent SQL Server 2016 ou version ultérieure. En savoir plus : {0}", - "sql.migration.database.assessment.xevents.description": "Pour les bases de données sélectionnées, fournissez éventuellement des fichiers de session d’événements étendus pour évaluer les requêtes SQL ad hoc ou dynamiques, ou les instructions DML lancées via la couche données de l’application. {0}", + "sql.migration.database.assessment.xevents.description": "Pour les bases de données sélectionnées, fournissez éventuellement des fichiers de session d'événements étendus pour évaluer les requêtes SQL ad hoc ou dynamiques ou toute instruction DML initiée via la couche de données d'application.", "sql.migration.full.backup.files": "Fichier(s) de sauvegarde complète", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "Usage général", + "sql.migration.target.provisioning.generate.template": "Générer un modèle", "sql.migration.status.generatingscript": "Génération du script", "sql.migration.status.generatingcompleted": "Génération du script terminée", "sql.migration.sku.get.recommendation": "Obtenir la recommandation Azure", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "Je confirme qu’il n’existe aucune sauvegarde de journal supplémentaire à fournir et que je souhaite effectuer le basculement.", "sql.migration.tde.wizard.optionadsconfirm": "J’accepte d’utiliser mes informations d’identification pour accéder aux certificats.", "sql.migration.tde.wizard.optionmanual": "J'ai déjà migré mes certificats et clés privées vers la cible.", + "sql.ir.local.ir.definition": "Je souhaite configurer le runtime d'intégration auto-hébergé sur une autre machine Windows qui n'est pas ma machine locale.", "sql.migration.sku.io.memory.requirement": "Exigence de latence d’E/S", + "sql.ir.ip.address": "Adresse IP", + "sql.ir.config.type": "Type de configuration IR", + "sql.ir.ir.version": "Version du runtime d’intégration", "sql.migration.empty.table.subtext": "Si des résultats étaient attendus, vérifiez la connexion à l’instance SQL Server.", "sql.migration.wizard.cancel.reason.others.input.box.note": "Si vous en avez sélectionné d’autres, veuillez rédiger une courte note.", "sql.migration.impact": "Impact", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "Importer l’évaluation dans Azure SQL", "sql.migration.sku.import.performance.data": "Importer des données de performances", "sql.migration.sku.import.performance.data.dialog.description": "Importez ce fichier de données à partir d'un dossier existant, si vous l'avez déjà collecté à l'aide de Data Migration Assistant.", + "sql.ir.important": "Important", "sql.migration.database.migration.migration.mode.tool.tip": "Dans Azure Database Migration Service, vous pouvez migrer vos bases de données hors connexion ou lorsqu'elles sont en ligne. Dans une migration hors ligne, le temps d'arrêt de l'application commence au démarrage de la migration. Pour limiter les temps d'arrêt au temps qu'il vous faut pour basculer vers le nouvel environnement après la migration, utilisez une migration en ligne.", "sql.migration.tde.validation.requirements.message": "Pour que la migration des certificats réussisse, vous devez remplir toutes les conditions répertoriées ci-dessous.\r\n\r\nCliquez sur « Exécuter la validation » pour vérifier que les exigences sont remplies.", "sql.migration.copy.status.inprogress": "En cours", @@ -484,6 +506,8 @@ "sql.login.migration.type": "Type de connexion", "sql.migration.sku.logs.iops.requirement": "Exigence IOPS des journaux", "sql.migration.field.label.mi.restore.state": "État de restauration de Managed Instance", + "sql.ir.manual.ir.collapsed": "Configuration du runtime d’intégration manuel réduite", + "sql.ir.manual.ir.expanded": "Configuration IR manuelle étendue", "sql.migration.map.target.heading": "Mapper les bases de données source sélectionnées aux bases de données cible pour la migration", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "Série premium à mémoire optimisée", "sql.migration.sku.memory.requirement": "Mémoire requise", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "Nouvelle migration", "sql.migration.newSupportRequest": "Nouvelle demande de support", "sql.migration.saved.assessment.next": "Suivant", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "La nouvelle génération d’appareils à usage général", "sql.migration.no": "Non", "sql.migration.no.sqldatabaseserver.found": "Aucun serveur de base de données Azure SQL trouvé.", "sql.migration.no.sqldatabase.found": "Aucune base de données Azure SQL trouvée.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Aucun problème trouvé pour la migration vers SQL Server sur une machine virtuelle Azure.", "sql.migration.no.location.found": "Emplacements introuvables.", "sql.migration.no.managedInstance.found": "Aucune instance managée trouvée.", + "sql.ir.no.node.found": "Aucun nœud trouvé", "sql.migration.no.pending.backups": "Aucune sauvegarde en attente. Cliquez sur Actualiser pour vérifier l’état actuel.", "sql.migration.cancel.feedback.no.reason.selected": "Aucune raison sélectionnée", "sql.migration.wizard.sku.error.noRecommendation": "Aucune recommandation disponible", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "Aucun abonnement trouvé.", "sql.migration.select.target.label": "Aucune cible sélectionnée. Sélectionnez la cible pour afficher le résumé de l’évaluation.", "sql.migration.no.virtualMachine.found": "Aucune machine virtuelle trouvée.", + "sql.ir.node.name": "Nom du nœud", "sql.migration.restore.status.none": "Aucun(e)", "sql.migration.restore.backupset.status.none": "Aucun(e)", "sql.migration.parallel.copy.type.none": "Aucun(e)", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "Pas prêt", "sql.migration.restore.status.not.started": "Non démarré", "sql.login.migration.steps.not.started": "Non démarré", + "sql.ir.recommended.link": "Remarque : consulter les recommandations du runtime d’IR auto-hébergé", "sql.migration.backup.file.number.of.stripes": "Nombre de franges", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "OK", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "Objets collectés", "sql.migration.offline": "Hors connexion", "sql.migration.database.migration.mode.offline.label": "Migration hors connexion", + "sql.ir.powershellscript.definition": "Une fois exécuté dans PowerShell, le script unique présenté ci-dessous téléchargera et installera le runtime d'intégration auto-hébergé et l'enregistrera auprès d’Azure Database Migration Service. Vous devrez avoir PowerShell installé sur la machine cible.", "sql.migration.online": "En ligne", "sql.migration.database.migration.mode.online.label": "Migration en ligne", "sql.migration.open": "Ouvrir", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "Veuillez sélectionner l’emplacement de vos fichiers de sauvegarde de base de données avant de continuer.", "sql.migration.cancel.feedback.reason.container.description": "Veuillez prendre un moment pour nous indiquer la raison de l'annulation de la migration. Cela nous aidera à améliorer l’expérience.", "sql.migration.port.label": "Port", + "sql.ir.powershell.script.saved": "Script PowerShell enregistré", + "sql.ir.ps.script.collapsed": "Le script Powershell s'est effondré", + "sql.ir.ps.script.expanded": "Script PowerShell développé", "sql.migration.status.prefetchobjects": "Pré-récupérer des objets", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "SSD Premium", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "SSD Premium v2", "sql.migration.sku.azureConfiguration.premiumSeries": "Série Premium", "sql.migration.copy.status.preparingforcopy": "Préparation", + "sql.ir.powershell.prereq": "Prérequis : Vous avez besoin de PowerShell avec des privilèges d’exécution en tant qu’administrateur. ", "sql.login.migration.status.page.previous.button.title": "Précédent (désactivé)", "sql.migration.tde.migrate.results.heading.previous": "Résultats de la migration des certificats précédents :", "sql.migration.provide.unique.containers": "Spécifiez un conteneur unique pour chaque base de données cible. Bases de données affectées : ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "Échec de l’actualisation de la liste de connexions à partir de la cible", "sql.login.migration.refresh.login.data.successful": "L’actualisation de la liste de connexions a réussi. Connexions sources trouvées {0}, connexions cibles trouvées {1}", "sql.migration.resourceGroups": "Groupe de ressources", + "sql.migration.storage.account.resource.group.label": "Groupe de ressources", "sql.migration.rg.created": "Groupe de ressources créé", "sql.migration.services.resource.group": "Groupe de ressources pour votre Azure Database Migration Service.", "sql.migration.dms.resource_group": "Groupe de ressources pour votre cible Azure SQL. Seuls les groupes de ressources qui contiennent un service sont affichés.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "Fichiers journaux SQL", "sql.migration.sql.assessment.notebook.title": "Évaluation de la migration SQL", "sql.migration.sku.sql.temp": "base de données SQL", + "sql.migration.target.provisioning.save": "Enregistrer", + "sql.migration.target.provisioning.title": "Enregistrer le modèle", "sql.migration.save.close": "Enregistrer et fermer", "sql.migration.save.assessment.report": "Enregistrer le rapport d'évaluation", "sql.migration.save.recommendation.report": "Enregistrer le rapport de recommandation", + "sql.ir.save.script": "Enregistrer le script", + "sql.migration.target.upload.to.azure": "Enregistrer dans un conteneur blob Azure", "sql.migration.saved.assessment.result": "Session enregistrée", "sql.migration.sku.parameters.scale.factor": "Facteur d'échelle", "sql.migration.schema.data": "Schéma et données", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "Recherche des sauvegardes", "sql.migration.wizard.troubleshooting": "Consultez le lien pour plus d’étapes de dépannage : https://aka.ms/dms-migrations-troubleshooting.", "sql.migration.select": "Sélectionner", + "sql.migration.select.storage.account.title": "Sélectionner le compte de stockage Azure", "sql.migration.select.service.title": "Sélectionner Database Migration Service", "sql.migration.select.service.prompt": "Sélectionner un Database Migration Service", "sql.migration.select.service.select.a.service": "Sélectionner un Database Migration Service", "sql.migration.invalid.migration.service.offline.error": "Sélectionnez un Database Migration Service connecté à un nœud.", "sql.migration.status.select.service.MESSAGE": "Sélectionnez un Database Migration Service pour surveiller les migrations.", + "sql.migration.select.storage.select.a.storage.account": "Sélectionner un compte de stockage", "sql.migration.blob.container.select": "Sélectionnez d’abord une valeur de conteneur d’objets Blob.", "sql.migration.sku.import.performance.data.dialog.open.folder": "Sélectionnez un dossier", "sql.migration.sku.import.performance.data.dialog.helper.message": "Sélectionnez un dossier sur votre disque local", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "Arrêter la validation", "sql.migration.sku.azureRecommendation.stop.popup": "Arrêt de la collecte des données de performances...", "sql.migration.sku.targetStorageConfiguration.storage": "Stockage", - "sql.migration.storage.account": "Compte de stockage", + "sql.migration.select.storage.account.label": "Compte de stockage", + "sql.migration.storage.account.details.label": "Compte de stockage", "sql.migration.network.share.azure.header": "Détails du compte de stockage", "sql.migration.subscription": "Abonnement", "sql.migration.blob.storage.subscription.label": "Abonnement", "sql.migration.dms.subscription": "Nom de l’abonnement pour votre Azure Database Migration Service", "sql.migration.services.subscription": "Nom de l’abonnement pour votre Azure Database Migration Service.", "sql.migration.sku.subscription": "Nom de l’abonnement pour votre cible Azure SQL", + "sql.migration.storage.account.subscription": "Nom de l’abonnement pour votre compte de stockage", "sql.migration.state.succeeded": "Réussite", "sql.migration.tde.validation.status.succeeded": "Réussi", "sql.migration.copy.status.succeeded": "Réussite", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "Type de cible", "sql.migration.username.label": "Nom de l'utilisateur cible", "sql.migration.target.version": "Version cible", + "sql.migration.target.provisioning.save.template.success": "Enregistrement du modèle réussi", + "sql.migration.target.provisioning.upload.template.success": "Le modèle a été chargé avec succès", "sql.migration.test.connection": "Tester la connexion", "sql.migration.dashboard.help.description.migrateUsingADS": "L’extension de migration Azure SQL pour Azure Data Studio fournit des fonctionnalités pour évaluer, obtenir des recommandations Azure adaptées et migrer SQL Server bases de données vers Azure.", "sql.migration.sqldb.not.ready": "Le serveur de base de données langage SQL '{0}' n'est pas disponible pour la migration car il est actuellement à l'état '{1}'. Pour continuer, sélectionnez un serveur de base de données langage SQL disponible.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "Chargement de la ou des sauvegardes de fichier journal", "sql.migration.sqldb.column.usedparallelcopies": "Copies parallèles utilisées", "sql.migration.path.user.account": "Compte utilisateur", + "sql.migration.network.share.user.account.label": "Compte utilisateur", "sql.migration.username": "Nom d'utilisateur", + "sql.migration.database.assessment.qds.label": "Utilisation du Magasin de données des requêtes (cette option est disponible pour Microsoft SQL Server 2016 et versions ultérieures)", + "sql.migration.database.assessment.xevents.label": "Utilisation d’une session d’événements étendue", "sql.migration.starting.login": "La validation et la migration des connexions sont en cours", "sql.login.migration.establish.user.mappings": "Validation et migration des identifiants terminées.\r\n\r\nÉtablir des mappages d'utilisateurs.", "sql.migration.starting.login.failed": "Échec de la validation et de la migration des connexions", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "Nous avons exécuté les étapes suivantes :", "sql.login.migration.wizard.target.data.migration.warning": "Nous vous recommandons de migrer vos bases de données vers la cible Azure SQL avant de commencer la migration de connexion pour éviter les échecs du processus. Vous pouvez exécuter ce processus de migration quand vous le souhaitez si votre objectif est de mettre à jour le mappage utilisateur pour les bases de données récemment migrées.\r\n\r\nSi les noms de la source et de la base de données ne sont pas identiques, il est possible que certaines autorisations ne soient pas appliquées correctement.", "sql.migration.blob.storage.folder.info": "Lorsque vous chargez des sauvegardes de base de données dans votre conteneur d'objets blob, assurez-vous que les fichiers de sauvegarde de différentes bases de données sont stockés dans des dossiers distincts. Seule la racine du conteneur et les dossiers d'au plus un niveau de profondeur sont pris en charge.", + "sql.ir.local.ir.setup.note": "Lorsque vous cliquez sur « exécuter le script », le script PowerShell ci-dessous télécharge automatiquement le logiciel d'exécution d'intégration auto-hébergé, l'installe et l'enregistre auprès de votre Database Migration Service Azure. Pour vérifier l’état de connexion du runtime d’intégration, revenez à l’écran précédent et actualisez. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "Où souhaitez-vous sauvegarder les données collectées ?", "sql.migration.network.share.windows.user.label": "Compte d’utilisateur Windows avec accès en lecture à l’emplacement du partage réseau", "sql.migration.network.share.windows.user.info": "Compte d’utilisateur Windows avec accès en lecture à l’emplacement du partage réseau.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Nom de votre ressource Azure Database Migration Service", "sql.migration.sku.resource": "Nom de votre ressource cible Azure SQL", "sql.migration.sku.resource.port": "Votre Azure SQL numéro de port de ressource cible : 0 - 65535", + "sql.migration.storage.account.blob.container": "Nom de votre conteneur Blob", + "sql.migration.storage.account": "Votre nom de compte de stockage", "sql.migration.pre.req.4": "Les détails de l’emplacement de sauvegarde de votre base de données, un partage de fichiers réseau ou un conteneur Stockage Blob Azure (non requis pour Azure SQL Database cibles).", "sql.migration.wizard.sku.assessment.error.detail": "[Il n’existe aucun résultat d’évaluation pour valider la préparation de la migration de votre base de données. En cochant cette case, vous reconnaissez vouloir poursuivre la migration de votre base de données vers la cible Azure SQL souhaitée.]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-it/CHANGELOG.md b/i18n/ads-language-pack-it/CHANGELOG.md index 6deb81783aab..786876a16a9b 100644 --- a/i18n/ads-language-pack-it/CHANGELOG.md +++ b/i18n/ads-language-pack-it/CHANGELOG.md @@ -2,7 +2,8 @@ Tutti i cambiamenti degni di nota al language pack "ads-language-pack-it" saranno documentati in questo file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-it/package.json b/i18n/ads-language-pack-it/package.json index 63411c27c6bf..f4fa0dd3b74a 100644 --- a/i18n/ads-language-pack-it/package.json +++ b/i18n/ads-language-pack-it/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-it", "displayName": "Italian Language Pack for Azure Data Studio", "description": "Language pack extension for Italian", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-it/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-it/translations/extensions/Microsoft.mssql.i18n.json index 9ca66443d787..937ed89b3504 100644 --- a/i18n/ads-language-pack-it/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-it/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "Filegroup", "objectManagement.databaseProperties.filegrowthLimitError": "L'aumento delle dimensioni del file non può essere maggiore della dimensione massima per un file", "objectManagement.databaseProperties.filesText": "File", - "objectManagement.optionsSectionHeader": "File", + "objectManagement.filesSectionHeader": "File", "objectManagement.databaseProperties.filestreamFilesText": "File FileStream", "objectManagement.filterSectionTitle": "Filtri", "objectManagement.findText": "Trova", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "Modalità operativa (effettiva)", "objectManagement.databaseProperties.requestedOperationModeText": "Modalità operativa (richiesta)", "objectManagement.optimizeAdHocWorkloadsLabel": "Ottimizza carichi di lavoro ad hoc", + "objectManagement.optionsSectionHeader": "Opzioni", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "Nome file originale", "objectManagement.overwriteExistingBackups": "Sovrascrivi tutti i set di backup esistenti", "objectManagement.backupOverwriteMedia": "Sovrascrivi supporti di memorizzazione", diff --git a/i18n/ads-language-pack-it/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-it/translations/extensions/Microsoft.notebook.i18n.json index a96e17b29790..c512a09afe0a 100644 --- a/i18n/ads-language-pack-it/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-it/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "Sfoglia", - "configurePython.installationType": "Tipo di installazione", - "configurePython.newInstall": "Nuova installazione di Python", "configurePythyon.noVersionsFound": "Non sono state trovate versioni Python supportate.", "configurePython.descriptionWithoutKernel": "I kernel dei notebook richiedono la configurazione di un runtime Python e l'installazione delle dipendenze.", - "configurePython.locationTextBoxText": "Percorso di installazione di Python", - "configurePython.pythonConfigured": "Il runtime Python è stato configurato.", + "configurePython.locationTextBoxText": "Percorso di Python", "configurePython.selectFileLabel": "Seleziona", "configurePython.descriptionWithKernel": "Il kernel '{0}' richiede la configurazione di un runtime Python e l'installazione delle dipendenze.", - "configurePython.existingInstall": "Usa l'installazione esistente di Python", + "configurePythyon.existingInstance": "{0} (Istanza Python corrente)", "configurePythyon.customPathLabel": "{0} (Personalizzato)", - "configurePythyon.defaultPathLabel": "{0} (Predefinito)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "È necessario specificare un percorso di notebook" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "Le sessioni del notebook di Python attive verranno arrestate per l'aggiornamento. Procedere ora?", "msgWaitingForInstall": "È già in corso un'altra installazione di Python. Attendere che venga completata.", - "msgPythonRunningError": "Non è possibile sovrascrivere un'installazione esistente di Python mentre Python è in esecuzione. Chiudere gli eventuali notebook attivi prima di procedere.", - "dontAskAgain": "Non chiedere più", - "msgDownloadPython": "Download della versione locale di Python per la piattaforma {0} in {1}", - "msgPythonDownloadPending": "Download del pacchetto Python", "msgGetPythonUserDirFailed": "Si è verificato un errore durante il recupero del percorso utente di Python: {0}", "msgPackageRetrievalFailed": "Si è verificato un errore durante il tentativo di recuperare l'elenco dei pacchetti installati: {0}", - "msgPythonDirectoryError": "Si è verificato un errore durante la creazione della directory di installazione di Python", - "msgPythonDownloadError": "Si è verificato un errore durante il download della configurazione di Python", - "msgPythonUnpackError": "Si è verificato un errore durante la decompressione del bundle di Python", "msgTaskName": "Installazione delle dipendenze di Notebook", "msgDependenciesInstallationFailed": "L'installazione delle dipendenze di Notebook non è riuscita. Errore: {0}", "msgInstallPkgStart": "Installazione delle dipendenze di Notebook. Per altre informazioni, vedere la visualizzazione attività", - "no": "No", "msgInstallPkgFinish": "L'installazione delle dipendenze di Notebook è stata completata", - "msgInstallPkgProgress": "L'installazione delle dipendenze di Notebook è in corso", - "msgPythonDownloadComplete": "Il download di Python è stato completato", - "msgPythonVersionUpdatePrompt": "Python {0} è ora disponibile in Azure Data Studio. La versione corrente di Python (3.6.6) non sarà supportata da dicembre 2021. Eseguire ora l'aggiornamento a Python {0} ?", - "msgPythonVersionUpdateWarning": "Python {0} verrà installato e sostituirà Python 3.6.6. Alcuni pacchetti potrebbero non essere più compatibili con la nuova versione o potrebbero dover essere reinstallati. Verrà creato un notebook che consente di reinstallare tutti i pacchetti pip. Continuare con l'aggiornamento ora?", - "msgPythonUnpackPending": "Decompressione del pacchetto Python", - "yes": "Sì" + "msgInstallPkgProgress": "L'installazione delle dipendenze di Notebook è in corso" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "L'arresto del server di Notebook non è riuscito: {0}" diff --git a/i18n/ads-language-pack-it/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-it/translations/extensions/Microsoft.sql-migration.i18n.json index 8ff53319e9f8..42de992c561d 100644 --- a/i18n/ads-language-pack-it/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-it/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "Il cutover della migrazione dell'Istanza gestita di SQL al livello di servizio business critical può richiedere molto più tempo dell'utilizzo generico perché è necessario eseguire il seeding di tre repliche secondarie per il gruppo di disponibilità elevata Always On. La durata di questa operazione dipende dalle dimensioni dei dati. La velocità di seeding nel 90% dei casi è pari a 220 GB/ora o a una velocità superiore.", "sql.migration.dashboard.help.description.dmsGuide": "Un hub di articoli sulla migrazione che fornisce indicazioni dettagliate per la migrazione e la modernizzazione degli asset di dati in Azure.", "sql.migration.resource.group.description": "Un gruppo di risorse è un contenitore che include le risorse correlate per una soluzione di Azure.", + "sql.migration.target.provisioning.template.display.limit": "Un singolo modello di ARM prevede un limite di distribuzione di un massimo di 50 database SQL di Azure. Il modello per i primi 50 database è visualizzato di seguito. Per visualizzare tutti i modelli, salvare il file JSON del modello in una risorsa di archiviazione locale o in una risorsa di archiviazione BLOB di Azure.", "sql.migration.pre.req.2": "Un database di SQL Server di origine in esecuzione in locale o in SQL Server su macchina virtuale di Azure o su qualsiasi macchina virtuale in esecuzione nel cloud (privato, pubblico).", "sql.migration.dashboard.help.description.sqldb": "Esercitazione dettagliata per eseguire la migrazione di database da un'istanza di SQL Server (locale o macchine virtuali di Azure) a database SQL di Azure.", "sql.migration.dashboard.help.description.mi": "Esercitazione dettagliata per eseguire la migrazione di database da un'istanza di SQL Server (locale o macchine virtuali di Azure) a Istanza gestita di SQL di Azure con tempi di inattività minimi.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "Tutti i backup sono stati ripristinati", "sql.migration.view.all": "Tutte le migrazioni del database", "sql.migration.all.fields.required": "Tutti i campi sono obbligatori.", + "sql.ir.version.mismatch": "Tutti i nodi devono essere della stessa versione per essere configurati", "sql.migration.all.source.tables.empty": "Tutte le tabelle di origine sono vuote. Nessuna tabella disponibile per la selezione per la migrazione dei dati. Sono tuttavia disponibili per la migrazione dello schema se non esistono nella destinazione.", "sql.migration.unavailable.source.tables.heading": "Tutte le tabelle seguenti sono vuote. Nessuna tabella disponibile per la selezione per la migrazione dei dati. Tuttavia, se non esistono nella destinazione, è disponibile la migrazione dello schema.", "sql.migration.missing.tables.heading": "Nella destinazione mancano tutte le tabelle seguenti. Per eseguire la migrazione dei dati in queste tabelle, selezionare l'opzione di migrazione dello schema precedente.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "Annullare la migrazione?", "sql.delete.migration.confirmation": "Eliminare questa migrazione?", "sql.migration.migration.list.ascending.label": "Crescente", - "sql.migration.database.assessment.xevents.title": "Valutare le sessioni di eventi estesi", + "sql.migration.database.assessment.xevents.title": "Valuta SQL ad hoc o dinamico", "sql.migration.assessed.dbs.label": "Database valutati: {0}", "sql.migration.assessment.findings.label": "Risultati della valutazione", "sql.migration.assessment.in.progress": "Valutazione in corso", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Servizio Migrazione del database di Azure", "sql.migration.service.ready": "Servizio Migrazione del database di Azure '{0}' è connesso al runtime di integrazione self-hosted in esecuzione nei nodi- {1}\r\n\r\nPer migliorare le prestazioni e la disponibilità elevata, è possibile registrare nodi aggiuntivi.", "sql.migration.service.ready.below": "Servizio Migrazione del database di Azure '{0}' è connesso al runtime di integrazione self-hosted in esecuzione nei nodi. {1}\r\n\r\nPer migliorare le prestazioni e la disponibilità elevata, è possibile registrare nodi aggiuntivi. Per istruzioni sulla registrazione, vedere di seguito.", + "sql.migration.service.ready.without.nodes": "Il Servizio Migrazione del database di Azure '{0}' è connesso al runtime di integrazione self-hosted in esecuzione sui seguenti nodi.", "sql.migration.service.header": "Dettagli sul Servizio Migrazione del database di Azure \"{0}\":`", "sql.migration.service.not.ready": "Il Servizio Migrazione del database di Azure non è registrato. Il Servizio Migrazione del database di Azure '{0}' deve essere registrato con il runtime di integrazione self-hosted su un nodo.", "sql.migration.service.not.ready.below": "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..\r\n\r\nVedere di seguito per le istruzioni di registrazione.", + "sql.migration.ir.container.description": "Il Servizio Migrazione del database di Azure sfrutta il Microsoft Integration runtime di integrazione self-hosted di Azure Data Factory per caricare i backup dalla condivisione di rete locale in Azure. In base alle selezioni nella pagina precedente, sarà necessario configurare un Integration Runtime self-hosted.", "sql.migration.service.container.container.description1": "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).", "sql.migration.services.name": "Nome del Servizio Migrazione del database di Azure.", "sql.migration.ir.page.description": "Il Servizio Migrazione del database di Azure orchestra le attività di migrazione dei database e tiene traccia dei progressi. È possibile selezionare un Servizio Migrazione del database esistente, se ne è stato creato uno in precedenza, o crearne uno nuovo di seguito.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Area di Azure per il Servizio Migrazione del database di Azure. Verranno visualizzate solo le aree che contengono un servizio.", "sql.migration.services.location": "Area di Azure per il Servizio Migrazione del database di Azure. Deve essere la stessa area dell'Azure SQL di destinazione.", "sql.migration.sku.location": "Area di Azure per la destinazione Azure SQL. Verranno visualizzate solo le aree che contengono una destinazione idonea per la migrazione.", + "sql.migration.storage.account.location": "Area di Azure per l'account di archiviazione. Verranno visualizzate solo le aree che contengono un account di archiviazione.", "sql.migration.summary.azure.storage": "Archiviazione di Azure", "sql.migration.validate.ir.validation.result.label.storage": "Connettività di Archiviazione di Azure", "sql.migration.summary.azure.storage.subscription": "Sottoscrizione di archiviazione di Azure", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "Dimensioni backup (MB)", "sql.migration.backup.start.time": "Ora di inizio backup", "sql.migration.wizard.sku.all": "In base ai risultati della valutazione, è possibile eseguire la migrazione di tutti e {0} i database in stato online ad Azure SQL.", + "sql.migration.target.provisioning.description": "Di seguito è riportato lo script ARM per lo SKU di destinazione consigliato. È possibile salvare lo script come modello.", "sql.migration.sku.targetStorageConfiguration.info": "Di seguito è riportata la configurazione dell'archiviazione di destinazione necessaria per soddisfare le esigenze di prestazioni di archiviazione.", "sql.migration.blob.container.title": "Contenitore BLOB", "sql.migration.blob.container.label": "Gruppo di risorse del contenitore BLOB", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "Fai clic per visualizzare i dettagli dell'errore", "sql.migration.service.details.button.label": "Chiudi", "sql.migration.close": "Chiudi", + "sql.migration.target.provisioning.close": "Chiudi", "sql.migration.sku.azureRecommendation.collectData.method": "Raccogli ora i dati delle prestazioni", "sql.login.migration.collecting.target.logins.failed": "La raccolta dell'accesso di destinazione non è riuscita con codice di errore {0}", "sql.migration.status.collectioncompleted": "Raccolta completata", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "Il completamento del cutover senza ripristinare tutti i backup può comportare una perdita di dati.", "sql.migration.restore.status.completing.migration": "Completamento della migrazione", "sql.migration.save.close.popup": "Configurazione salvata. La raccolta dei dati sulle prestazioni rimarrà in esecuzione in background. È possibile arrestare la raccolta quando si vuole.", + "sql.migration.configure.ir": "Configura Microsoft Integration Runtime", + "sql.ir.configure.manually": "Configurazione manuale ", + "sql.ir.configure.powershellscript": "Configura usando lo script di PowerShell ", "sql.migration.connection.label": "Connettere", "sql.migration.community.support.description": "Entra in contatto con la community Microsoft", "sql.migration.wizard.target.connection.error": "Errore di connessione: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "Descrizione", "sql.migration.details.title": "Dettagli", "sql.migration.details.copied": "Copia dei dettagli completata", + "sql.migration.validate.ir.error.message": "I dettagli per {0} sono obbligatori e mancanti.", "sql.migration.field.label.deteected.files": "File rilevati", "sql.migration.dashboard.description": "Determinare l'idoneità alla migrazione delle istanze di SQL Server, identificare una destinazione di Azure SQL consigliata e completare la migrazione dell'istanza di SQL Server a Istanza gestita di SQL di Azure, SQL Server in Macchine virtuali di Azure o database SQL di Azure.", "sql.migration.restore.backuptype.differentialdatabase": "Database differenziale", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "Immettere le credenziali di autenticazione di Windows usate per la connessione all'istanza di SQL Server {0}. Queste credenziali verranno usate per connettersi all'istanza di SQL Server e identificare i file di backup validi.", "sql.migration.source.details.windowAuth.db": "Immettere le credenziali di autenticazione Windows usate per la connessione all'istanza di SQL Server {0}. Queste credenziali verranno usate per connettersi all'istanza di SQL Server dal runtime di integrazione self-hosted.", "sql.migration.enter.your.sql.cred": "Immettere le credenziali per l'istanza di SQL Server di origine. Queste credenziali verranno usate durante la migrazione dei database ad Azure SQL.", + "sql.migration.select.storage.account.heading": "Immettere i dettagli seguenti per selezionare l'account Archiviazione di Azure e salvare lo script come modello", "sql.migration.services.container.description": "Immettere le informazioni di seguito per aggiungere un nuovo Servizio Migrazione del database di Azure.", "sql.migration.services.container.description.network": "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.", "sql.migration.sku.parameters.text": "Immettere le informazioni seguenti per modificare i parametri della raccomandazione.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "Errore: Istanza gestita di SQL di Azure supporta un massimo di {0} database utente per istanza. Seleziona {0} o meno database per continuare.", "sql.login.migration.migrate.server.roles.and.set.permissions": "Definizione dei mapping utente completata..\r\n\r\nÈ in corso la migrazione dei ruoli del server, la creazione di mapping del server e l'impostazione delle autorizzazioni. L'operazione richiederà qualche minuto.", "sql.login.migration.establish.user.mappings.failed": "La definizione dei mapping utente non è riuscita", + "sql.ir.powershellscript": "Esegui script ", + "sql.ir.executing.powershellscript": "Esecuzione avviata e monitoraggio della finestra di PowerShell aperta. ", "sql.migration.support.resources.description": "Esplora la documentazione", "sql.migration.tde.wizard.optionads": "Esportare i certificati e le chiavi private nella destinazione.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "La migrazione degli account di accesso {0} a {1} '{2}' non è riuscita", "sql.migration.notebook.open.error": "Non è stato possibile aprire il notebook di migrazione.", "sql.migration.dms.provision.failed": "Non è stato possibile effettuare il provisioning di un Servizio Migrazione del database. Attendere qualche minuto, quindi riprovare.", + "sql.migration.target.provisioning.save.template.fail": "Non è stato possibile salvare il modello di ARM", + "sql.migration.target.provisioning.upload.template.fail": "Non è stato possibile caricare il modello di ARM", "sql.migration.tab.button.feedback.description": "Feedback", "sql.migration.tab.button.feedback.label": "Feedback", "sql.migration.feedback.issue.title": "Feedback sull'esperienza di migrazione", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "Seguire le istruzioni seguenti per configurare il runtime di integrazione self-hosted.", "sql.migration.database.table.selection.description": "Per ogni database seguente, fare clic su Modifica per selezionare le tabelle di cui eseguire la migrazione dall'origine alla destinazione. Quindi, prima di fare clic su Avanti, convalidare la configurazione specificata facendo clic su 'Esegui convalida'.", "sql.migration.sql.vm.page.blob.info": "Per i server di destinazione che eseguono SQL Server 2014 o versione precedente, è necessario archiviare i backup dei database in un contenitore BLOB del servizio di archiviazione di Azure invece di caricarli usando l'opzione condivisione di rete. È inoltre necessario archiviare i file di backup come BLOB di pagine, perché i BLOB in blocchi sono supportati solo per le destinazioni che eseguono SQL Server 2016 o versione successiva. Altre informazioni: {0}", - "sql.migration.database.assessment.xevents.description": "È 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}", + "sql.migration.database.assessment.xevents.description": "È 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.", "sql.migration.full.backup.files": "File di backup completo", "sql.migration.sku.azureConfiguration.gen5": "Generazione5", "sql.migration.sku.azureConfiguration.generalPurpose": "Utilizzo generico", + "sql.migration.target.provisioning.generate.template": "Genera modello", "sql.migration.status.generatingscript": "Generazione dello script", "sql.migration.status.generatingcompleted": "Generazione dello script completata", "sql.migration.sku.get.recommendation": "Ottieni raccomandazione di Azure", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "L'utente conferma che non sono presenti altri backup del log da fornire e che desidera completare il cutover.", "sql.migration.tde.wizard.optionadsconfirm": "Acconsento all'utilizzo delle mie credenziali per l'accesso ai certificati.", "sql.migration.tde.wizard.optionmanual": "Ho già eseguito la migrazione dei certificati e delle chiavi private alla destinazione.", + "sql.ir.local.ir.definition": "Voglio configurare il runtime di integrazione self-hosted in un altro computer Windows che non è il computer locale.", "sql.migration.sku.io.memory.requirement": "Requisito latenza I/O", + "sql.ir.ip.address": "Indirizzo IP", + "sql.ir.config.type": "Tipo di configurazione runtime di integrazione", + "sql.ir.ir.version": "Versione runtime di integrazione", "sql.migration.empty.table.subtext": "Se sono previsti risultati, verificare la connessione all'istanza di SQL Server.", "sql.migration.wizard.cancel.reason.others.input.box.note": "Se sono stati selezionati altri utenti, scrivere una breve nota.", "sql.migration.impact": "Impatto", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "Importa valutazione in Azure SQL", "sql.migration.sku.import.performance.data": "Importa dati sulle prestazioni", "sql.migration.sku.import.performance.data.dialog.description": "Importa questo file di dati da una cartella esistente, se è già stato raccolto tramite Data Migration Assistant.", + "sql.ir.important": "Importante", "sql.migration.database.migration.migration.mode.tool.tip": "In Servizio Migrazione del database di Azure è possibile eseguire la migrazione dei database offline o mentre sono online. In una migrazione offline, il tempo di inattività dell'applicazione viene avviato all'avvio della migrazione. Per limitare il tempo di inattività al tempo necessario per eseguire il cutover nel nuovo ambiente dopo la migrazione, usare una migrazione online.", "sql.migration.tde.validation.requirements.message": "Per completare la migrazione dei certificati, è necessario soddisfare tutti i requisiti elencati di seguito.\r\n\r\nFare clic su \"Esegui convalida\" per verificare che i requisiti siano soddisfatti.", "sql.migration.copy.status.inprogress": "In corso", @@ -484,6 +506,8 @@ "sql.login.migration.type": "Tipo di account di accesso", "sql.migration.sku.logs.iops.requirement": "Requisito operazioni di I/O al secondo dei log", "sql.migration.field.label.mi.restore.state": "Stato di ripristino dell'istanza gestita", + "sql.ir.manual.ir.collapsed": "Configurazione runtime di integrazione manuale compressa", + "sql.ir.manual.ir.expanded": "Configurazione runtime di integrazione manuale espansa", "sql.migration.map.target.heading": "Eseguire il mapping dei database di origine selezionati ai database di destinazione per la migrazione", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "Serie Premium con ottimizzazione per la memoria", "sql.migration.sku.memory.requirement": "Requisiti memoria", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "Nuova migrazione", "sql.migration.newSupportRequest": "Nuova richiesta di supporto", "sql.migration.saved.assessment.next": "Avanti", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "Per utilizzo generico di nuova generazione", "sql.migration.no": "No", "sql.migration.no.sqldatabaseserver.found": "Non sono stati trovati server di database SQL di Azure.", "sql.migration.no.sqldatabase.found": "Non sono stati trovati database SQL di Azure.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Nono sono stati riscontrati problemi per la migrazione a SQL Server per la macchina virtuale di Azure.", "sql.migration.no.location.found": "Nessuna località trovata.", "sql.migration.no.managedInstance.found": "Non sono state trovate istanze gestite.", + "sql.ir.no.node.found": "Nessun nodo trovato", "sql.migration.no.pending.backups": "Nessun backup in sospeso. Fare clic su Aggiorna per controllare lo stato corrente.", "sql.migration.cancel.feedback.no.reason.selected": "Nessun motivo selezionato", "sql.migration.wizard.sku.error.noRecommendation": "Nessuna raccomandazione disponibile", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "Non sono state trovate sottoscrizioni.", "sql.migration.select.target.label": "Nessuna destinazione selezionata. Selezionare la destinazione per visualizzare il riepilogo della valutazione.", "sql.migration.no.virtualMachine.found": "Non sono state trovate macchine virtuali.", + "sql.ir.node.name": "Nome nodo", "sql.migration.restore.status.none": "Nessuno", "sql.migration.restore.backupset.status.none": "Nessuno", "sql.migration.parallel.copy.type.none": "Nessuno", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "Non pronto", "sql.migration.restore.status.not.started": "Non avviato", "sql.login.migration.steps.not.started": "Non avviato", + "sql.ir.recommended.link": "Nota: vedere gli elementi consigliati del runtime di integrazione self-hosted", "sql.migration.backup.file.number.of.stripes": "Numero di strisce", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "OK", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "Oggetti raccolti", "sql.migration.offline": "Offline", "sql.migration.database.migration.mode.offline.label": "Migrazione offline", + "sql.ir.powershellscript.definition": "Una volta eseguito in PowerShell, lo script univoco visualizzato di seguito scaricherà e installerà il runtime di integrazione self-hosted e lo registrerà con il Servizio Migrazione del database di Azure. PowerShell deve essere installato nel computer di destinazione.", "sql.migration.online": "Online", "sql.migration.database.migration.mode.online.label": "Migrazione online", "sql.migration.open": "Apri", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "Selezionare il percorso dei file di backup del database prima di continuare.", "sql.migration.cancel.feedback.reason.container.description": "Attendere qualche istante per indicare il motivo dell'annullamento della migrazione. Questo ci aiuterà a migliorare l'esperienza.", "sql.migration.port.label": "Porta", + "sql.ir.powershell.script.saved": "Script PowerShell salvato", + "sql.ir.ps.script.collapsed": "Script PowerShell compresso", + "sql.ir.ps.script.expanded": "Script powershell espanso", "sql.migration.status.prefetchobjects": "Prelettura oggetti", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "Unità SSD Premium", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "SSD Premium v2", "sql.migration.sku.azureConfiguration.premiumSeries": "Serie Premium", "sql.migration.copy.status.preparingforcopy": "Preparazione", + "sql.ir.powershell.prereq": "Prerequisito: è necessario PowerShell con privilegi di esecuzione come amministratore. ", "sql.login.migration.status.page.previous.button.title": "Precedente (disabilitato)", "sql.migration.tde.migrate.results.heading.previous": "Risultati della migrazione dei certificati precedenti:", "sql.migration.provide.unique.containers": "Specificare un contenitore univoco per ogni database di destinazione. Database interessati: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "L'aggiornamento dell'elenco di accesso dalla destinazione non è riuscito", "sql.login.migration.refresh.login.data.successful": "L'aggiornamento dell'elenco di accesso è riuscito. Account di accesso di origine trovati {0}. Account di accesso di destinazione trovati {1}", "sql.migration.resourceGroups": "Gruppo di risorse", + "sql.migration.storage.account.resource.group.label": "Gruppo di risorse", "sql.migration.rg.created": "Il gruppo di risorse è stato creato", "sql.migration.services.resource.group": "Gruppo di risorse per il Servizio Migrazione del database di Azure.", "sql.migration.dms.resource_group": "Gruppo di risorse per la destinazione Azure SQL. Verranno visualizzati solo i gruppi di risorse che contengono un servizio.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "File di log SQL", "sql.migration.sql.assessment.notebook.title": "Valutazione della migrazione SQL", "sql.migration.sku.sql.temp": "Tempdb SQL", + "sql.migration.target.provisioning.save": "Salva", + "sql.migration.target.provisioning.title": "Salva modello", "sql.migration.save.close": "Salva e chiudi", "sql.migration.save.assessment.report": "Salvare report di valutazione", "sql.migration.save.recommendation.report": "Salvare report delle raccomandazioni", + "sql.ir.save.script": "Salva script", + "sql.migration.target.upload.to.azure": "Salva in Contenitore BLOB di Azure", "sql.migration.saved.assessment.result": "Sessione salvata", "sql.migration.sku.parameters.scale.factor": "Fattore di scala:", "sql.migration.schema.data": "Schema e dati", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "Ricerca dei backup", "sql.migration.wizard.troubleshooting": "Per altre procedure di risoluzione dei problemi, vedere il collegamento: https://aka.ms/dms-migrations-troubleshooting.", "sql.migration.select": "Seleziona", + "sql.migration.select.storage.account.title": "Seleziona account di archiviazione di Azure", "sql.migration.select.service.title": "Seleziona Servizio Migrazione del database", "sql.migration.select.service.prompt": "Selezionare un Servizio Migrazione del database", "sql.migration.select.service.select.a.service": "Selezionare un Servizio Migrazione del database", "sql.migration.invalid.migration.service.offline.error": "Selezionare un Servizio Migrazione del database connesso a un nodo.", "sql.migration.status.select.service.MESSAGE": "Selezionare un Servizio di Migrazione del database per monitorare le migrazioni.", + "sql.migration.select.storage.select.a.storage.account": "Selezionare un account di archiviazione", "sql.migration.blob.container.select": "Selezionare prima un valore del contenitore BLOB.", "sql.migration.sku.import.performance.data.dialog.open.folder": "Selezionare una cartella", "sql.migration.sku.import.performance.data.dialog.helper.message": "Selezionare una cartella nell'unità locale", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "Interrompi convalida", "sql.migration.sku.azureRecommendation.stop.popup": "Arresto della raccolta dei dati delle prestazioni...", "sql.migration.sku.targetStorageConfiguration.storage": "Archiviazione", - "sql.migration.storage.account": "Account di archiviazione", + "sql.migration.select.storage.account.label": "Account di archiviazione", + "sql.migration.storage.account.details.label": "Account di archiviazione", "sql.migration.network.share.azure.header": "Dettagli dell'account di archiviazione", "sql.migration.subscription": "Sottoscrizione", "sql.migration.blob.storage.subscription.label": "Sottoscrizione", "sql.migration.dms.subscription": "Gruppo di risorse per il Servizio Migrazione del database di Azure", "sql.migration.services.subscription": "Gruppo di risorse per il Servizio Migrazione del database di Azure.", "sql.migration.sku.subscription": "Nome sottoscrizione per l’SQL Azure di destinazione", + "sql.migration.storage.account.subscription": "Nome della sottoscrizione per l'account di archiviazione", "sql.migration.state.succeeded": "Riuscito", "sql.migration.tde.validation.status.succeeded": "Operazione riuscita", "sql.migration.copy.status.succeeded": "Riuscita", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "Tipo di destinazione", "sql.migration.username.label": "Nome utente di destinazione", "sql.migration.target.version": "Versione di destinazione", + "sql.migration.target.provisioning.save.template.success": "Salvataggio del modello completato", + "sql.migration.target.provisioning.upload.template.success": "Il modello è stato caricato", "sql.migration.test.connection": "Verifica connessione", "sql.migration.dashboard.help.description.migrateUsingADS": "L'estensione Azure SQL Migration per Azure Data Studio offre funzionalità per valutare, ottenere consigli di Azure di dimensioni corrette ed eseguire la migrazione di database SQL Server in Azure.", "sql.migration.sqldb.not.ready": "Il server di database SQL '{0}' non è disponibile per la migrazione perché si trova attualmente nello stato '{1}'. Per continuare, selezionare un server di database SQL disponibile.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "Caricamento dei backup del log in corso", "sql.migration.sqldb.column.usedparallelcopies": "Copie parallele usate", "sql.migration.path.user.account": "Account utente", + "sql.migration.network.share.user.account.label": "Account utente", "sql.migration.username": "Nome utente", + "sql.migration.database.assessment.qds.label": "Utilizzo di Query Data Store (questa opzione è disponibile per Microsoft SQL Server 2016 e versioni successive)", + "sql.migration.database.assessment.xevents.label": "Utilizzo della sessione eventi estesa", "sql.migration.starting.login": "La convalida e la migrazione degli account di accesso sono in corso", "sql.login.migration.establish.user.mappings": "Convalida e migrazione degli account di accesso completate.\r\n\r\nDefinizione dei mapping utente.", "sql.migration.starting.login.failed": "Convalida e migrazione degli account di accesso non riuscita", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "Sono stati eseguiti i passaggi seguenti:", "sql.login.migration.wizard.target.data.migration.warning": "È consigliabile eseguire la migrazione dei database alla destinazione Azure SQL prima di avviare la migrazione dell'account di accesso per evitare errori nel processo. Tuttavia, è possibile eseguire questo processo di migrazione ogni volta che si vuole se l'obiettivo è aggiornare il mapping utente per i database di cui è stata eseguita la migrazione di recente.\r\n\r\n Se i nomi di origine e di database non sono uguali, è possibile che alcune autorizzazioni non vengano applicate correttamente.", "sql.migration.blob.storage.folder.info": "Durante il caricamento dei backup del database nel contenitore BLOB, assicurarsi che i file di backup di database diversi siano archiviati in cartelle separate. Sono supportate solo la radice del contenitore e delle cartelle a un massimo di un livello.", + "sql.ir.local.ir.setup.note": "Quando si fa clic su \"Esegui script\", lo script PowerShell seguente scaricherà automaticamente il software del runtime di integrazione self-hosted, lo installerà e lo registrerà con il Servizio Migrazione del database di Azure. Per controllare lo stato della connessione del runtime di integrazione, tornare alla schermata precedente e aggiornare. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "Dove si vogliono salvare i dati raccolti?", "sql.migration.network.share.windows.user.label": "Account utente di Windows con accesso in lettura al percorso di condivisione di rete", "sql.migration.network.share.windows.user.info": "Account utente di Windows con accesso in lettura al percorso di condivisione di rete.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Nome della risorsa Servizio Migrazione del database di Azure", "sql.migration.sku.resource": "Nome della risorsa di destinazione Azure SQL", "sql.migration.sku.resource.port": "Numero di porta della risorsa di destinazione Azure SQL: 0 - 65535", + "sql.migration.storage.account.blob.container": "Nome del contenitore BLOB", + "sql.migration.storage.account": "Nome dell'account di archiviazione", "sql.migration.pre.req.4": "Dettagli del percorso di backup del database, una condivisione file di rete o un contenitore di Archiviazione BLOB di Azure (non necessario per destinazioni database SQL di Azure).", "sql.migration.wizard.sku.assessment.error.detail": "[Non sono disponibili risultati di valutazione per convalidare l'idoneità della migrazione del database. Selezionando questa casella, si conferma di voler procedere con la migrazione del database alla destinazione Azure SQL desiderata.]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-ja/CHANGELOG.md b/i18n/ads-language-pack-ja/CHANGELOG.md index e0401625c9f0..06374f19d257 100644 --- a/i18n/ads-language-pack-ja/CHANGELOG.md +++ b/i18n/ads-language-pack-ja/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-ja" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-ja/package.json b/i18n/ads-language-pack-ja/package.json index c2a141d028c9..2f998231bc9e 100644 --- a/i18n/ads-language-pack-ja/package.json +++ b/i18n/ads-language-pack-ja/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-ja", "displayName": "Japanese Language Pack for Azure Data Studio", "description": "Language pack extension for Japanese", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-ja/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-ja/translations/extensions/Microsoft.mssql.i18n.json index 0e7f06a928e9..79965902eb5a 100644 --- a/i18n/ads-language-pack-ja/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-ja/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "ファイル グループ", "objectManagement.databaseProperties.filegrowthLimitError": "Filegrowth をファイルの最大ファイル サイズより大きくすることはできません", "objectManagement.databaseProperties.filesText": "ファイル", - "objectManagement.optionsSectionHeader": "ファイル", + "objectManagement.filesSectionHeader": "ファイル", "objectManagement.databaseProperties.filestreamFilesText": "filestream ファイル", "objectManagement.filterSectionTitle": "フィルター", "objectManagement.findText": "検索", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "操作モード (実際)", "objectManagement.databaseProperties.requestedOperationModeText": "操作モード (要求)", "objectManagement.optimizeAdHocWorkloadsLabel": "アドホック ワークロードの最適化", + "objectManagement.optionsSectionHeader": "オプション​​", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "元のファイル名", "objectManagement.overwriteExistingBackups": "既存のすべてのバックアップ セットを上書きする", "objectManagement.backupOverwriteMedia": "メディアを上書きする", diff --git a/i18n/ads-language-pack-ja/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-ja/translations/extensions/Microsoft.notebook.i18n.json index ffd6f2a8b784..bd67a07b75aa 100644 --- a/i18n/ads-language-pack-ja/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-ja/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "参照", - "configurePython.installationType": "インストールの種類", - "configurePython.newInstall": "新しい Python インストール", "configurePythyon.noVersionsFound": "サポートされている Python バージョンが見つかりません。", "configurePython.descriptionWithoutKernel": "Notebook カーネルには、Python ランタイムが構成され、依存関係がインストールされている必要があります。", - "configurePython.locationTextBoxText": "Python のインストール場所", - "configurePython.pythonConfigured": "Python ランタイムが構成されました!", + "configurePython.locationTextBoxText": "Python の場所", "configurePython.selectFileLabel": "選択", "configurePython.descriptionWithKernel": "'{0}' カーネルにって、Python ランタイムを構成し、依存関係をインストールする必要があります。", - "configurePython.existingInstall": "既存の Python インストールを使用する", + "configurePythyon.existingInstance": "{0} (現在の Python インスタンス)", "configurePythyon.customPathLabel": "{0} (カスタム)", - "configurePythyon.defaultPathLabel": "{0} (既定値)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "ノートブック パスが必須です" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "更新のために、アクティブな Python ノートブック セッションがシャットダウンされます。今すぐ続行しますか?", "msgWaitingForInstall": "別の Python のインストールが現在進行中です。完了するのを待っています。", - "msgPythonRunningError": "Python の実行中は、既存の Python インストールを上書きできません。続行する前に、アクティブなノートブックを閉じてください。", - "dontAskAgain": "今後このメッセージを表示しない", - "msgDownloadPython": "{0} から {1} にプラットフォーム用のローカル Python をダウンロードしています", - "msgPythonDownloadPending": "Python パッケージをダウンロードしています", "msgGetPythonUserDirFailed": "Python ユーザー パスの取得時にエラーが発生しました: {0}", "msgPackageRetrievalFailed": "インストールされているパッケージの一覧を取得しようとしてエラーが発生しました: {0}", - "msgPythonDirectoryError": "Python インストール ディレクトリの作成中にエラーが発生しました", - "msgPythonDownloadError": "Python セットアップのダウンロード中にエラーが発生しました", - "msgPythonUnpackError": "Python バンドルのアンパック中にエラーが発生しました", "msgTaskName": "Notebook 依存関係のインストール", "msgDependenciesInstallationFailed": "Notebook 依存関係のインストールに失敗しました。エラー: {0}", "msgInstallPkgStart": "Notebook 依存関係のインストールについて詳しくは、[タスク ビュー] を参照してください", - "no": "いいえ", "msgInstallPkgFinish": "Notebook 依存関係のインストールが完了しました", - "msgInstallPkgProgress": "Notebook 依存関係のインストールが進行中です", - "msgPythonDownloadComplete": "Python のダウンロードが完了しました", - "msgPythonVersionUpdatePrompt": "Python {0} が Azure Data Studio で利用できるようになりました。現在の Python バージョン (3.6.6) は、2021 年 12 月にサポートされなくなります。今すぐ Python {0} に更新しますか?", - "msgPythonVersionUpdateWarning": "Python {0} がインストールされ、Python 3.6.6 が置換されます。一部のパッケージは、新しいバージョンとの互換性がなくなったか、再インストールが必要になる可能性があります。すべての pip パッケージの再インストールを支援するためにノートブックが作成されます。今すぐ更新を続行しますか?", - "msgPythonUnpackPending": "Python パッケージをアンパックしています", - "yes": "はい" + "msgInstallPkgProgress": "Notebook 依存関係のインストールが進行中です" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "Notebook サーバーをシャットダウンできませんでした: {0}" diff --git a/i18n/ads-language-pack-ja/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-ja/translations/extensions/Microsoft.sql-migration.i18n.json index c30a0369e7e5..141956266036 100644 --- a/i18n/ads-language-pack-ja/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-ja/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "ビジネス クリティカル サービス層の SQL Managed Instance の一括移行では、Always On 高可用性グループに 3 つのセカンダリ レプリカをシードする必要があるため、通常の目的よりも大幅に時間がかかります。このオペレーションの期間は、データのサイズに依存します。シードの速度は、90% のケースで220GB/時以上となっています。", "sql.migration.dashboard.help.description.dmsGuide": "Azure のデータ資産の移行と最新化に関して、手順を追ったガイダンスを提供する移行記事のハブ。", "sql.migration.resource.group.description": "リソース グループは、Azure のソリューションに関連するリソースを保持するコンテナーです。", + "sql.migration.target.provisioning.template.display.limit": "1 つの ARM テンプレートには、最大 50 個の Azure SQL データベースというデプロイ制限があります。最初の 50 個のデータベースのテンプレートは、以下のように表示されます。すべてのテンプレートを表示するには、テンプレート JSON ファイルをローカル ストレージまたは Azure Blob Storage に保存します。", "sql.migration.pre.req.2": "オンプレミス、Azure 仮想マシン上のSQL Server、またはクラウドで実行されている任意の仮想マシン (プライベート、パブリック) で実行されているソース SQL Server データベース。", "sql.migration.dashboard.help.description.sqldb": "SQL Server インスタンス (オンプレミスまたは Azure Virtual Machines) から Azure SQL Database にデータベースを移行するためのステップ バイ ステップ チュートリアルです。", "sql.migration.dashboard.help.description.mi": "SQL Server インスタンス (オンプレミスまたは Azure Virtual Machines) から Azure SQL Managed Instance に最小のダウンタイムでデータベースを移行するための手順を追ったチュートリアルです。", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "すべてのバックアップが復元されました", "sql.migration.view.all": "すべてのデータベース移行", "sql.migration.all.fields.required": "すべてのフィールドに入力してください。", + "sql.ir.version.mismatch": "すべてのノードが同じバージョンに構成されている必要があります", "sql.migration.all.source.tables.empty": "すべてのソース テーブルが空です。データ移行用に選択できるテーブルはありません。ただし、ターゲットに存在しない場合は、スキーマの移行に使用できます。", "sql.migration.unavailable.source.tables.heading": "以下のテーブルはすべて空です。データ移行用に選択できるテーブルはありません。ただし、ターゲットに存在しない場合は、スキーマの移行を使用できます。", "sql.migration.missing.tables.heading": "以下のすべてのテーブルがターゲットに存在しません。これらのテーブルのデータを移行するには、上記の [スキーマの移行] オプションを選択します。", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "この移行を取り消しますか?", "sql.delete.migration.confirmation": "この移行を削除しますか?", "sql.migration.migration.list.ascending.label": "昇順", - "sql.migration.database.assessment.xevents.title": "拡張イベント セッションの評価", + "sql.migration.database.assessment.xevents.title": "アドホックまたは動的 SQL を評価する", "sql.migration.assessed.dbs.label": "評価されたデータベース: {0}", "sql.migration.assessment.findings.label": "評価結果", "sql.migration.assessment.in.progress": "評価の実行中", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Azure Database Migration Service", "sql.migration.service.ready": "Azure Database Migration Service '{0}' は、これらのノードで動作中のセルフホステッド統合ランタイムに接続されています - {1}\r\n\r\nパフォーマンスの向上と高可用性を実現したい場合は、追加のノードを登録できます。", "sql.migration.service.ready.below": "Azure Database Migration Service '{0}' は、これらのノードで動作中のセルフホステッド統合ランタイムに接続されています - {1}\r\n\r\nパフォーマンスの向上と高可用性を実現したい場合は、追加のノードを登録できます。登録手順については以下をご覧ください。", + "sql.migration.service.ready.without.nodes": "Azure Database Migration Service '{0}' は、次のノードで実行されているセルフホステッド統合ランタイムに接続されています", "sql.migration.service.header": "Azure Database Migration Service ファイル \"{0}\" の詳細:`", "sql.migration.service.not.ready": "Azure Database Migration Service が登録されていません。Azure Database Migration Service '{0}' は、任意のノードでセルフホステッド統合ランタイムに登録する必要があります。", "sql.migration.service.not.ready.below": "Azure Database Migration Service が登録されていません。Azure Database Migration Service '{0}' が、任意のノードのセルフホステッド統合ランタイムに登録されている必要があります。\r\n\r\n登録手順については以下をご覧ください。", + "sql.migration.ir.container.description": "Azure Database Migration Service は Azure Data Factory のセルフホステッド統合ランタイムを活用して、オンプレミスのネットワーク ファイル共有から Azure にバックアップをアップロードします。前のページの選択内容に基づいて、セルフホステッド統合ランタイムをセットアップする必要があります。", "sql.migration.service.container.container.description1": "Azure Database Migration Service では、ソースとターゲットの間の接続の処理、および (該当する場合) オンプレミスのネットワーク ファイル共有から Azure へのバックアップのアップロードを、Azure Data Factory のセルフホステッド統合ランタイムを利用して行います。", "sql.migration.services.name": "Azure Database Migration Service 名。", "sql.migration.ir.page.description": "Azure Database Migration Service は、データベース移行アクティビティを調整し、その進行状況を追跡します。以前に作成した場合は既存のDatabase Migration Serviceを選択するか、以下で新しいDatabase Migration Serviceを作成できます。", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Azure Database Migration Service における Azure リージョン。サービスを含むリージョンのみが表示されます。", "sql.migration.services.location": "Azure Database Migration Service の Azure リージョン。これは、ターゲット Azure SQL と同じリージョンである必要があります。", "sql.migration.sku.location": "Azure SQL ターゲット用途の Azure リージョン。移行先として適しているターゲットを含むリージョンのみが表示されます。", + "sql.migration.storage.account.location": "ストレージ アカウントの Azure リージョン。ストレージ アカウントを含むリージョンのみが表示されます。", "sql.migration.summary.azure.storage": "Azure Storage", "sql.migration.validate.ir.validation.result.label.storage": "Azure Storage の接続性", "sql.migration.summary.azure.storage.subscription": "Azure ストレージ サブスクリプション", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "バックアップ サイズ (MB)", "sql.migration.backup.start.time": "バックアップ開始時刻", "sql.migration.wizard.sku.all": "評価結果に基づくと、オンライン状態のデータベースのすべての {0} を Azure SQL に移行できます。", + "sql.migration.target.provisioning.description": "おすすめのターゲット SKU の ARM スクリプトを次に示します。スクリプトをテンプレートとして保存できます。", "sql.migration.sku.targetStorageConfiguration.info": "ストレージ パフォーマンスのニーズを満たすために必要なターゲット ストレージ構成を次に示します。", "sql.migration.blob.container.title": "BLOB コンテナー", "sql.migration.blob.container.label": "BLOB コンテナー リソース グループ", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "クリックするとエラー詳細が表示されます。", "sql.migration.service.details.button.label": "閉じる", "sql.migration.close": "閉じる", + "sql.migration.target.provisioning.close": "閉じる", "sql.migration.sku.azureRecommendation.collectData.method": "パフォーマンス データを今すぐ収集する", "sql.login.migration.collecting.target.logins.failed": "ターゲット ログインの収集がエラー コード {0} で失敗しました", "sql.migration.status.collectioncompleted": "コレクションが完了しました", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "すべてのバックアップを復元せずに一括移行を完了すると、データが失われる可能性があります。", "sql.migration.restore.status.completing.migration": "移行を完了しています", "sql.migration.save.close.popup": "構成が保存されました。パフォーマンス データの収集はバックグラウンドで実行されたままになります。必要に応じて、コレクションを停止できます。", + "sql.migration.configure.ir": "統合ランタイムの構成", + "sql.ir.configure.manually": "手動で構成 ", + "sql.ir.configure.powershellscript": "PowerShell スクリプトを使用して構成する ", "sql.migration.connection.label": "接続", "sql.migration.community.support.description": "Microsoft コミュニティとつながる", "sql.migration.wizard.target.connection.error": "接続エラー: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "説明", "sql.migration.details.title": "詳細", "sql.migration.details.copied": "詳細をコピー済み", + "sql.migration.validate.ir.error.message": "{0} の詳細は必須であり、見つかりません。", "sql.migration.field.label.deteected.files": "検出されたファイル", "sql.migration.dashboard.description": "SQL Server インスタンスの移行準備状況を判断し、推奨されるAzure SQLターゲットを特定し、SQL Server インスタンスの Azure SQL Managed Instance への移行、Azure Virtual Machines または Azure SQL Database でのSQL Serverを完了します。", "sql.migration.restore.backuptype.differentialdatabase": "差分データベース", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "SQL Server インスタンス {0} への接続に使用する Windows 認証の資格情報を入力します。これらの資格情報は、SQL Server インスタンスに接続して、有効なバックアップ ファイルを識別するために使用されます。", "sql.migration.source.details.windowAuth.db": "SQL Server インスタンス {0} への接続に使用する Windows 認証の資格情報を入力してください。これらの資格情報は、セルフホステッド統合ランタイムから SQL Server インスタンスへの接続に使用されます。", "sql.migration.enter.your.sql.cred": "ソース SQL Server インスタンスの資格情報を入力します。これらの資格情報は、データベースを Azure SQL に移行する場合に使用されます。", + "sql.migration.select.storage.account.heading": "以下に詳細を入力して Azure Storage アカウントを選択し、スクリプトをテンプレートとして保存します", "sql.migration.services.container.description": "以下の情報を入力して、新しい Azure Database Migration Service を追加します。", "sql.migration.services.container.description.network": "以下の情報を入力して、新しい Azure Database Migration Service を追加します。セルフホステッド統合ランタイムを登録するには、前のページで [データベースのバックアップがネットワーク共有上にある] を選択します。", "sql.migration.sku.parameters.text": "レコメンデーション パラメーターを編集するには、以下の情報を入力します。", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "エラー: Azure SQL Managed Instance でサポートされるインスタンスあたりのユーザー データベースは、最大 {0} 個までです。続行するには、選択するデータベース数を {0} 個以下にします。", "sql.login.migration.migrate.server.roles.and.set.permissions": "ユーザー マッピングの確立が完了しました。\r\n\r\n現在、サーバーの役割を移行し、サーバー マッピングを確立し、アクセス許可を設定しています。これには時間がかかります。", "sql.login.migration.establish.user.mappings.failed": "ユーザー マッピングの確立に失敗しました", + "sql.ir.powershellscript": "スクリプトの実行 ", + "sql.ir.executing.powershellscript": "実行が開始され、開かれた PowerShell ウィンドウを監視します。 ", "sql.migration.support.resources.description": "ドキュメントの探索", "sql.migration.tde.wizard.optionads": "証明書と秘密キーをターゲットにエクスポートします。", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "{0} 件のログインを {1} '{2}' への移行が失敗しました", "sql.migration.notebook.open.error": "移行ノートブックを開けませんでした。", "sql.migration.dms.provision.failed": "Database Migration Service をプロビジョニングできませんでした。数分待ってからもう一度やり直してください。", + "sql.migration.target.provisioning.save.template.fail": "ARM テンプレートを保存できませんでした", + "sql.migration.target.provisioning.upload.template.fail": "ARM テンプレートをアップロードできませんでした", "sql.migration.tab.button.feedback.description": "フィードバック", "sql.migration.tab.button.feedback.label": "フィードバック", "sql.migration.feedback.issue.title": "移行エクスペリエンスのフィードバック", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "セルフホステッド統合ランタイムをセットアップするには、以下の手順に従ってください。", "sql.migration.database.table.selection.description": "以下の各データベースについて、[編集] をクリックし、ソースからターゲットへの移行対象にするテーブルを選択してください。その後、[検証の実行] をクリックして指定の構成を検証してから、[次へ] をクリックしてください。", "sql.migration.sql.vm.page.blob.info": "SQL Server 2014 以下を実行しているターゲット サーバーでは、ネットワーク共有オプションを使用してデータベース バックアップをアップロードするのではなく、Azure Storage Blob コンテナーに格納する必要があります。また、ブロック BLOB はSQL Server 2016 以降を実行しているターゲットでのみサポートされているため、バックアップ ファイルをページ BLOB として保存する必要があります。詳細情報: {0}", - "sql.migration.database.assessment.xevents.description": "選択したデータベースに対して、必要に応じて拡張イベント セッション ファイルを提供して、アドホックまたは動的 SQL クエリ、またはアプリケーション データ レイヤーを介して開始された DML ステートメントを評価します。{0}", + "sql.migration.database.assessment.xevents.description": "選択したデータベースに対して、必要に応じて拡張イベント セッション ファイルを提供して、アドホックまたは動的 SQL クエリ、またはアプリケーション データ レイヤーを介して開始された DML ステートメントを評価します。", "sql.migration.full.backup.files": "完全バックアップ ファイル", "sql.migration.sku.azureConfiguration.gen5": "第 5 世代", "sql.migration.sku.azureConfiguration.generalPurpose": "汎用", + "sql.migration.target.provisioning.generate.template": "テンプレートの生成", "sql.migration.status.generatingscript": "スクリプトを生成しています", "sql.migration.status.generatingcompleted": "スクリプトの生成が完了しました", "sql.migration.sku.get.recommendation": "Azure のレコメンデーションを取得する", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "提供する追加のログ バックアップがないことを確認し、一括移行の完了を希望します。", "sql.migration.tde.wizard.optionadsconfirm": "証明書へのアクセスに自分の資格情報を使用することに同意します。", "sql.migration.tde.wizard.optionmanual": "証明書と秘密鍵は既にターゲットに移行しています。", + "sql.ir.local.ir.definition": "ローカル マシンではない別の Windows マシンにセルフホステッド統合ランタイムをセットアップしたいと考えています。", "sql.migration.sku.io.memory.requirement": "IO 待機時間の要件", + "sql.ir.ip.address": "IP アドレス", + "sql.ir.config.type": "IR 構成の種類", + "sql.ir.ir.version": "IR バージョン", "sql.migration.empty.table.subtext": "結果が期待通りだった場合、SQL Server インスタンスへの接続を確認します。", "sql.migration.wizard.cancel.reason.others.input.box.note": "その他を選択した場合は、短いメモを書いてください。", "sql.migration.impact": "Impact", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "評価を Azure SQL にインポートします", "sql.migration.sku.import.performance.data": "パフォーマンス データのインポート", "sql.migration.sku.import.performance.data.dialog.description": "Data Migration Assistant を使用してこのデータ ファイルを既に収集している場合は、既存のフォルダーからインポートします。", + "sql.ir.important": "重要", "sql.migration.database.migration.migration.mode.tool.tip": "Azure Database Migration Service では、データベースをオフラインにして移行するか、オンライン状態のまま移行することができます。オフライン移行では、移行の開始時にアプリケーションのダウンタイムが開始されます。ダウンタイムの長さを、移行後の新しい環境へのカットオーバー時間のみに限定するには、オンライン移行を使用します。", "sql.migration.tde.validation.requirements.message": "証明書の移行を成功させるには、以下に示す要件をすべて満たしている必要があります。\r\n\r\n[検証の実行] をクリックして、要件が満たされていることを確認します。", "sql.migration.copy.status.inprogress": "進行中", @@ -484,6 +506,8 @@ "sql.login.migration.type": "ログインの種類", "sql.migration.sku.logs.iops.requirement": "ログ IOPS 要件", "sql.migration.field.label.mi.restore.state": "マネージド インスタンスの復元状態", + "sql.ir.manual.ir.collapsed": "手動 IR 構成が折りたたまれています", + "sql.ir.manual.ir.expanded": "手動 IR 構成が展開されています", "sql.migration.map.target.heading": "選択したソース データベースを移行先データベースにマップする", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "メモリ最適化 Premium シリーズ", "sql.migration.sku.memory.requirement": "メモリ要件", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "新規の移行", "sql.migration.newSupportRequest": "新しいサポート リクエスト", "sql.migration.saved.assessment.next": "次へ", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "次世代 General Purpose", "sql.migration.no": "いいえ", "sql.migration.no.sqldatabaseserver.found": "Azure SQL データベース サーバーが見つかりません。", "sql.migration.no.sqldatabase.found": "Azure SQL データベースが見つかりません。", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Azure Virtual Machine 上で SQL Server への移行に関する問題は見つかりませんでした。", "sql.migration.no.location.found": "場所が見つかりません。", "sql.migration.no.managedInstance.found": "マネージド インスタンスが見つかりません。", + "sql.ir.no.node.found": "ノードが見つかりません", "sql.migration.no.pending.backups": "保留中のバックアップはありません。[最新の情報に更新] をクリックして、現在の状態を確認します。", "sql.migration.cancel.feedback.no.reason.selected": "理由が選択されていません", "sql.migration.wizard.sku.error.noRecommendation": "利用可能なレコメンデーションはありません", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "サブスクリプションが見つかりません。", "sql.migration.select.target.label": "ターゲットが選択されていません。評価の概要を表示するには、ターゲットを選択します。", "sql.migration.no.virtualMachine.found": "仮想マシンが見つかりません。", + "sql.ir.node.name": "ノード名", "sql.migration.restore.status.none": "なし", "sql.migration.restore.backupset.status.none": "なし", "sql.migration.parallel.copy.type.none": "なし", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "準備ができていません", "sql.migration.restore.status.not.started": "未開始", "sql.login.migration.steps.not.started": "未開始", + "sql.ir.recommended.link": "注: セルフホステッド IR の推奨事項を参照してください", "sql.migration.backup.file.number.of.stripes": "ストライプの数", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "OK", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "収集されたオブジェクト", "sql.migration.offline": "オフライン", "sql.migration.database.migration.mode.offline.label": "オフライン移行", + "sql.ir.powershellscript.definition": "PowerShell で実行すると、次に示す一意のスクリプトがダウンロードされ、セルフホステッド統合ランタイムがインストールされ、Azure Database Migration Service に登録されます。ターゲット マシンに PowerShell がインストールされている必要があります。", "sql.migration.online": "オンライン", "sql.migration.database.migration.mode.online.label": "オンライン移行", "sql.migration.open": "開く", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "続行する前に、データベース バックアップ ファイルの場所を選択してください。", "sql.migration.cancel.feedback.reason.container.description": "移行を取り消す理由をお聞かせください。これはエクスペリエンスの向上に役立ちます。", "sql.migration.port.label": "ポート", + "sql.ir.powershell.script.saved": "PowerShell スクリプトが保存されました", + "sql.ir.ps.script.collapsed": "PowerShell スクリプトが折りたたまれています", + "sql.ir.ps.script.expanded": "PowerShell スクリプトが展開されています", "sql.migration.status.prefetchobjects": "プリフェッチ オブジェクト", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "Premium SSD", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "Premium SSD v2", "sql.migration.sku.azureConfiguration.premiumSeries": "Premium シリーズ", "sql.migration.copy.status.preparingforcopy": "準備中", + "sql.ir.powershell.prereq": "前提条件: 管理者特権として実行する PowerShell が必要です。 ", "sql.login.migration.status.page.previous.button.title": "前 (無効)", "sql.migration.tde.migrate.results.heading.previous": "以前の証明書移行の結果:", "sql.migration.provide.unique.containers": "ターゲット データベースごとに一意のコンテナーを指定してください。影響を受けるデータベースは以下のとおりです。", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "ターゲットのログイン リストの更新に失敗しました", "sql.login.migration.refresh.login.data.successful": "ログイン リストの更新に成功しました。ソース ログインが {0} 件、ターゲット ログインが {1} 件見つかりました。", "sql.migration.resourceGroups": "リソース グループ", + "sql.migration.storage.account.resource.group.label": "リソース グループ", "sql.migration.rg.created": "リソース グループが作成されました", "sql.migration.services.resource.group": "Azure Database Migration Service のリソース グループ。", "sql.migration.dms.resource_group": "Azure SQL ターゲット用途のリソース グループ。サービスを含むリソース グループのみが表示されます。", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "SQL ログ ファイル", "sql.migration.sql.assessment.notebook.title": "SQL 移行評価", "sql.migration.sku.sql.temp": "SQL tempdb", + "sql.migration.target.provisioning.save": "保存", + "sql.migration.target.provisioning.title": "テンプレートの保存", "sql.migration.save.close": "保存して閉じる", "sql.migration.save.assessment.report": "評価レポートを保存する", "sql.migration.save.recommendation.report": "推奨事項レポートを保存する", + "sql.ir.save.script": "スクリプトの保存", + "sql.migration.target.upload.to.azure": "Azure BLOB コンテナーに保存する", "sql.migration.saved.assessment.result": "保存されたセッション", "sql.migration.sku.parameters.scale.factor": "倍率:", "sql.migration.schema.data": "スキーマとデータ", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "バックアップの検索", "sql.migration.wizard.troubleshooting": "詳細なトラブルシューティング手順については、https://aka.ms/dms-migrations-troubleshooting のリンクを参照してください。", "sql.migration.select": "選択", + "sql.migration.select.storage.account.title": "Azure Storage アカウントの選択", "sql.migration.select.service.title": "Database Migration Service の選択", "sql.migration.select.service.prompt": "Database Migration Service の選択", "sql.migration.select.service.select.a.service": "Database Migration Service の選択", "sql.migration.invalid.migration.service.offline.error": "ノードに接続された Database Migration Service を選択します。", "sql.migration.status.select.service.MESSAGE": "移行を監視する Database Migration Service を選択します。", + "sql.migration.select.storage.select.a.storage.account": "ストレージ アカウントの選択", "sql.migration.blob.container.select": "最初に BLOB コンテナーの値を選択します。", "sql.migration.sku.import.performance.data.dialog.open.folder": "フォルダーを選択する", "sql.migration.sku.import.performance.data.dialog.helper.message": "ローカル ドライブ上のフォルダーを選択する", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "検証を停止", "sql.migration.sku.azureRecommendation.stop.popup": "パフォーマンス データ収集を停止しています...", "sql.migration.sku.targetStorageConfiguration.storage": "ストレージ", - "sql.migration.storage.account": "ストレージ アカウント", + "sql.migration.select.storage.account.label": "ストレージ アカウント", + "sql.migration.storage.account.details.label": "ストレージ アカウント", "sql.migration.network.share.azure.header": "ストレージ アカウントの詳細", "sql.migration.subscription": "サブスクリプション", "sql.migration.blob.storage.subscription.label": "サブスクリプション", "sql.migration.dms.subscription": "Azure Database Migration Service のサブスクリプション名。", "sql.migration.services.subscription": "Azure Database Migration Service のサブスクリプション名。", "sql.migration.sku.subscription": "Azure SQL ターゲットのサブスクリプション名", + "sql.migration.storage.account.subscription": "ストレージ アカウントのサブスクリプション名", "sql.migration.state.succeeded": "成功", "sql.migration.tde.validation.status.succeeded": "成功", "sql.migration.copy.status.succeeded": "成功", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "ターゲットの種類", "sql.migration.username.label": "ターゲット ユーザー名", "sql.migration.target.version": "ターゲット バージョン", + "sql.migration.target.provisioning.save.template.success": "テンプレートは正常に保存されました", + "sql.migration.target.provisioning.upload.template.success": "テンプレートは正常にアップロードされました", "sql.migration.test.connection": "接続のテスト", "sql.migration.dashboard.help.description.migrateUsingADS": "Azure Data Studio の Azure SQL 移行拡張機能では、アセスメントを実行し、適切なサイズの Azure 推奨事項を取得し、SQL Server データベースを Azure に移行する機能が提供されます。", "sql.migration.sqldb.not.ready": "SQL データベース サーバー '{0}' は現在 '{1}' 状態であるため、移行できません。続行するには、使用可能な SQL データベース サーバーを選択します。", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "ログ バックアップをアップロードしています", "sql.migration.sqldb.column.usedparallelcopies": "並列コピーが使用されました", "sql.migration.path.user.account": "ユーザー アカウント", + "sql.migration.network.share.user.account.label": "ユーザー アカウント", "sql.migration.username": "ユーザー名", + "sql.migration.database.assessment.qds.label": "クエリ データ ストアの使用 (このオプションは Microsoft SQL Server 2016 以降で使用できます)", + "sql.migration.database.assessment.xevents.label": "拡張イベント セッションの使用", "sql.migration.starting.login": "ログインの検証と移行が進行中です", "sql.login.migration.establish.user.mappings": "ログインの検証と移行が完了しました。\r\n\r\nユーザー マッピングを確立しています。", "sql.migration.starting.login.failed": "ログインの検証と移行に失敗しました", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "次のステップを実行しました:", "sql.login.migration.wizard.target.data.migration.warning": "ログイン移行を開始する前に、データベースを Azure SQL ターゲットに移行して、プロセスでエラーが発生しないようにすることをお勧めします。最近移行したデータベースのユーザー マッピングを更新することが目標である場合は、いつでもこの移行プロセスを実行できます。\r\n\r\nソース名とデータベース名が同じでない場合は、一部のアクセス許可が正しく適用されない可能性があります。", "sql.migration.blob.storage.folder.info": "データベースのバックアップを BLOB コンテナーにアップロードする際、異なるデータベースのバックアップ ファイルは必ず異なるフォルダーに保存してください。コンテナーのルートと深さ 1 レベルまでのフォルダーのみがサポートされています。", + "sql.ir.local.ir.setup.note": "'スクリプトの実行' をクリックすると、以下の PowerShell スクリプトによって、セルフホステッド統合ランタイム ソフトウェアが自動的にダウンロードされ、インストールされ、Azure Database Migration Service に登録されます。IR の接続状態を確認するには、前の画面に戻って更新します。 ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "収集したデータをどこに保存しますか?", "sql.migration.network.share.windows.user.label": "ネットワーク共有の場所への読み取り権限のある Windows ユーザー アカウント", "sql.migration.network.share.windows.user.info": "ネットワーク共有の場所への読み取り権限のある Windows ユーザー アカウント。", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Azure Database Migration Service のリソース名。", "sql.migration.sku.resource": "Azure SQL ターゲット リソース名", "sql.migration.sku.resource.port": "Azure SQL ターゲット リソースのポート番号: 0 - 65535", + "sql.migration.storage.account.blob.container": "BLOB コンテナー名", + "sql.migration.storage.account": "ストレージ アカウント名", "sql.migration.pre.req.4": "データベースバックアップの場所の詳細、ネットワーク ファイル共有またはAzure Blob Storageコンテナー (Azure SQL データベース ターゲットには必要ありません)。", "sql.migration.wizard.sku.assessment.error.detail": "[データベース移行の準備状況を確認するための評価結果はありません。このチェックボックスをオンにすることで、データベースを目的の Azure SQL ターゲットに移行することを承認します。]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-ko/CHANGELOG.md b/i18n/ads-language-pack-ko/CHANGELOG.md index 9262727a5f25..d29758aad74c 100644 --- a/i18n/ads-language-pack-ko/CHANGELOG.md +++ b/i18n/ads-language-pack-ko/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-ko" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-ko/package.json b/i18n/ads-language-pack-ko/package.json index c5804e27b22c..51c6e4ff1ef9 100644 --- a/i18n/ads-language-pack-ko/package.json +++ b/i18n/ads-language-pack-ko/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-ko", "displayName": "Korean Language Pack for Azure Data Studio", "description": "Language pack extension for Korean", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-ko/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-ko/translations/extensions/Microsoft.mssql.i18n.json index d9d166127345..12fbcfba3aba 100644 --- a/i18n/ads-language-pack-ko/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-ko/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "파일 그룹", "objectManagement.databaseProperties.filegrowthLimitError": "Filegrowth는 파일의 최대 파일 크기보다 클 수 없습니다.", "objectManagement.databaseProperties.filesText": "파일", - "objectManagement.optionsSectionHeader": "파일", + "objectManagement.filesSectionHeader": "파일", "objectManagement.databaseProperties.filestreamFilesText": "파일 스트림 파일", "objectManagement.filterSectionTitle": "필터", "objectManagement.findText": "찾기", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "작동 모드(실제)", "objectManagement.databaseProperties.requestedOperationModeText": "작동 모드(요청)", "objectManagement.optimizeAdHocWorkloadsLabel": "임시 워크로드 최적화", + "objectManagement.optionsSectionHeader": "옵션", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "원래 파일 이름", "objectManagement.overwriteExistingBackups": "모든 기존 백업 세트 덮어쓰기", "objectManagement.backupOverwriteMedia": "미디어 덮어쓰기", diff --git a/i18n/ads-language-pack-ko/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-ko/translations/extensions/Microsoft.notebook.i18n.json index c51438dc4b08..a7008c9b029b 100644 --- a/i18n/ads-language-pack-ko/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-ko/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "찾아보기", - "configurePython.installationType": "설치 유형", - "configurePython.newInstall": "새 Python 설치", "configurePythyon.noVersionsFound": "지원되는 Python 버전을 찾을 수 없습니다.", "configurePython.descriptionWithoutKernel": "Notebook 커널에서는 Python 런타임을 구성하고 종속성을 설치해야 합니다.", - "configurePython.locationTextBoxText": "Python 설치 위치", - "configurePython.pythonConfigured": "Python 런타임이 구성되었습니다.", + "configurePython.locationTextBoxText": "Python 위치", "configurePython.selectFileLabel": "선택", "configurePython.descriptionWithKernel": "‘{0}’ 커널을 사용하려면 Python 런타임을 구성하고 종속성을 설치해야 합니다.", - "configurePython.existingInstall": "기존 Python 설치 사용", + "configurePythyon.existingInstance": "{0} (현재 Python 인스턴스)", "configurePythyon.customPathLabel": "{0}(사용자 지정)", - "configurePythyon.defaultPathLabel": "{0}(기본값)", "configurePythyon.dropdownPathLabel": "{0}(Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "Notebook 경로는 필수입니다." }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "업데이트를 하기 위해 활성 Python Notebook 세션이 종료됩니다. 지금 계속하시겠습니까?", "msgWaitingForInstall": "현재 다른 Python 설치를 진행 중입니다. 완료될 때까지 기다립니다.", - "msgPythonRunningError": "Python이 실행되는 동안 기존 Python 설치를 덮어쓸 수 없습니다. 계속하기 전에 활성 Notebook을 닫으세요.", - "dontAskAgain": "다시 묻지 않음", - "msgDownloadPython": "{0} 플랫폼용 로컬 python을 {1}(으)로 다운로드하는 중", - "msgPythonDownloadPending": "Python 패키지 다운로드 중", "msgGetPythonUserDirFailed": "Python 사용자 경로를 가져올 때 오류가 발생했습니다. {0}", "msgPackageRetrievalFailed": "설치된 패키지 목록을 검색하는 동안 오류가 발생했습니다. {0}", - "msgPythonDirectoryError": "Python 설치 디렉터리를 만드는 동안 오류가 발생했습니다.", - "msgPythonDownloadError": "Python 설정을 다운로드하는 동안 오류가 발생했습니다.", - "msgPythonUnpackError": "Python 번들 압축을 푸는 동안 오류가 발생했습니다.", "msgTaskName": "Notebook 종속성 설치 중", "msgDependenciesInstallationFailed": "오류: {0}(을) 나타내며 Notebook 종속성 설치에 실패했습니다.", "msgInstallPkgStart": "Notebook 종속성을 설치하는 중입니다. 자세한 내용은 작업 보기를 참조하세요.", - "no": "아니요", "msgInstallPkgFinish": "Notebook 종속성 설치를 완료했습니다.", - "msgInstallPkgProgress": "Notebook 종속성 설치가 진행 중입니다.", - "msgPythonDownloadComplete": "Python 다운로드가 완료되었습니다.", - "msgPythonVersionUpdatePrompt": "이제 python {0}에서 Azure Data Studio를 사용할 수 있습니다. 현재 Python 버전(3.6.6)은 2021년 12월에 지원되지 않습니다. 지금 Python {0}을(를) 업데이트하시겠습니까?", - "msgPythonVersionUpdateWarning": "Python {0}이(가) 설치되고 Python 3.6.6을 대체합니다. 일부 패키지는 더 이상 새 버전과 호환되지 않거나 다시 설치해야 할 수 있습니다. 모든 pip 패키지를 다시 설치하는 데 도움이 되는 전자 필기장이 만들어집니다. 지금 업데이트를 계속하시겠습니까?", - "msgPythonUnpackPending": "Python 패키지 압축을 푸는 중", - "yes": "네" + "msgInstallPkgProgress": "Notebook 종속성 설치가 진행 중입니다." }, "dist/jupyter/jupyterServerManager": { "shutdownError": "Notebook 서버 종료 실패: {0}" diff --git a/i18n/ads-language-pack-ko/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-ko/translations/extensions/Microsoft.sql-migration.i18n.json index f9d4ece1a10c..f89b5f1fb56f 100644 --- a/i18n/ads-language-pack-ko/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-ko/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "중요 업무용 서비스 계층으로의 SQL Managed Instance 마이그레이션 컷오버는 Always On 고가용성 그룹에 대해 3개의 보조 복제본을 시드해야 하기 때문에 범용보다 훨씬 오래 걸릴 수 있습니다. 작업 기간은 데이터 크기에 따라 다릅니다. 90%의 경우 시딩 속도는 220GB/시간 이상입니다.", "sql.migration.dashboard.help.description.dmsGuide": "Azure에서 데이터 자산을 마이그레이션하고 최신화하기 위한 단계별 지침을 제공하는 마이그레이션 문서의 허브입니다.", "sql.migration.resource.group.description": "리소스 그룹은 Azure 솔루션에 대한 관련 리소스를 보유하는 컨테이너입니다.", + "sql.migration.target.provisioning.template.display.limit": "단일 ARM 템플릿에는 최대 50개의 Azure SQL 데이터베이스 배포 제한이 있습니다. 처음 50개의 데이터베이스의 템플릿이 아래에 표시됩니다. 모든 템플릿을 보려면 템플릿 JSON 파일을 로컬 저장소 또는 Azure Blob 저장소에 저장하세요.", "sql.migration.pre.req.2": "온-프레미스 또는 Azure Virtual Machine의 SQL Server 또는 클라우드(프라이빗, 퍼블릭)에서 실행되는 모든 가상 머신에서 실행되는 원본 SQL Server 데이터베이스입니다.", "sql.migration.dashboard.help.description.sqldb": "SQL Server 인스턴스(온-프레미스 또는 Azure Virtual Machines)에서 Azure SQL Database로 데이터베이스를 마이그레이션하는 단계별 자습서입니다.", "sql.migration.dashboard.help.description.mi": "가동 중지 시간을 최소화하면서 SQL Server 인스턴스(온-프레미스 또는 Azure Virtual Machines)에서 Azure SQL Managed Instance로 데이터베이스를 마이그레이션하는 단계별 자습서입니다.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "모든 백업이 복원됨", "sql.migration.view.all": "모든 데이터베이스 마이그레이션", "sql.migration.all.fields.required": "모든 필드가 필수 항목입니다.", + "sql.ir.version.mismatch": "구성하려면 모든 노드가 동일한 버전에 있어야 합니다.", "sql.migration.all.source.tables.empty": "원본 테이블이 모두 비어 있습니다. 데이터 마이그레이션을 위해 선택할 수 있는 테이블이 없습니다. 그러나 대상에 테이블이 없는 경우 스키마 마이그레이션을 사용할 수 있습니다.", "sql.migration.unavailable.source.tables.heading": "아래 테이블이 모두 비어 있습니다. 데이터 마이그레이션을 위해 선택할 수 있는 테이블이 없습니다. 그러나 대상에 테이블이 없는 경우 스키마 마이그레이션을 사용할 수 있습니다.", "sql.migration.missing.tables.heading": "아래 테이블이 모두 대상에 없습니다. 이러한 테이블의 데이터를 마이그레이션하려면 위의 스키마 마이그레이션 옵션을 선택하세요.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "이 마이그레이션을 취소하시겠습니까?", "sql.delete.migration.confirmation": "이 마이그레이션을 삭제하시겠습니까?", "sql.migration.migration.list.ascending.label": "오름차순", - "sql.migration.database.assessment.xevents.title": "확장 이벤트 세션 평가", + "sql.migration.database.assessment.xevents.title": "임시 또는 동적 SQL 평가", "sql.migration.assessed.dbs.label": "평가된 데이터베이스: {0}", "sql.migration.assessment.findings.label": "평가 결과", "sql.migration.assessment.in.progress": "평가 진행 중", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Azure Database Migration Service", "sql.migration.service.ready": "Azure Database Migration Service '{0}'이(가) 노드에서 실행되는 자체 호스팅 통합 런타임에 연결됨 - {1}\r\n\r\n향상된 성능과 고가용성을 위해 추가 노드를 등록할 수 있습니다.", "sql.migration.service.ready.below": "Azure Database Migration Service '{0}'이(가) 노드에서 실행되는 자체 호스팅 통합 런타임에 연결됨 - {1}\r\n\r\n향상된 성능과 고가용성을 위해 추가 노드를 등록할 수 있습니다. 아래에서 등록 지침을 확인하세요.", + "sql.migration.service.ready.without.nodes": "Azure Database Migration Service '{0}'이(가) 다음 노드에서 실행 중인 자체 호스팅 통합 런타임에 연결되어 있습니다.", "sql.migration.service.header": "Azure Database Migration Service \"{0}\" 세부 정보:'", "sql.migration.service.not.ready": "Azure Database Migration Service가 등록되지 않았습니다. Azure Database Migration Service '{0}'를 노드에서 자체 호스팅 통합 런타임에 등록해야 합니다.", "sql.migration.service.not.ready.below": "Azure Database Migration Service가 등록되지 않았습니다. Azure Database Migration Service '{0}'를 노드에서 자체 호스팅 통합 런타임에 등록해야 합니다.\r\n\r\n아래에서 등록 지침을 확인하세요.", + "sql.migration.ir.container.description": "Azure Database Migration Service는 Azure Data Factory의 자체 호스팅 통합 런타임을 활용하여 온-프레미스 네트워크 파일 공유에서 Azure로 백업을 업로드합니다. 이전 페이지의 선택 영역에 따라 자체 호스팅 통합 런타임을 설정해야 합니다.", "sql.migration.service.container.container.description1": "Azure Database Migration Service는 Azure Data Factory의 자체 호스팅 통합 런타임을 활용하여 원본과 대상 간의 연결을 처리하고 온-프레미스 네트워크 파일 공유에서 Azure로 백업을 업로드합니다(해당하는 경우).", "sql.migration.services.name": "Azure Database Migration Service 이름", "sql.migration.ir.page.description": "Azure Database Migration Service는 데이터베이스 마이그레이션 활동을 오케스트레이션하고 진행 상황을 추적합니다. 기존 Database Migration Service를 이전에 생성한 경우 기존 서비스를 선택하거나 아래에서 새로 생성할 수 있습니다.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Azure Database Migration Service의 Azure 지역입니다. 서비스를 포함하는 지역만 표시합니다.", "sql.migration.services.location": "Azure Database Migration Service의 Azure 지역입니다. 대상 Azure SQL과 동일한 지역이어야 합니다.", "sql.migration.sku.location": "Azure SQL 대상의 Azure 지역입니다. 마이그레이션에 적합한 대상을 포함하는 지역만 표시합니다.", + "sql.migration.storage.account.location": "스토리지 계정의 Azure 지역입니다. 스토리지 계정이 포함된 지역만 표시됩니다.", "sql.migration.summary.azure.storage": "Azure Storage", "sql.migration.validate.ir.validation.result.label.storage": "Azure Storage 연결", "sql.migration.summary.azure.storage.subscription": "Azure Storage 구독", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "백업 크기(MB)", "sql.migration.backup.start.time": "백업 시작 시간", "sql.migration.wizard.sku.all": "평가 결과에 따라 온라인 상태의 모든 {0} 데이터베이스를 Azure SQL로 마이그레이션할 수 있습니다.", + "sql.migration.target.provisioning.description": "다음은 권장 대상 SKU에 대한 ARM 스크립트입니다. 스크립트를 템플릿으로 저장할 수 있습니다.", "sql.migration.sku.targetStorageConfiguration.info": "다음은 스토리지 성능 요구 사항을 충족하는 데 필요한 대상 스토리지 구성입니다.", "sql.migration.blob.container.title": "BLOB 컨테이너", "sql.migration.blob.container.label": "Blob 컨테이너 리소스 그룹", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "오류 세부 정보를 보려면 클릭하세요.", "sql.migration.service.details.button.label": "닫기", "sql.migration.close": "닫기", + "sql.migration.target.provisioning.close": "닫기", "sql.migration.sku.azureRecommendation.collectData.method": "지금 성능 데이터 수집", "sql.login.migration.collecting.target.logins.failed": "오류 코드로 대상 로그인을 수집하지 못했습니다. {0}", "sql.migration.status.collectioncompleted": "수집 완료됨", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "모든 백업을 복원하지 않고 컷오버를 완료하면 데이터가 손실될 수 있습니다.", "sql.migration.restore.status.completing.migration": "마이그레이션 완료 중", "sql.migration.save.close.popup": "구성을 저장했습니다. 백그라운드에서 성능 데이터 수집을 계속 실행합니다. 원하는 경우 수집을 중지할 수 있습니다.", + "sql.migration.configure.ir": "통합 런타임 구성", + "sql.ir.configure.manually": "수동으로 구성 ", + "sql.ir.configure.powershellscript": "PowerShell 스크립트를 사용하여 구성 ", "sql.migration.connection.label": "연결", "sql.migration.community.support.description": "Microsoft 커뮤니티와 연결", "sql.migration.wizard.target.connection.error": "연결 오류: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "설명", "sql.migration.details.title": "세부 정보", "sql.migration.details.copied": "세부 정보 복사됨", + "sql.migration.validate.ir.error.message": "{0}에 대한 세부 정보는 필수이며 누락되었습니다.", "sql.migration.field.label.deteected.files": "검색된 파일", "sql.migration.dashboard.description": "SQL Server 인스턴스의 마이그레이션 준비 상태를 확인하고, 권장되는 Azure SQL 대상을 식별하고, SQL Server 인스턴스를 Azure SQL Managed Instance, SQL Server on Azure Virtual Machines 또는 Azure SQL Database로 마이그레이션을 완료합니다.", "sql.migration.restore.backuptype.differentialdatabase": "데이터베이스 차등", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "SQL Server 인스턴스 {0}에 연결하는 데 사용되는 Windows 인증 자격 증명을 입력합니다. 이러한 자격 증명은 SQL Server 인스턴스에 연결하고 유효한 백업 파일을 식별하는 데 사용됩니다.", "sql.migration.source.details.windowAuth.db": "{0} SQL Server 인스턴스에 연결하는 데 사용한 Windows 인증 자격 증명을 입력합니다. 이러한 자격 증명은 자체 호스팅 통합 런타임에서 SQL Server 인스턴스에 연결하는 데 사용됩니다.", "sql.migration.enter.your.sql.cred": "원본 SQL Server 인스턴스에 대한 자격 증명을 입력합니다. 이러한 자격 증명은 데이터베이스를 Azure SQL로 마이그레이션하는 동안 사용됩니다.", + "sql.migration.select.storage.account.heading": "아래 세부 정보를 입력하여 Azure Storage 계정을 선택하고 스크립트를 템플릿으로 저장하세요.", "sql.migration.services.container.description": "새 Azure Database Migration Service를 추가하려면 아래 정보를 입력하세요.", "sql.migration.services.container.description.network": "새 Azure Database Migration Service를 추가하려면 아래에 정보를 입력하세요. 자체 호스팅 통합 런타임을 등록하려면 이전 페이지에서 '내 데이터베이스 백업이 네트워크 공유에 있음'을 선택합니다.", "sql.migration.sku.parameters.text": "권장 사항 매개 변수를 편집하려면 아래에 정보를 입력하세요.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "오류: Azure SQL Managed Instance 인스턴스당 최대 사용자 데이터베이스 {0}개를 지원합니다. 계속 진행하려면 {0}개 이하의 데이터베이스를 선택하세요.", "sql.login.migration.migrate.server.roles.and.set.permissions": "사용자 매핑 설정이 완료되었습니다.\r\n\r\n현재 서버 역할을 마이그레이션하고, 서버 매핑을 설정하고, 권한을 설정하는 중입니다. 이 작업은 시간이 걸릴 수 있습니다.", "sql.login.migration.establish.user.mappings.failed": "사용자 매핑을 설정하지 못 함", + "sql.ir.powershellscript": "스크립트 실행 ", + "sql.ir.executing.powershellscript": "실행이 시작되었으며 열려 있는 PowerShell 창을 모니터링합니다. ", "sql.migration.support.resources.description": "설명서 살펴보기", "sql.migration.tde.wizard.optionads": "내 인증서와 프라이빗 키를 대상으로 내보냅니다.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "{0} 로그인을 {1} '{2}'(으)로 마이그레이션하지 못 함", "sql.migration.notebook.open.error": "마이그레이션 노트북을 열지 못했습니다.", "sql.migration.dms.provision.failed": "데이터베이스 마이그레이션 서비스를 프로비전하지 못했습니다. 몇 분 기다렸다가 다시 시도하세요.", + "sql.migration.target.provisioning.save.template.fail": "ARM 템플릿을 저장하지 못했습니다.", + "sql.migration.target.provisioning.upload.template.fail": "ARM 템플릿을 업로드하지 못했습니다.", "sql.migration.tab.button.feedback.description": "피드백", "sql.migration.tab.button.feedback.label": "피드백", "sql.migration.feedback.issue.title": "마이그레이션 환경에 대한 피드백", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "아래 지침에 따라 자체 호스팅 통합 런타임을 설정합니다.", "sql.migration.database.table.selection.description": "아래의 각 데이터베이스에 대해 편집을 클릭하여 원본에서 대상으로 마이그레이션할 테이블을 선택합니다. 그런 다음 '유효성 검사 실행'을 클릭하여 제공된 구성의 유효성을 검사한 후 다음을 클릭합니다.", "sql.migration.sql.vm.page.blob.info": "SQL Server 2014 이하를 실행하는 대상 서버의 경우 데이터베이스를 백업할 때 네트워크 공유 옵션을 사용하여 업로드하는 대신 Azure Storage Blob 컨테이너에 저장해야 합니다. 또한 블록 Blob은 SQL Server 2016 이상을 실행하는 대상에만 지원되므로 백업 파일을 페이지 Blob으로 저장해야 합니다. 자세한 정보: {0}", - "sql.migration.database.assessment.xevents.description": "선택한 데이터베이스에 대해 확장 이벤트 세션 파일을 선택적으로 제공하여 임시 또는 동적 SQL 쿼리 또는 응용 프로그램 데이터 계층을 통해 시작된 모든 DML 문을 평가합니다. {0}", + "sql.migration.database.assessment.xevents.description": "선택한 데이터베이스에 대해 확장 이벤트 세션 파일을 선택적으로 제공하여 임시 또는 동적 SQL 쿼리 또는 응용 프로그램 데이터 계층을 통해 시작된 모든 DML 문을 평가합니다.", "sql.migration.full.backup.files": "전체 백업 파일", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "범용", + "sql.migration.target.provisioning.generate.template": "템플릿 생성", "sql.migration.status.generatingscript": "스크립트 생성", "sql.migration.status.generatingcompleted": "스크립트 생성 완료", "sql.migration.sku.get.recommendation": "Azure 권장 사항 가져오기", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "제공할 추가 로그 백업이 없음을 확인하고 컷오버를 완료하려고 함을 확인합니다.", "sql.migration.tde.wizard.optionadsconfirm": "인증서에 액세스하기 위해 내 자격 증명을 사용하는 데 동의합니다.", "sql.migration.tde.wizard.optionmanual": "이미 인증서와 프라이빗 키를 대상으로 마이그레이션했습니다.", + "sql.ir.local.ir.definition": "내 로컬 컴퓨터가 아닌 다른 Windows 컴퓨터에서 자체 호스팅 통합 런타임을 설정하려고 합니다.", "sql.migration.sku.io.memory.requirement": "IO 대기 시간 요구 사항", + "sql.ir.ip.address": "IP 주소", + "sql.ir.config.type": "IR 구성 유형", + "sql.ir.ir.version": "IR 버전", "sql.migration.empty.table.subtext": "결과가 예상되는 경우 SQL Server 인스턴스에 대한 연결을 확인하세요.", "sql.migration.wizard.cancel.reason.others.input.box.note": "기타를 선택한 경우 간단히 메모해 주세요.", "sql.migration.impact": "영향", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "평가를 Azure SQL로 가져오기", "sql.migration.sku.import.performance.data": "성능 데이터 가져오기", "sql.migration.sku.import.performance.data.dialog.description": "Data Migration Assistant를 사용하여 이미 수집한 경우 기존 폴더에서 이 데이터 파일을 가져옵니다.", + "sql.ir.important": "중요", "sql.migration.database.migration.migration.mode.tool.tip": "Azure Database Migration Service에서 오프라인 또는 온라인 상태일 때 데이터베이스를 마이그레이션할 수 있습니다. 오프라인 마이그레이션에서는 마이그레이션이 시작될 때 애플리케이션 가동 중지 시간이 시작됩니다. 가동 중지 시간을 마이그레이션 후 새 환경으로 컷오버하는 데 걸리는 시간으로 제한하려면 온라인 마이그레이션을 사용하세요.", "sql.migration.tde.validation.requirements.message": "인증서 마이그레이션이 성공하려면 아래 나열된 모든 요구 사항을 충족해야 합니다.\r\n\r\n\"유효성 검사 실행\"을 클릭하여 요구 사항을 충족하는지 확인하세요.", "sql.migration.copy.status.inprogress": "진행 중", @@ -484,6 +506,8 @@ "sql.login.migration.type": "로그인 유형", "sql.migration.sku.logs.iops.requirement": "로그 IOPS 요구 사항", "sql.migration.field.label.mi.restore.state": "관리되는 인스턴스 복원 상태", + "sql.ir.manual.ir.collapsed": "수동 IR 구성을 축소함", + "sql.ir.manual.ir.expanded": "수동 IR 구성을 확장함", "sql.migration.map.target.heading": "선택한 원본 데이터베이스를 마이그레이션할 대상 데이터베이스에 매핑", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "메모리 최적화 프리미엄-데이터 계열", "sql.migration.sku.memory.requirement": "메모리 요구 사항", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "새 마이그레이션", "sql.migration.newSupportRequest": "새 지원 요청", "sql.migration.saved.assessment.next": "다음", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "차세대 범용", "sql.migration.no": "아니요", "sql.migration.no.sqldatabaseserver.found": "Azure SQL 데이터베이스 서버를 찾을 수 없습니다.", "sql.migration.no.sqldatabase.found": "Azure SQL 데이터베이스를 찾을 수 없습니다.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Azure Virtual Machine에서 SQL Server로 마이그레이션하는 데 문제가 없습니다.", "sql.migration.no.location.found": "위치를 찾을 수 없음.", "sql.migration.no.managedInstance.found": "관리되는 인스턴스를 찾을 수 없음.", + "sql.ir.no.node.found": "노드를 찾을 수 없음", "sql.migration.no.pending.backups": "보류 중인 백업이 없습니다. 새로 고침을 클릭하여 현재 상태를 확인합니다.", "sql.migration.cancel.feedback.no.reason.selected": "이유 선택 안 함", "sql.migration.wizard.sku.error.noRecommendation": "사용할 수 있는 권장 사항 없음", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "구독을 찾을 수 없음.", "sql.migration.select.target.label": "대상을 선택하지 않았습니다. 평가 요약을 보려면 대상을 선택하세요.", "sql.migration.no.virtualMachine.found": "가상 머신이 없습니다.", + "sql.ir.node.name": "노드 이름", "sql.migration.restore.status.none": "없음", "sql.migration.restore.backupset.status.none": "없음", "sql.migration.parallel.copy.type.none": "없음", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "준비되지 않음", "sql.migration.restore.status.not.started": "시작되지 않음", "sql.login.migration.steps.not.started": "시작되지 않음", + "sql.ir.recommended.link": "참고: 자체 호스팅 IR 권장 사항 참조", "sql.migration.backup.file.number.of.stripes": "스트라이프 수", "sql.migration.offline.caps": "오프라인", "sql.migration.ok": "확인", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "수집된 개체", "sql.migration.offline": "오프라인", "sql.migration.database.migration.mode.offline.label": "오프라인 마이그레이션", + "sql.ir.powershellscript.definition": "PowerShell에서 실행되면 아래 표시된 고유 스크립트가 자체 호스팅 통합 런타임을 다운로드하여 설치하고 Azure Database Migration Service로 등록합니다. 대상 컴퓨터에 PowerShell이 설치되어 있어야 합니다.", "sql.migration.online": "온라인", "sql.migration.database.migration.mode.online.label": "온라인 마이그레이션", "sql.migration.open": "열기", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "계속하기 전에 데이터베이스 백업 파일의 위치를 선택하세요.", "sql.migration.cancel.feedback.reason.container.description": "잠시 시간을 내어 마이그레이션을 취소하는 이유를 알려주세요. 이는 환경을 개선하는 데 도움이 됩니다.", "sql.migration.port.label": "포트", + "sql.ir.powershell.script.saved": "PowerShell 스크립트를 저장함", + "sql.ir.ps.script.collapsed": "Powershell 스크립트를 축소함", + "sql.ir.ps.script.expanded": "Powershell 스크립트를 확장함", "sql.migration.status.prefetchobjects": "개체 프리페치", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "프리미엄 SSD", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "프리미엄 SSD v2", "sql.migration.sku.azureConfiguration.premiumSeries": "프리미엄-데이터 계열", "sql.migration.copy.status.preparingforcopy": "준비 중", + "sql.ir.powershell.prereq": "필수 구성 요소: 관리자 권한으로 실행할 수 있는 PowerShell이 필요합니다. ", "sql.login.migration.status.page.previous.button.title": "이전(사용 안 함)", "sql.migration.tde.migrate.results.heading.previous": "이전 인증서 마이그레이션 결과:", "sql.migration.provide.unique.containers": "각 대상 데이터베이스에 대해 고유한 컨테이너를 제공하세요. 영향을 받는 데이터베이스:", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "대상에서 로그인 목록을 새로 고침 하지 못 함", "sql.login.migration.refresh.login.data.successful": "로그인 목록을 새로 고침 했습니다. 원본 로그인이 {0}을(를) 찾았습니다. 대상 로그인이 {1}을(를) 찾았습니다.", "sql.migration.resourceGroups": "리소스 그룹", + "sql.migration.storage.account.resource.group.label": "리소스 그룹", "sql.migration.rg.created": "리소스 그룹을 만들었습니다.", "sql.migration.services.resource.group": "Azure Database Migration Service의 리소스 그룹입니다.", "sql.migration.dms.resource_group": "Azure SQL 대상의 리소스 그룹입니다. 서비스를 포함하는 리소스 그룹만 표시합니다.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "SQL 로그 파일", "sql.migration.sql.assessment.notebook.title": "SQL 마이그레이션 평가", "sql.migration.sku.sql.temp": "SQL tempdb", + "sql.migration.target.provisioning.save": "저장", + "sql.migration.target.provisioning.title": "템플릿 저장", "sql.migration.save.close": "저장하고 닫기", "sql.migration.save.assessment.report": "평가 보고서 저장", "sql.migration.save.recommendation.report": "권장 사항 보고서 저장", + "sql.ir.save.script": "스크립트 저장", + "sql.migration.target.upload.to.azure": "Azure Blob 컨테이너에 저장", "sql.migration.saved.assessment.result": "저장된 세션", "sql.migration.sku.parameters.scale.factor": "배율", "sql.migration.schema.data": "스키마 및 데이터", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "백업 검색 중", "sql.migration.wizard.troubleshooting": "자세한 문제 해결 단계는 링크: https://aka.ms/dms-migrations-troubleshooting을 참조하세요.", "sql.migration.select": "선택", + "sql.migration.select.storage.account.title": "Azure Storage 계정 선택", "sql.migration.select.service.title": "Database Migration Service 선택", "sql.migration.select.service.prompt": "Database Migration Service 선택", "sql.migration.select.service.select.a.service": "Database Migration Service 선택", "sql.migration.invalid.migration.service.offline.error": "노드에 연결된 Database Migration Service를 선택합니다.", "sql.migration.status.select.service.MESSAGE": "마이그레이션을 모니터링할 Database Migration Service를 선택하세요.", + "sql.migration.select.storage.select.a.storage.account": "스토리지 계정 선택", "sql.migration.blob.container.select": "먼저 Blob 컨테이너 값을 선택합니다.", "sql.migration.sku.import.performance.data.dialog.open.folder": "폴더 선택", "sql.migration.sku.import.performance.data.dialog.helper.message": "로컬 드라이브에서 폴더 선택", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "유효성 검사 중지", "sql.migration.sku.azureRecommendation.stop.popup": "성능 데이터 수집을 중지하는 중...", "sql.migration.sku.targetStorageConfiguration.storage": "스토리지", - "sql.migration.storage.account": "스토리지 계정", + "sql.migration.select.storage.account.label": "스토리지 계정", + "sql.migration.storage.account.details.label": "스토리지 계정", "sql.migration.network.share.azure.header": "스토리지 계정 세부 정보", "sql.migration.subscription": "구독", "sql.migration.blob.storage.subscription.label": "구독", "sql.migration.dms.subscription": "Azure Database Migration Service의 구독 이름", "sql.migration.services.subscription": "Azure Database Migration Service의 구독 이름입니다.", "sql.migration.sku.subscription": "Azure SQL 대상의 구독 이름", + "sql.migration.storage.account.subscription": "스토리지 계정의 구독 이름", "sql.migration.state.succeeded": "성공", "sql.migration.tde.validation.status.succeeded": "성공", "sql.migration.copy.status.succeeded": "성공", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "대상 유형", "sql.migration.username.label": "대상 사용자 이름", "sql.migration.target.version": "대상 버전", + "sql.migration.target.provisioning.save.template.success": "템플릿을 저장했습니다.", + "sql.migration.target.provisioning.upload.template.success": "템플릿을 업로드함", "sql.migration.test.connection": "연결 테스트", "sql.migration.dashboard.help.description.migrateUsingADS": "Azure Data Studio용 Azure SQL 마이그레이션 확장은 Azure 권장 사항을 평가하고, 적합한 크기를 구하며, SQL Server 데이터베이스를 Azure로 마이그레이션하는 기능을 제공합니다.", "sql.migration.sqldb.not.ready": "SQL 데이터베이스 서버 '{0}'은(는) 현재 '{1}' 상태이므로 마이그레이션에 사용할 수 없습니다. 계속하려면 사용 가능한 SQL 데이터베이스 서버를 선택합니다.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "로그 백업 업로드", "sql.migration.sqldb.column.usedparallelcopies": "사용된 병렬 복사본", "sql.migration.path.user.account": "사용자 계정", + "sql.migration.network.share.user.account.label": "사용자 계정", "sql.migration.username": "사용자 이름", + "sql.migration.database.assessment.qds.label": "쿼리 데이터 저장소 사용(이 옵션은 Microsoft SQL Server 2016 이상에서 사용할 수 있음)", + "sql.migration.database.assessment.xevents.label": "확장 이벤트 세션 사용", "sql.migration.starting.login": "로그인을 확인하고 마이그레이션하는 중입니다.", "sql.login.migration.establish.user.mappings": "로그인 확인 및 마이그레이션이 완료되었습니다.\r\n\r\n사용자 매핑을 설정하는 중입니다.", "sql.migration.starting.login.failed": "로그인 확인 및 마이그레이션하지 못 함", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "다음 단계를 실행했습니다:", "sql.login.migration.wizard.target.data.migration.warning": "프로세스의 오류를 방지하기 위해서 로그인 마이그레이션을 시작하기 전에 데이터베이스를 Azure SQL 대상으로 마이그레이션하는 것이 좋습니다. 최근에 마이그레이션된 데이터베이스에 대한 사용자 매핑을 업데이트하는 것이 목표라면 원할 때마다 이 마이그레이션 프로세스를 실행할 수 있습니다.\r\n\r\n원본 이름과 데이터베이스 이름이 같으면 일부 사용 권한이 제대로 적용되지 않을 수 있습니다.", "sql.migration.blob.storage.folder.info": "데이터베이스 백업을 Blob 컨테이너에 업로드할 때 서로 다른 데이터베이스의 백업 파일이 별도의 폴더에 저장되어 있는지 확인하세요. 최대 한 수준 깊이의 컨테이너와 폴더 루트만 지원됩니다.", + "sql.ir.local.ir.setup.note": "'스크립트 실행'을 클릭하면 아래 PowerShell 스크립트가 자동으로 자체 호스팅 통합 런타임 소프트웨어를 다운로드하고 설치한 후 Azure Database Migration Service로 등록합니다. IR의 연결 상태를 확인하려면 이전 화면으로 돌아가서 새로 고치세요. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "수집된 데이터는 어디에 저장하시겠습니까?", "sql.migration.network.share.windows.user.label": "네트워크 공유 위치에 대한 읽기 권한이 있는 Windows 사용자 계정", "sql.migration.network.share.windows.user.info": "네트워크 공유 위치에 대한 읽기 권한이 있는 Windows 사용자 계정입니다.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Azure Database Migration Service 리소스 이름", "sql.migration.sku.resource": "Azure SQL 대상 리소스 이름", "sql.migration.sku.resource.port": "Azure SQL 대상 리소스 포트 번호: 0 - 65535", + "sql.migration.storage.account.blob.container": "Blob 컨테이너 이름", + "sql.migration.storage.account": "스토리지 계정 이름", "sql.migration.pre.req.4": "네트워크 파일 공유 또는 Azure Blob Storage 컨테이너(Azure SQL Database 대상에는 필요하지 않음)인 데이터베이스 백업 위치 세부 정보.", "sql.migration.wizard.sku.assessment.error.detail": "[데이터베이스 마이그레이션 준비 상태의 유효성을 검사하는 평가 결과가 없습니다. 이 확인란을 선택하면 데이터베이스를 원하는 Azure SQL 대상으로 계속 마이그레이션할 수 있습니다.]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-pt-BR/CHANGELOG.md b/i18n/ads-language-pack-pt-BR/CHANGELOG.md index 2a66a73740f4..2cebd28bd998 100644 --- a/i18n/ads-language-pack-pt-BR/CHANGELOG.md +++ b/i18n/ads-language-pack-pt-BR/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-pt_BR" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-pt-BR/package.json b/i18n/ads-language-pack-pt-BR/package.json index 6afcc4b71889..584e7f810aa7 100644 --- a/i18n/ads-language-pack-pt-BR/package.json +++ b/i18n/ads-language-pack-pt-BR/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-pt-br", "displayName": "Portuguese (Brazil) Language Pack for Azure Data Studio", "description": "Language pack extension for Portuguese (Brazil)", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.mssql.i18n.json index d289fba9e28f..6bbcc41c4da5 100644 --- a/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "Grupos de arquivos", "objectManagement.databaseProperties.filegrowthLimitError": "O aumento do arquivo não pode ser maior que o tamanho máximo do arquivo de um arquivo", "objectManagement.databaseProperties.filesText": "Arquivos", - "objectManagement.optionsSectionHeader": "Arquivos", + "objectManagement.filesSectionHeader": "Arquivos", "objectManagement.databaseProperties.filestreamFilesText": "Arquivos do fluxo de arquivos", "objectManagement.filterSectionTitle": "Filtros", "objectManagement.findText": "Encontrar", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "Modo de operação (real)", "objectManagement.databaseProperties.requestedOperationModeText": "Modo de operação (solicitado)", "objectManagement.optimizeAdHocWorkloadsLabel": "Otimizar cargas de trabalho Ad Hoc", + "objectManagement.optionsSectionHeader": "Opções", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "Nome do Arquivo Original", "objectManagement.overwriteExistingBackups": "Substituir todos os conjuntos de backup existentes", "objectManagement.backupOverwriteMedia": "Substituir mídia", diff --git a/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.notebook.i18n.json index 83acfcc6c70f..76aebe8167df 100644 --- a/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "Procurar", - "configurePython.installationType": "Tipo de Instalação", - "configurePython.newInstall": "Nova instalação do Python", "configurePythyon.noVersionsFound": "Não foram encontradas versões do Python com suporte.", "configurePython.descriptionWithoutKernel": "Os kernels do Notebook exigem que o runtime do Python seja configurado e as dependências sejam instaladas.", - "configurePython.locationTextBoxText": "Localização da Instalação do Python", - "configurePython.pythonConfigured": "Runtime do Python configurado.", + "configurePython.locationTextBoxText": "Local do Python", "configurePython.selectFileLabel": "Selecionar", "configurePython.descriptionWithKernel": "O kernel '{0}' exige que um runtime do Python seja configurado e as dependências sejam instaladas.", - "configurePython.existingInstall": "Usar a instalação existente do Python", + "configurePythyon.existingInstance": "{0} (Instância Atual do Python)", "configurePythyon.customPathLabel": "{0} (Personalizado)", - "configurePythyon.defaultPathLabel": "{0} (Padrão)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "É necessário um caminho de notebook" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "As sessões ativas do bloco de anotações do Python serão encerradas para serem atualizadas. Deseja continuar agora?", "msgWaitingForInstall": "Outra instalação do Python está em andamento no momento. Esperando a conclusão.", - "msgPythonRunningError": "Não é possível substituir uma instalação do Python existente enquanto o Python está em execução. Feche todos os notebooks ativos antes de prosseguir.", - "dontAskAgain": "Não perguntar novamente", - "msgDownloadPython": "Baixando o Python local para a plataforma: {0} a {1}", - "msgPythonDownloadPending": "Baixando o pacote Python", "msgGetPythonUserDirFailed": "Foi encontrado um erro ao obter o caminho do usuário do Python: {0}", "msgPackageRetrievalFailed": "Foi encontrado um erro ao tentar recuperar a lista de pacotes instalados: {0}", - "msgPythonDirectoryError": "Erro ao criar o diretório de instalação do Python", - "msgPythonDownloadError": "Erro ao baixar a configuração do Python", - "msgPythonUnpackError": "Erro ao descompactar o pacote Python", "msgTaskName": "Instalando as dependências do Notebook", "msgDependenciesInstallationFailed": "Falha na instalação das dependências do Notebook com o erro: {0}", "msgInstallPkgStart": "Instalando as dependências do Notebook. Confira a exibição Tarefas para obter mais informações", - "no": "Não", "msgInstallPkgFinish": "A instalação das dependências do Notebook está concluída", - "msgInstallPkgProgress": "A instalação de dependências do Notebook está em andamento", - "msgPythonDownloadComplete": "O download do Python está concluído", - "msgPythonVersionUpdatePrompt": "O Python {0} agora está disponível no Azure Data Studio. A versão atual do Python (3.6.6) estará sem suporte em dezembro de 2021. Deseja atualizar para o Python {0} agora?", - "msgPythonVersionUpdateWarning": "O Python {0} será instalado e substituirá o Python 3.6.6. Alguns pacotes podem não ser mais compatíveis com a nova versão ou talvez precisem ser reinstalados. Um bloco de anotações será criado para ajudá-lo a reinstalar todos os pacotes pip. Deseja continuar com a atualização agora?", - "msgPythonUnpackPending": "Descompactando o pacote Python", - "yes": "Sim" + "msgInstallPkgProgress": "A instalação de dependências do Notebook está em andamento" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "Falha no desligamento do servidor do Notebook: {0}" diff --git a/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.sql-migration.i18n.json index 2949d7fe5667..c7bd02dbeb66 100644 --- a/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-pt-BR/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "Uma substituição de migração de Instância Gerenciada de SQL para a camada de serviço Comercialmente Crítico pode levar muito mais tempo do que a de Uso Geral, pois três réplicas secundárias devem ser propagadas para o grupo de Alta Disponibilidade Always On. A duração da operação depende do tamanho dos dados. A velocidade de propagação em 90% dos casos é de 220 GB/hora ou superior.", "sql.migration.dashboard.help.description.dmsGuide": "Um hub de artigos de migração que fornece orientações passo a passo para migrar e modernizar seus ativos de dados no Azure.", "sql.migration.resource.group.description": "Um grupo de recursos é um contêiner que armazena recursos relacionados para uma solução do Azure.", + "sql.migration.target.provisioning.template.display.limit": "Um único modelo do ARM tem uma limitação de implantação de no máximo 50 bancos de dados SQL do Azure. O modelo para os primeiros 50 bancos de dados é exibido abaixo. Para exibir todos os modelos, salve o arquivo JSON de modelo em um armazenamento local ou Armazenamento de Blobs do Azure.", "sql.migration.pre.req.2": "Uma fonte de bancos de dados SQL Server em execução no local ou no SQL Server na Máquina Virtual do Azure ou em qualquer máquina virtual em execução na nuvem (privada, pública).", "sql.migration.dashboard.help.description.sqldb": "Um tutorial passo a passo para migrar bancos de dados de uma instância do SQL Server (no local ou Máquinas Virtuais do Microsoft Azure) para o Banco de Dados SQL do Azure.", "sql.migration.dashboard.help.description.mi": "Um tutorial passo a passo para migrar bancos de dados de uma instância do SQL Server (local ou Máquinas Virtuais do Azure) para a Instância Gerenciada de SQL do Azure com tempo de inatividade mínimo.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "Todos os backups restaurados", "sql.migration.view.all": "Todas as migrações de banco de dados", "sql.migration.all.fields.required": "Todos os campos são obrigatórios.", + "sql.ir.version.mismatch": "Todos os nós devem estar na mesma versão para serem configurados", "sql.migration.all.source.tables.empty": "Todas as tabelas de destino estão vazias. Nenhuma tabela está disponível para seleção para migração de dados. Mas eles estão disponíveis para migração de esquema se não existirem no destino.", "sql.migration.unavailable.source.tables.heading": "Todas as tabelas abaixo estão vazias. Nenhuma tabela está disponível para seleção para migração de dados. Mas se eles não existirem no destino, a migração de esquema estará disponível.", "sql.migration.missing.tables.heading": "Todas as tabelas abaixo estão ausentes no destino. Para migrar os dados nessas tabelas, selecione a opção de migração de esquema acima.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "Tem certeza de que deseja cancelar esta migração?", "sql.delete.migration.confirmation": "Tem certeza de que deseja excluir esta migração?", "sql.migration.migration.list.ascending.label": "Crescente", - "sql.migration.database.assessment.xevents.title": "Avaliar sessões de eventos estendidos", + "sql.migration.database.assessment.xevents.title": "Avaliar SQL ad hoc ou dinâmico", "sql.migration.assessed.dbs.label": "Bancos de dados avaliados: {0}", "sql.migration.assessment.findings.label": "Resultados da avaliação", "sql.migration.assessment.in.progress": "Avaliação em andamento", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Serviço de Migração de Banco de Dados do Azure", "sql.migration.service.ready": "O Serviço de Migração de Banco de Dados do Azure “{0}” está conectado ao runtime de integração auto-hospedado em execução no(s) nó(s) – {1}\r\n\r\nPara melhorar o desempenho e alta disponibilidade, você pode registrar nós adicionais.", "sql.migration.service.ready.below": "O Serviço de Migração de Banco de Dados do Azure “{0}” está conectado ao runtime de integração auto-hospedado em execução no(s) nó(s) – {1}\r\n\r\nPara melhorar o desempenho e a alta disponibilidade, você pode registrar nós adicionais. Confira abaixo as instruções de registro.", + "sql.migration.service.ready.without.nodes": "O Serviço de Migração de Banco de Dados do Azure ''{0}'' está conectado ao runtime de integração auto-hospedada em execução nos nós a seguir", "sql.migration.service.header": "Detalhes do Serviço de Migração de Banco de Dados do Azure \"{0}\": `", "sql.migration.service.not.ready": "O Serviço de Migração de Banco de Dados do Azure não está registrado. O Serviço de Migração de Banco de Dados do Azure '{0}' precisa ser registrado com o runtime de integração auto-hospedada em qualquer nó.", "sql.migration.service.not.ready.below": "O Serviço de Migração de Banco de Dados do Azure não está registrado. O Serviço de Migração de Banco de Dados do Azure “{0}” precisa ser registrado com o runtime de integração auto-hospedado em qualquer nó.\r\n\r\nConfira abaixo as instruções de registro.", + "sql.migration.ir.container.description": "O Serviço de Migração de Banco de Dados do Azure aproveita o Runtime de Integração auto-hospedada do Azure Data Factory para carregar backups do compartilhamento de arquivo de rede local para o Azure. Com base nas seleções na página anterior, você precisará configurar uma página de Runtime de integração auto-hospedada.", "sql.migration.service.container.container.description1": "O Serviço de Migração de Banco de Dados do Azure aproveita o runtime de integração auto-hospedada do Azure Data Factory para lidar com a conectividade entre a origem e o destino e carregar backups de um compartilhamento de arquivos de rede local para o Azure (se aplicável).", "sql.migration.services.name": "Nome do Serviço de Migração de Banco de Dados do Azure.", "sql.migration.ir.page.description": "O Serviço de Migração de Banco de Dados do Azure orquestra as atividades de migração de banco de dados e acompanha seu progresso. Você pode selecionar um Serviço de Migração de Banco de Dados existente se você já criou um anteriormente, ou criar um novo abaixo.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Região do Azure para seu Serviço de Migração de Banco de Dados do Azure. Somente as regiões que contêm um serviço serão mostradas.", "sql.migration.services.location": "Região do Azure para seu Serviço de Migração de Banco de Dados do Azure. Essa deve ser a mesma região que o SQL do Azure de destino.", "sql.migration.sku.location": "Região do Azure para seu destino SQL do Azure. Somente as regiões que contêm um destino qualificado para migração serão mostradas.", + "sql.migration.storage.account.location": "Região do Azure para sua Conta de Armazenamento. Somente as regiões que contêm uma conta de armazenamento serão mostradas.", "sql.migration.summary.azure.storage": "Armazenamento do Azure", "sql.migration.validate.ir.validation.result.label.storage": "Conectividade de armazenamento do Azure", "sql.migration.summary.azure.storage.subscription": "Assinatura de armazenamento do Azure", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "Tamanho do Backup (MB)", "sql.migration.backup.start.time": "Hora de início do backup", "sql.migration.wizard.sku.all": "Com base nos resultados da avaliação, todos os {0} de seus bancos de dados em um estado online podem ser migrados para o SQL do Azure.", + "sql.migration.target.provisioning.description": "Abaixo está o script ARM para o SKU de destino recomendado. Você pode salvar o script como modelo.", "sql.migration.sku.targetStorageConfiguration.info": "Abaixo está a configuração de armazenamento de destino necessária para atender suas necessidades de desempenho de armazenamento.", "sql.migration.blob.container.title": "Contêiner de blob", "sql.migration.blob.container.label": "Grupo de recursos de contêiner de blob", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "Clique para exibir os detalhes do erro", "sql.migration.service.details.button.label": "Fechar", "sql.migration.close": "Fechar", + "sql.migration.target.provisioning.close": "Fechar", "sql.migration.sku.azureRecommendation.collectData.method": "Coletar dados de desempenho agora", "sql.login.migration.collecting.target.logins.failed": "Falha ao coletar o logon de destino com o código de erro {0}", "sql.migration.status.collectioncompleted": "Coleta concluída", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "Concluir a substituição sem restaurar todos os backups pode resultar em perda de dados.", "sql.migration.restore.status.completing.migration": "Concluindo a migração", "sql.migration.save.close.popup": "Configuração salva. A coleta de dados de desempenho permanecerá em execução em segundo plano. Você pode parar a coleta quando quiser.", + "sql.migration.configure.ir": "Configurar o Integration Runtime", + "sql.ir.configure.manually": "Configurar manualmente ", + "sql.ir.configure.powershellscript": "Configurar usando o script do PowerShell ", "sql.migration.connection.label": "Conectar", "sql.migration.community.support.description": "Conecte-se com a Microsoft Community", "sql.migration.wizard.target.connection.error": "Erro de conexão: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "Descrição", "sql.migration.details.title": "Detalhes", "sql.migration.details.copied": "Detalhes copiados", + "sql.migration.validate.ir.error.message": "Os detalhes para {0} são obrigatórios e estão ausentes.", "sql.migration.field.label.deteected.files": "Arquivos detectados", "sql.migration.dashboard.description": "Determine a prontidão da migração de suas instâncias do SQL Server, identifique um destino de SQL do Azure recomendado e conclua a migração da sua instância do SQL Server para a Instância Gerenciada de SQL do Azure, SQL Server em Máquinas Virtuais do Azure ou Banco de Dados SQL do Azure.", "sql.migration.restore.backuptype.differentialdatabase": "Banco de dados diferencial", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "Insira as credenciais de Autenticação do Windows usadas para se conectar à Instância do SQL Server {0}. Essas credenciais serão usadas para se conectar à instância do SQL Server e identificar arquivos de backup válidos.", "sql.migration.source.details.windowAuth.db": "Insira as credenciais de autenticação do Windows usadas para conectar-se à instância do SQL Server {0}. Essas credenciais serão usadas para se conectar à instância do SQL Server a partir do runtime de integração auto-hospedada.", "sql.migration.enter.your.sql.cred": "Insira as credenciais para a Instância do SQL Server de origem. Essas credenciais serão usadas ao migrar bancos de dados para o SQL do Azure.", + "sql.migration.select.storage.account.heading": "Insira os detalhes abaixo para selecionar a conta de Armazenamento do Azure e salvar o script como modelo", "sql.migration.services.container.description": "Insira as informações abaixo para adicionar um novo Serviço de Migração de Banco de Dados do Azure.", "sql.migration.services.container.description.network": "Insira as informações abaixo para adicionar um novo Serviço de Migração de Banco de Dados do Azure. Para registrar o runtime de integração auto-hospedada, selecione “Meus backups de banco de dados estão em um compartilhamento de rede” na página anterior.", "sql.migration.sku.parameters.text": "Insira as informações abaixo para editar os parâmetros de recomendação.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "Erro: A Instância Gerenciada de SQL do Azure dá suporte a no máximo {0} bancos de dados de usuários por instância. Selecione {0} ou menos bancos de dados para prosseguir.", "sql.login.migration.migrate.server.roles.and.set.permissions": "O estabelecimento de mapeamentos de usuários foi concluído.\r\n\r\nAtualmente, migrando as funções de servidor, estabelecendo mapeamentos de servidores e definindo permissões. Isso levará algum tempo.", "sql.login.migration.establish.user.mappings.failed": "Ocorreu um erro ao estabelecer os mapeamentos de usuários", + "sql.ir.powershellscript": "Executar script ", + "sql.ir.executing.powershellscript": "A execução foi iniciada e o monitor da janela do PowerShell foi aberto. ", "sql.migration.support.resources.description": "Explorar a documentação", "sql.migration.tde.wizard.optionads": "Exporte meus certificados e minha chave privada para o destino.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "Ocorreu um erro ao migrar {0} logons para {1} '{2}'", "sql.migration.notebook.open.error": "Falha ao abrir o bloco de anotações de migração.", "sql.migration.dms.provision.failed": "Falha ao provisional um Serviço de Migração de Banco de Dados. Aguarde alguns minutos e tente novamente.", + "sql.migration.target.provisioning.save.template.fail": "Falha ao salvar o Modelo ARM", + "sql.migration.target.provisioning.upload.template.fail": "Falha ao carregar o Modelo ARM", "sql.migration.tab.button.feedback.description": "Comentários", "sql.migration.tab.button.feedback.label": "Comentários", "sql.migration.feedback.issue.title": "Comentários sobre a experiência de migração", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "Siga as instruções abaixo para configurar o runtime de integração auto-hospedada.", "sql.migration.database.table.selection.description": "Para cada banco de dados abaixo, clique em Editar para selecionar as tabelas a serem migradas da origem para o destino. Em seguida, antes de clicar em Avançar, valide a configuração fornecida clicando em 'Executar validação'.", "sql.migration.sql.vm.page.blob.info": "Para servidores de destino que executam o SQL Server 2014 ou inferior, você deve armazenar seus backups de banco de dados em um contêiner do Azure Storage Blob em vez de carregá-los usando a opção de compartilhamento de rede. Além disso, você deve armazenar os arquivos de backup como blobs de páginas, pois os blobs de blocos têm suporte apenas para destinos que executam o SQL Server 2016 ou posterior. Saiba mais: {0}", - "sql.migration.database.assessment.xevents.description": "Para os bancos de dados selecionados, opcionalmente, forneça arquivos de sessão de evento estendido para avaliar consultas ad hoc ou SQL dinâmicas ou quaisquer instruções DML iniciadas pela camada de dados do aplicativo. {0}", + "sql.migration.database.assessment.xevents.description": "Para os bancos de dados selecionados, opcionalmente, forneça arquivos de sessão de evento prorrogado para avaliar consultas de SQL ad hoc ou dinâmicas ou quaisquer instruções DML iniciadas por meio da camada de dados do aplicativo.", "sql.migration.full.backup.files": "Arquivo(s) de backup completo(s)", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "Uso geral", + "sql.migration.target.provisioning.generate.template": "Gerar Modelo", "sql.migration.status.generatingscript": "Gerando script", "sql.migration.status.generatingcompleted": "Geração de script concluída", "sql.migration.sku.get.recommendation": "Obter recomendações do Azure", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "Confirmo que não há backups de log adicionais para fornecer e desejo concluir a substituição.", "sql.migration.tde.wizard.optionadsconfirm": "Eu dou consentimento para usar minhas credenciais para acessar os certificados.", "sql.migration.tde.wizard.optionmanual": "Já migrei meus certificados e chaves privadas para o destino.", + "sql.ir.local.ir.definition": "Quero configurar o runtime de integração auto-hospedada em outro computador Windows que não seja meu computador local.", "sql.migration.sku.io.memory.requirement": "Requisitos de latência de E/S", + "sql.ir.ip.address": "Endereço IP", + "sql.ir.config.type": "Tipo de configuração de IR", + "sql.ir.ir.version": "Versão do IR", "sql.migration.empty.table.subtext": "Para atingir os resultados esperados, verifique a conexão com a Instância do SQL Server.", "sql.migration.wizard.cancel.reason.others.input.box.note": "Se você selecionou outras pessoas, escreva uma breve nota.", "sql.migration.impact": "Impacto", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "Importar avaliação para SQL do Azure", "sql.migration.sku.import.performance.data": "Importar dados de desempenho", "sql.migration.sku.import.performance.data.dialog.description": "Importe esse arquivo de dados de uma pasta existente, se você já o tiver coletado usando o Assistente de Migração de Dados.", + "sql.ir.important": "Importante", "sql.migration.database.migration.migration.mode.tool.tip": "No Serviço de Migração de Banco de Dados do Azure, você pode migrar seus bancos de dados offline ou enquanto estiverem online. Em uma migração offline, o tempo de inatividade do aplicativo começa quando a migração é iniciada. Para limitar o tempo de inatividade ao tempo que leva para mudar para o novo ambiente após a migração, use uma migração online.", "sql.migration.tde.validation.requirements.message": "Para que a migração de certificado seja bem-sucedida, você deve atender a todos os requisitos listados abaixo.\r\n\r\nClique em \"Executar validação\" para verificar se os requisitos foram atendidos.", "sql.migration.copy.status.inprogress": "Em andamento", @@ -484,6 +506,8 @@ "sql.login.migration.type": "Tipo de logon", "sql.migration.sku.logs.iops.requirement": "Requisito de IOPS de registros", "sql.migration.field.label.mi.restore.state": "Estado de restauração da instância gerenciada", + "sql.ir.manual.ir.collapsed": "Configuração de IR manual recolhida", + "sql.ir.manual.ir.expanded": "Configuração de IR manual expandida", "sql.migration.map.target.heading": "Mapeie os bancos de dados de origem selecionados para os bancos de dados de destino", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "Série premium otimizada para memória", "sql.migration.sku.memory.requirement": "Requisito de Memória", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "Nova migração", "sql.migration.newSupportRequest": "Nova solicitação de suporte", "sql.migration.saved.assessment.next": "Próximo", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "Dados de próxima geração Uso Geral", "sql.migration.no": "Não", "sql.migration.no.sqldatabaseserver.found": "Nenhum servidor de banco de dados SQL do Azure foi encontrado.", "sql.migration.no.sqldatabase.found": "Nenhum banco de dados SQL do Azure foi encontrado.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Nenhum problema encontrado para a migração para o SQL Server na Máquina Virtual do Azure.", "sql.migration.no.location.found": "Nenhum local encontrado.", "sql.migration.no.managedInstance.found": "Nenhuma instância gerenciada encontrada.", + "sql.ir.no.node.found": "Nenhum nó encontrado", "sql.migration.no.pending.backups": "Nenhum backup pendente. Clique em Atualizar para verificar o status atual.", "sql.migration.cancel.feedback.no.reason.selected": "Nenhum motivo selecionado", "sql.migration.wizard.sku.error.noRecommendation": "Nenhuma recomendação disponível", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "Nenhuma assinatura encontrada.", "sql.migration.select.target.label": "Nenhum alvo selecionado. Selecione o alvo para exibir o resumo da avaliação.", "sql.migration.no.virtualMachine.found": "Nenhuma máquina virtual encontrada.", + "sql.ir.node.name": "Nome do nó", "sql.migration.restore.status.none": "Nenhum", "sql.migration.restore.backupset.status.none": "Nenhum", "sql.migration.parallel.copy.type.none": "Nenhum", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "Não está pronto", "sql.migration.restore.status.not.started": "Não foi iniciado", "sql.login.migration.steps.not.started": "Não iniciado", + "sql.ir.recommended.link": "Observação: consulte as recomendações de IR auto-hospedado", "sql.migration.backup.file.number.of.stripes": "Número de faixas", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "OK", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "Objetos coletados", "sql.migration.offline": "Off-line", "sql.migration.database.migration.mode.offline.label": "Migração offline", + "sql.ir.powershellscript.definition": "Depois de executado no PowerShell, o script exclusivo mostrado abaixo será baixado, instalará o runtime de integração auto-hospedada e o registrará com o Serviço de Migração de Banco de Dados do Azure. Você precisará ter o PowerShell instalado no computador de destino.", "sql.migration.online": "On-line", "sql.migration.database.migration.mode.online.label": "Migração online", "sql.migration.open": "Abrir", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "Selecione o local dos arquivos de backup do banco de dados antes de continuar.", "sql.migration.cancel.feedback.reason.container.description": "Reserve um momento para nos dizer o motivo do cancelamento da migração. Isso nos ajudará a melhorar a experiência.", "sql.migration.port.label": "Porta", + "sql.ir.powershell.script.saved": "Script do PowerShell salvo", + "sql.ir.ps.script.collapsed": "Script do PowerShell recolhido", + "sql.ir.ps.script.expanded": "Script do PowerShell expandido", "sql.migration.status.prefetchobjects": "Pré-buscar objetos", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "SSD Premium", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "SSD Premium v2", "sql.migration.sku.azureConfiguration.premiumSeries": "Série Premium", "sql.migration.copy.status.preparingforcopy": "Preparando", + "sql.ir.powershell.prereq": "Pré-requisito: é necessário ter o PowerShell com privilégios de execução como administrador. ", "sql.login.migration.status.page.previous.button.title": "Anterior (Desabilitado)", "sql.migration.tde.migrate.results.heading.previous": "Resultados anteriores da migração de certificados:", "sql.migration.provide.unique.containers": "Forneça um contêiner exclusivo para cada banco de dados de destino. Banco de dados afetados: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "Ocorreu um erro ao atualizar a lista de logons de destino", "sql.login.migration.refresh.login.data.successful": "A atualização da lista de logons foi bem-sucedida. {0} Logons de origem encontrados, {1} Logons de destino encontrados", "sql.migration.resourceGroups": "Grupo de recursos", + "sql.migration.storage.account.resource.group.label": "Grupo de recursos", "sql.migration.rg.created": "Grupo de recursos criado", "sql.migration.services.resource.group": "Grupo de recursos para o seu Serviço de Migração de Banco de Dados do Azure.", "sql.migration.dms.resource_group": "Grupo de recursos para seu destino SQL do Azure. somente grupos de recursos que contêm um serviço serão mostrados.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "Arquivos de log do SQL", "sql.migration.sql.assessment.notebook.title": "Avaliação de migração de SQL", "sql.migration.sku.sql.temp": "Tempdb do SQL", + "sql.migration.target.provisioning.save": "Salvar", + "sql.migration.target.provisioning.title": "Salvar Modelo", "sql.migration.save.close": "Salvar e fechar", "sql.migration.save.assessment.report": "Salvar relatório de avaliação", "sql.migration.save.recommendation.report": "Salvar relatório de recomendação", + "sql.ir.save.script": "Salvar script", + "sql.migration.target.upload.to.azure": "Salvar no contêiner de blobs do Azure", "sql.migration.saved.assessment.result": "Sessão salva", "sql.migration.sku.parameters.scale.factor": "Fator de escala:", "sql.migration.schema.data": "Esquema e dados", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "Pesquisando backups", "sql.migration.wizard.troubleshooting": "Confira o link para obter mais etapas de solução de problemas: https://aka.ms/dms-migrations-troubleshooting.", "sql.migration.select": "Selecionar", + "sql.migration.select.storage.account.title": "Selecione a Conta de Armazenamento do Azure", "sql.migration.select.service.title": "Selecionar o Serviço de Migração de Banco de Dados", "sql.migration.select.service.prompt": "Selecionar um Serviço de Migração de Banco de Dados", "sql.migration.select.service.select.a.service": "Selecionar um Serviço de Migração de Banco de Dados", "sql.migration.invalid.migration.service.offline.error": "Selecione um Serviço de Migração de Banco de Dados que esteja conectado a um nó.", "sql.migration.status.select.service.MESSAGE": "Selecione um Serviço de Migração de Banco de Dados para monitorar as migrações.", + "sql.migration.select.storage.select.a.storage.account": "Selecionar uma Conta de Armazenamento", "sql.migration.blob.container.select": "Selecione um valor de contêiner blob primeiro.", "sql.migration.sku.import.performance.data.dialog.open.folder": "Selecionar uma pasta", "sql.migration.sku.import.performance.data.dialog.helper.message": "Selecionar uma pasta na unidade local", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "Parar validação", "sql.migration.sku.azureRecommendation.stop.popup": "Interrompendo a coleta de dados de desempenho...", "sql.migration.sku.targetStorageConfiguration.storage": "Armazenamento", - "sql.migration.storage.account": "Conta de armazenamento", + "sql.migration.select.storage.account.label": "Conta de Armazenamento", + "sql.migration.storage.account.details.label": "Conta de armazenamento", "sql.migration.network.share.azure.header": "Detalhes da conta de armazenamento", "sql.migration.subscription": "Assinatura", "sql.migration.blob.storage.subscription.label": "Assinatura", "sql.migration.dms.subscription": "Nome da assinatura para seu Serviço de Migração de Banco de Dados do Azure", "sql.migration.services.subscription": "Nome da assinatura para o seu Serviço de Migração de Banco de Dados do Azure.", "sql.migration.sku.subscription": "Nome da assinatura para o destino do SQL do Azure", + "sql.migration.storage.account.subscription": "Nome da assinatura da sua Conta de Armazenamento", "sql.migration.state.succeeded": "Com êxito", "sql.migration.tde.validation.status.succeeded": "Bem-sucedido", "sql.migration.copy.status.succeeded": "Com êxito", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "Tipo de destino", "sql.migration.username.label": "Nome do usuário de destino", "sql.migration.target.version": "Versão alvo", + "sql.migration.target.provisioning.save.template.success": "Modelo salvo com êxito", + "sql.migration.target.provisioning.upload.template.success": "Modelo carregado com êxito", "sql.migration.test.connection": "Testar conexão", "sql.migration.dashboard.help.description.migrateUsingADS": "A extensão SQL do Azure Migration para Azure Data Studio fornece recursos para avaliar, obter recomendações do Azure do tamanho certo e migrar bancos de dados do SQL Server para o Azure.", "sql.migration.sqldb.not.ready": "O servidor de banco de dados SQL '{0}' não está disponível para migração porque atualmente está no estado '{1}'. Para continuar, selecione um servidor de banco de dados SQL disponível.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "Carregando backups de log", "sql.migration.sqldb.column.usedparallelcopies": "Cópias paralelas usadas", "sql.migration.path.user.account": "Conta de usuário", + "sql.migration.network.share.user.account.label": "Conta de usuário", "sql.migration.username": "Nome do usuário", + "sql.migration.database.assessment.qds.label": "Usando Repositório de Dados de Consultas (essa opção está disponível para o Microsoft SQL Server 2016 e posterior)", + "sql.migration.database.assessment.xevents.label": "Usando a sessão de evento estendido", "sql.migration.starting.login": "A validação e a migração de logons estão em andamento", "sql.login.migration.establish.user.mappings": "A validação e a migração de logons foram concluídas.\r\n\r\nEstabelecendo os mapeamentos de usuários.", "sql.migration.starting.login.failed": "Ocorreu um erro ao validar e migrar os logons", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "Executamos as seguintes etapas:", "sql.login.migration.wizard.target.data.migration.warning": "Recomendamos migrar seus bancos de dados para o destino do SQL do Azure antes de iniciar a migração de login para evitar falhas no processo. No entanto, você pode executar esse processo de migração sempre que quiser se o seu objetivo for atualizar o mapeamento de usuário para bancos de dados migrados recentemente.\r\n\r\n Se os nomes de origem e banco de dados não forem os mesmos, é possível que algumas permissões não sejam aplicadas adequadamente.", "sql.migration.blob.storage.folder.info": "Ao carregar backups de banco de dados no contêiner de blobs, verifique se os arquivos de backup de bancos de dados diferentes estão armazenados em pastas separadas. Há suporte apenas para a raiz do contêiner e das pastas no máximo um nível de profundidade.", + "sql.ir.local.ir.setup.note": "Quando você clicar em \"executar script\", o script do PowerShell abaixo fará o download automático do software de runtime de integração auto-hospedado, o instalará e o registrará no Serviço de Migração de Banco de Dados do Azure. Para verificar o status da conexão do IR, volte à tela anterior e atualize-a. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "Onde você deseja salvar os dados coletados?", "sql.migration.network.share.windows.user.label": "Conta de usuário do Windows com acesso de leitura ao local de compartilhamento de rede.", "sql.migration.network.share.windows.user.info": "Conta de usuário do Windows com acesso de leitura ao local de compartilhamento de rede.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Seu nome de recurso do Serviço de Migração de Banco de Dados do Azure", "sql.migration.sku.resource": "Seu nome de recurso do SQL do Azure de destino", "sql.migration.sku.resource.port": "Seu número de porta de recurso de destino do SQL do Azure : 0 - 65535", + "sql.migration.storage.account.blob.container": "Nome do SEU Contêiner de Blob", + "sql.migration.storage.account": "Nome da Sua Conta de Armazenamento", "sql.migration.pre.req.4": "Os detalhes do local de backup do seu banco de dados, seja um compartilhamento de arquivos de rede ou um contêiner de Armazenamento de Blobs do Azure (não necessário para destinos de Banco de Dados SQL do Azure).", "sql.migration.wizard.sku.assessment.error.detail": "[Não há resultados de avaliação para validar a preparação da migração do seu banco de dados. Ao marcar esta caixa, você reconhece que deseja continuar migrando seu banco de dados para o destino SQL do Azure desejado.]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-ru/CHANGELOG.md b/i18n/ads-language-pack-ru/CHANGELOG.md index 0ef395ab9214..6e89f68481e1 100644 --- a/i18n/ads-language-pack-ru/CHANGELOG.md +++ b/i18n/ads-language-pack-ru/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-ru" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-ru/package.json b/i18n/ads-language-pack-ru/package.json index 0613ebd6cbed..83fb1b81d8d8 100644 --- a/i18n/ads-language-pack-ru/package.json +++ b/i18n/ads-language-pack-ru/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-ru", "displayName": "Russian Language Pack for Azure Data Studio", "description": "Language pack extension for Russian", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-ru/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-ru/translations/extensions/Microsoft.mssql.i18n.json index 0b92761cad6c..cfadf3c5df44 100644 --- a/i18n/ads-language-pack-ru/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-ru/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "Файловые группы", "objectManagement.databaseProperties.filegrowthLimitError": "Увеличение размера файла не может превышать максимальный размер файла", "objectManagement.databaseProperties.filesText": "Файлы", - "objectManagement.optionsSectionHeader": "Файлы", + "objectManagement.filesSectionHeader": "Файлы", "objectManagement.databaseProperties.filestreamFilesText": "Файлы файлового потока", "objectManagement.filterSectionTitle": "Фильтры", "objectManagement.findText": "Найти", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "Режим работы (фактический)", "objectManagement.databaseProperties.requestedOperationModeText": "Режим работы (запрошенный)", "objectManagement.optimizeAdHocWorkloadsLabel": "Оптимизировать нерегламентированные рабочие нагрузки", + "objectManagement.optionsSectionHeader": "Параметры", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "Исходное имя файла", "objectManagement.overwriteExistingBackups": "Перезаписать все существующие резервные наборы данных", "objectManagement.backupOverwriteMedia": "Перезапись носителя", diff --git a/i18n/ads-language-pack-ru/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-ru/translations/extensions/Microsoft.notebook.i18n.json index 70aac0c03129..e281600683e2 100644 --- a/i18n/ads-language-pack-ru/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-ru/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "Обзор", - "configurePython.installationType": "Тип установки", - "configurePython.newInstall": "Новая установка Python", "configurePythyon.noVersionsFound": "Поддерживаемые версии Python не найдены.", "configurePython.descriptionWithoutKernel": "Для ядер записных книжек требуется настроить среду выполнения Python и установить зависимости.", - "configurePython.locationTextBoxText": "Расположение установки Python", - "configurePython.pythonConfigured": "Среда выполнения Python настроена.", + "configurePython.locationTextBoxText": "Расположение Python", "configurePython.selectFileLabel": "Выбрать", "configurePython.descriptionWithKernel": "Для ядра \"{0}\" требуется настроить среду выполнения Python и установить зависимости.", - "configurePython.existingInstall": "Использовать существующую установку Python", + "configurePythyon.existingInstance": "{0} (текущий экземпляр Python)", "configurePythyon.customPathLabel": "{0} (пользовательский)", - "configurePythyon.defaultPathLabel": "{0} (по умолчанию)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "Требуется путь к записной книжке" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "Сеансы активных записных книжек Python будут завершены, чтобы обновить их. Хотите продолжить?", "msgWaitingForInstall": "Сейчас выполняется другая установка Python. Дождитесь ее завершения.", - "msgPythonRunningError": "Не удается перезаписать существующую установку Python во время работы Python. Прежде чем продолжить, закройте все активные записные книжки.", - "dontAskAgain": "Больше не спрашивать", - "msgDownloadPython": "Скачивание локального Python для платформы: {0} в {1}", - "msgPythonDownloadPending": "Идет скачивание пакета Python", "msgGetPythonUserDirFailed": "Обнаружена ошибка при получении пути пользователя Python: {0}", "msgPackageRetrievalFailed": "Произошла ошибка при попытке получить список установленных пакетов: {0}", - "msgPythonDirectoryError": "Ошибка при создании каталога установки Python", - "msgPythonDownloadError": "Ошибка при скачивании программы установки Python", - "msgPythonUnpackError": "Ошибка при распаковке пакета Python", "msgTaskName": "Идет установка зависимостей Notebook", "msgDependenciesInstallationFailed": "Установка зависимостей Notebook завершилась с ошибкой: {0}", "msgInstallPkgStart": "Идет установка зависимостей Notebook, дополнительные сведения см. в представлении задач", - "no": "Нет", "msgInstallPkgFinish": "Установка зависимостей Notebook завершена", - "msgInstallPkgProgress": "Выполняется установка зависимостей Notebook", - "msgPythonDownloadComplete": "Скачивание Python завершено", - "msgPythonVersionUpdatePrompt": "{0} Python доступна в Azure Data Studio. Текущая версия Python (3.6.6) не поддерживается в декабре 2021. Вы хотите обновить {0} Python сейчас?", - "msgPythonVersionUpdateWarning": "Будет установлен {0} Python, который заменит 3.6.6 Python. Некоторые пакеты могут быть несовместимы с новой версией или требуют переустановки. Будет создана Записная книжка, которая поможет вам переустановить все пакеты PIP. Вы хотите продолжить обновление сейчас?", - "msgPythonUnpackPending": "Распаковка пакета Python", - "yes": "Да" + "msgInstallPkgProgress": "Выполняется установка зависимостей Notebook" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "Сбой при завершении работы сервера Notebook: {0}" diff --git a/i18n/ads-language-pack-ru/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-ru/translations/extensions/Microsoft.sql-migration.i18n.json index 0387ebdf420e..63223b99357f 100644 --- a/i18n/ads-language-pack-ru/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-ru/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "Прямая миграция управляемого экземпляра SQL на критически важный для бизнеса уровень может занять значительно больше времени, чем для уровня общего назначения, поскольку для группы высокого уровня доступности Always On необходимо присвоить начальное значение трем вторичным репликам. Продолжительность этой операции зависит от объема данных. В 90% случаев скорость присвоения начального значения составляет 220 ГБ в час или выше.", "sql.migration.dashboard.help.description.dmsGuide": "Центр статей по миграции, предоставляющий пошаговое руководство по миграции и модернизации ресурсов данных в Azure.", "sql.migration.resource.group.description": "Группа ресурсов — это контейнер, содержащий связанные ресурсы для решения Azure.", + "sql.migration.target.provisioning.template.display.limit": "Для одного шаблона ARM применяется ограничение развертывания, составляющее максимум 50 баз данных SQL Azure. Шаблон для первых 50 баз данных отображается ниже. Чтобы просмотреть все шаблоны, сохраните файл JSON шаблона в локальном хранилище или хранилище BLOB-объектов Azure.", "sql.migration.pre.req.2": "Исходные базы данных SQL Server, работающие в локальной среде, на SQL Server в виртуальной машине Azure или в любой виртуальной машине, работающей в облаке (частном, общедоступном).", "sql.migration.dashboard.help.description.sqldb": "Пошаговый учебник по миграции баз данных с экземпляра SQL Server (локальная среда или Виртуальные машины Azure) в Базу данных SQL Azure.", "sql.migration.dashboard.help.description.mi": "Пошаговый учебник по миграции баз данных с экземпляра SQL Server (локальный или Виртуальные машины Microsoft Azure) в Управляемый экземпляр SQL Azure с минимальным простоем.", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "Все резервные копии восстановлены", "sql.migration.view.all": "Все миграции баз данных", "sql.migration.all.fields.required": "Нужно заполнить все поля.", + "sql.ir.version.mismatch": "Для настройки все узлы должны иметь одинаковую версию", "sql.migration.all.source.tables.empty": "Все исходные таблицы пусты. Нет доступных таблиц для выбора с целью переноса данных. Но они доступны для миграции схемы, если они не существуют в целевом объекте.", "sql.migration.unavailable.source.tables.heading": "Все таблицы ниже пусты. Нет доступных таблиц для выбора с целью переноса данных. Но если они не существуют в целевом объекте, миграция схемы доступна.", "sql.migration.missing.tables.heading": "Все указанные ниже таблицы отсутствуют в целевом объекте. Чтобы перенести данные в эти таблицы, выберите вариант схемы миграции выше.", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "Вы действительно хотите отменить эту миграцию?", "sql.delete.migration.confirmation": "Действительно удалить эту миграцию?", "sql.migration.migration.list.ascending.label": "По возрастанию", - "sql.migration.database.assessment.xevents.title": "Оценка расширенных сеансов событий", + "sql.migration.database.assessment.xevents.title": "Оценка специального или динамического SQL", "sql.migration.assessed.dbs.label": "Оцениваемые базы данных: {0}", "sql.migration.assessment.findings.label": "Результаты оценки", "sql.migration.assessment.in.progress": "Оценка выполняется", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Служба миграции баз данных Azure", "sql.migration.service.ready": "Служба Azure Database Migration Service \"{0}\" подключена к локальной среде выполнения интеграции, работающей на узлах: {1}\r\n\r\nДля улучшения производительности и обеспечения высокой доступности можно зарегистрировать дополнительные узлы.", "sql.migration.service.ready.below": "Служба Azure Database Migration Service \"{0}\" подключена к локальной среде выполнения интеграции, работающей на узлах: {1}\r\n\r\nДля улучшения производительности и обеспечения высокой доступности можно зарегистрировать дополнительные узлы. Инструкции по регистрации см. ниже.", + "sql.migration.service.ready.without.nodes": "Azure Database Migration Service \"{0}\" подключена к локальной среде выполнения интеграции, запущенной на следующем узле или узлах", "sql.migration.service.header": "Сведения Azure Database Migration Service \"{0}\":`", "sql.migration.service.not.ready": "Служба Azure Database Migration Service не зарегистрирована. Azure Database Migration Service \"{0}\" необходимо зарегистрировать в локальной среде выполнения интеграции на любом узле.", "sql.migration.service.not.ready.below": "Служба Azure Database Migration Service не зарегистрирована. Необходимо зарегистрировать Azure Database Migration Service \"{0}\" в локальной среде выполнения интеграции на любом узле.\r\n\r\nИнструкции по регистрации см. ниже.", + "sql.migration.ir.container.description": "Azure Database Migration Service использует локальную среду выполнения интеграции Фабрики данных Azure для отправки резервных копий из общей папки локальной сети в Azure. В зависимости от выбранных на предыдущей странице элементов потребуется настроить локальную среду выполнения интеграции.", "sql.migration.service.container.container.description1": "Azure Database Migration Service использует локальную среду выполнения интеграции Фабрики данных Azure для управления подключением между источником и назначением и для загрузки резервных копий из локальной сетевой папки в Azure (если применимо).", "sql.migration.services.name": "Имя Azure Database Migration Service.", "sql.migration.ir.page.description": "Azure Database Migration Service координирует действия по миграции базы данных и отслеживает их ход выполнения. Вы можете выбрать существующую службу миграции базы данных, если вы уже создали ее ранее, или создать новую ниже.", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Регион Azure для Azure Database Migration Service. Будут показаны только регионы, содержащие службу.", "sql.migration.services.location": "Регион Azure для Azure Database Migration Service. Это должен быть тот же регион, что и целевой экземпляр Azure SQL.", "sql.migration.sku.location": "Регион Azure для целевого Azure SQL. Будут показаны только регионы, в которых есть целевые объекты, подходящие для миграции.", + "sql.migration.storage.account.location": "Регион Azure для учетной записи хранения. Будут показаны только регионы, содержащие учетную запись хранения.", "sql.migration.summary.azure.storage": "Служба хранилища Azure", "sql.migration.validate.ir.validation.result.label.storage": "Подключение к службе хранилища Azure", "sql.migration.summary.azure.storage.subscription": "Подписка на службу хранилища Azure", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "Размер резервной копии (МБ)", "sql.migration.backup.start.time": "Время начала резервного копирования", "sql.migration.wizard.sku.all": "Исходя из результатов оценки, все {0} из ваших баз данных в подключенном состоянии можно перенести в Azure SQL.", + "sql.migration.target.provisioning.description": "Ниже приведен сценарий ARM для рекомендуемого целевого SKU. Сценарий можно сохранить в качестве шаблона.", "sql.migration.sku.targetStorageConfiguration.info": "Ниже приведена целевая конфигурация хранилища, необходимая для выполнения ваших требований к производительности хранилища.", "sql.migration.blob.container.title": "Контейнер BLOB-объектов", "sql.migration.blob.container.label": "Группа ресурсов контейнера BLOB-объектов", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "Щелкните, чтобы просмотреть сведения об ошибке.", "sql.migration.service.details.button.label": "Закрыть", "sql.migration.close": "Закрыть", + "sql.migration.target.provisioning.close": "Закрыть", "sql.migration.sku.azureRecommendation.collectData.method": "Собрать данные производительности", "sql.login.migration.collecting.target.logins.failed": "Сбой получения целевого входа с кодом ошибки {0}", "sql.migration.status.collectioncompleted": "Сбор завершен", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "Завершение прямой миграции без восстановления всех резервных копий может привести к потере данных.", "sql.migration.restore.status.completing.migration": "Завершение миграции", "sql.migration.save.close.popup": "Конфигурация сохранена. Сбор данных производительности будет выполняться в фоновом режиме. Вы можете остановить сбор, когда за хотите.", + "sql.migration.configure.ir": "Настройка среды выполнения интеграции", + "sql.ir.configure.manually": "Настроить вручную ", + "sql.ir.configure.powershellscript": "Настроить с помощью сценария PowerShell ", "sql.migration.connection.label": "Подключиться", "sql.migration.community.support.description": "Обратитесь к сообществу Microsoft", "sql.migration.wizard.target.connection.error": "Ошибка подключения: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "Описание", "sql.migration.details.title": "Сведения", "sql.migration.details.copied": "Сведения скопированы", + "sql.migration.validate.ir.error.message": "Сведения для {0} являются обязательными и отсутствуют.", "sql.migration.field.label.deteected.files": "Обнаруженные файлы", "sql.migration.dashboard.description": "Определите готовность своих экземпляров SQL Server к миграции, определите рекомендуемую цель Azure SQL и завершите миграцию своего экземпляра SQL Server в Управляемый экземпляр SQL Azure, SQL Server на виртуальных машинах Azure или базу данных SQL Azure.", "sql.migration.restore.backuptype.differentialdatabase": "Разностное копирование базы данных", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "Введите учетные данные проверки подлинности Windows, используемые для подключения к экземпляру SQL Server {0}. Эти учетные данные будут использоваться для подключения к экземпляру SQL Server и определения действительных файлов резервных копий.", "sql.migration.source.details.windowAuth.db": "Введите учетные данные проверки подлинности Windows, используемые для подключения к экземпляру SQL Server {0}. Эти учетные данные будут использоваться для подключения к экземпляру SQL Server из локальной среды выполнения интеграции.", "sql.migration.enter.your.sql.cred": "Введите учетные данные для источника экземпляра SQL Server. Эти учетные данные будут использоваться при миграции баз данных в Azure SQL.", + "sql.migration.select.storage.account.heading": "Введите сведения ниже, чтобы выбрать учетную запись службы хранения Azure и сохранить сценарий в качестве шаблона", "sql.migration.services.container.description": "Чтобы добавить новую службу Azure Database Migration Service, введите сведения ниже.", "sql.migration.services.container.description.network": "Введите сведения ниже, чтобы добавить новую службу Azure Database Migration Service. Чтобы зарегистрировать локальную среду выполнения интеграции, выберите \"Мои резервные копии базы данных находятся в сетевой папке\" на предыдущей странице.", "sql.migration.sku.parameters.text": "Введите ниже сведения, чтобы изменить параметры рекомендаций.", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "Ошибка: Управляемый экземпляр SQL Azure поддерживает не более {0} баз данных на экземпляр. Выберите {0} или меньше баз данных, чтобы продолжить.", "sql.login.migration.migrate.server.roles.and.set.permissions": "Установка сопоставлений пользователей завершена.\r\n\r\nВ настоящее время выполняется миграция ролей сервера, установка сопоставлений серверов и настройка разрешений. Это займет некоторое время.", "sql.login.migration.establish.user.mappings.failed": "Сбой установки сопоставлений пользователей", + "sql.ir.powershellscript": "Выполнить сценарий ", + "sql.ir.executing.powershellscript": "Выполнение запущено, окно мониторинга PowerShell открыто. ", "sql.migration.support.resources.description": "Обзор документации", "sql.migration.tde.wizard.optionads": "Экспорт сертификатов и закрытых ключей в целевой объект.", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "Не удалось перенести учетные данные ({0}) в {1} \"{2}\"", "sql.migration.notebook.open.error": "Не удалось открыть записную книжку миграции.", "sql.migration.dms.provision.failed": "Не удалось подготовить Database Migration Service. Подождите несколько минут и повторите попытку.", + "sql.migration.target.provisioning.save.template.fail": "Не удалось сохранить шаблон ARM", + "sql.migration.target.provisioning.upload.template.fail": "Не удалось отправить шаблон ARM", "sql.migration.tab.button.feedback.description": "Отзывы", "sql.migration.tab.button.feedback.label": "Отзывы", "sql.migration.feedback.issue.title": "Отзывы об интерфейсе миграции", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "Настройте локальную среду выполнения интеграции, следуя инструкциям ниже.", "sql.migration.database.table.selection.description": "Для каждой базы данных ниже нажмите кнопку \"Изменить\", чтобы выбрать таблицы для миграции из источника в целевую базу данных. Перед нажатием кнопки \"Далее\" проверьте указанную конфигурацию, нажав кнопку \"Выполнить проверку\".", "sql.migration.sql.vm.page.blob.info": "Для целевых серверов с SQL Server 2014 или более поздней версии необходимо хранить резервные копии баз данных в контейнере Azure Storage Blob, а не отправлять их с помощью сетевой папки. Кроме того, файлы резервных копий должны храниться как страничные BLOB-объекты, так как блочные BLOB-объекты поддерживаются только для целевых объектов с SQL Server 2016 или более поздней версии. Дополнительные сведения: {0}", - "sql.migration.database.assessment.xevents.description": "Для выбранных баз данных при необходимости предоставьте файлы расширенных сеансов событий для оценки специализированных или динамических SQL-запросов или любых инструкций DML, инициированных с помощью уровня данных приложения. {0}", + "sql.migration.database.assessment.xevents.description": "Для выбранных баз данных при необходимости предоставьте файлы расширенных сеансов событий для оценки специализированных или динамических SQL-запросов или любых инструкций DML, инициированных с помощью уровня данных приложения.", "sql.migration.full.backup.files": "Файлы полной резервной копии", "sql.migration.sku.azureConfiguration.gen5": "5-е поколение", "sql.migration.sku.azureConfiguration.generalPurpose": "Общее назначение", + "sql.migration.target.provisioning.generate.template": "Генерировать шаблон", "sql.migration.status.generatingscript": "Создается скрипт", "sql.migration.status.generatingcompleted": "Создание скрипта завершено", "sql.migration.sku.get.recommendation": "Получить рекомендацию Azure", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "Я подтверждаю отсутствие дополнительных резервных копий журналов и хочу завершить прямую миграцию.", "sql.migration.tde.wizard.optionadsconfirm": "Я даю согласие на использование моих учетных данных для доступа к сертификатам.", "sql.migration.tde.wizard.optionmanual": "Мои сертификаты и закрытые ключи уже перенесены в целевой объект.", + "sql.ir.local.ir.definition": "Я хочу настроить локальную среду выполнения интеграции на другом компьютере с Windows, который не является моим локальным компьютером.", "sql.migration.sku.io.memory.requirement": "Требование задержки ввода-вывода", + "sql.ir.ip.address": "IP-адрес", + "sql.ir.config.type": "Тип конфигурации IR", + "sql.ir.ir.version": "Версия IR", "sql.migration.empty.table.subtext": "Если ожидались результаты, проверьте подключение к экземпляру SQL Server.", "sql.migration.wizard.cancel.reason.others.input.box.note": "Если вы выбрали других пользователей, напишите краткую заметку.", "sql.migration.impact": "Воздействие", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "Импорт оценки в Azure SQL", "sql.migration.sku.import.performance.data": "Импорт данных производительности", "sql.migration.sku.import.performance.data.dialog.description": "Импортируйте этот файл данных из существующей папки, если вы уже собрали его с помощью Помощника по миграции данных.", + "sql.ir.important": "Важно", "sql.migration.database.migration.migration.mode.tool.tip": "В Azure Database Migration Service вы можете перенести базы данных в автономном режиме или при их подключении к сети. При автономной миграции время простоя приложения начинается при запуске миграции. Чтобы ограничить время простоя временем, необходимым для перехода в новую среду после миграции, используйте миграцию по сети.", "sql.migration.tde.validation.requirements.message": "Чтобы миграция сертификата была успешной, необходимо выполнить все требования, указанные ниже.\r\n\r\nНажмите \"Запустить проверку\", чтобы проверить выполнение требований.", "sql.migration.copy.status.inprogress": "Выполняется", @@ -484,6 +506,8 @@ "sql.login.migration.type": "Тип учетных данных", "sql.migration.sku.logs.iops.requirement": "Требуемое количество операций ввода-вывода в секунду для журналов", "sql.migration.field.label.mi.restore.state": "Состояние восстановления управляемого экземпляра", + "sql.ir.manual.ir.collapsed": "Конфигурация IR вручную свернута", + "sql.ir.manual.ir.expanded": "Конфигурация IR вручную развернута", "sql.migration.map.target.heading": "Сопоставление выбранных баз данных-источников с целевыми базами данных для миграции", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "Серия Premium, оптимизированная для операций в памяти", "sql.migration.sku.memory.requirement": "Требования к памяти", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "Новая миграция", "sql.migration.newSupportRequest": "Новый запрос на поддержку", "sql.migration.saved.assessment.next": "Далее", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "Следующее поколение общего назначения", "sql.migration.no": "Нет", "sql.migration.no.sqldatabaseserver.found": "Серверы баз данных SQL Azure не найдены.", "sql.migration.no.sqldatabase.found": "Базы данных SQL Azure не найдены.", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "Не найдены проблемы миграции в SQL Server на виртуальной машине Azure.", "sql.migration.no.location.found": "Расположения не найдены.", "sql.migration.no.managedInstance.found": "Управляемые экземпляры не найдены.", + "sql.ir.no.node.found": "Узел не найден", "sql.migration.no.pending.backups": "Ожидающие резервные копии отсутствуют. Нажмите кнопку Обновить, чтобы проверить текущее состояние.", "sql.migration.cancel.feedback.no.reason.selected": "Причина не выбрана", "sql.migration.wizard.sku.error.noRecommendation": "Нет доступных рекомендаций", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "Подписки не найдены.", "sql.migration.select.target.label": "Цель не выбрана. Выберите целевой объект, чтобы просмотреть сводку оценки.", "sql.migration.no.virtualMachine.found": "Виртуальные машины не найдены", + "sql.ir.node.name": "Имя узла", "sql.migration.restore.status.none": "Нет", "sql.migration.restore.backupset.status.none": "Нет", "sql.migration.parallel.copy.type.none": "Нет", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "Не готово", "sql.migration.restore.status.not.started": "Не запущено", "sql.login.migration.steps.not.started": "Не запущено", + "sql.ir.recommended.link": "Примечание. См. рекомендации для локальной среды выполнения интеграции", "sql.migration.backup.file.number.of.stripes": "Число полос", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "ОК", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "Собранные объекты", "sql.migration.offline": "Вне сети", "sql.migration.database.migration.mode.offline.label": "Автономная миграция", + "sql.ir.powershellscript.definition": "После выполнения в PowerShell уникальный сценарий, показанный ниже, загрузит и установит локальную среду выполнения интеграции и зарегистрирует ее в Azure Database Migration Service. На целевом компьютере необходимо установить PowerShell.", "sql.migration.online": "В Интернете", "sql.migration.database.migration.mode.online.label": "Миграция по сети", "sql.migration.open": "Открыть", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "Прежде чем продолжить, выберите расположение файлов резервной копии базы данных.", "sql.migration.cancel.feedback.reason.container.description": "Укажите причину отмены миграции. Это поможет нам улучшить взаимодействие.", "sql.migration.port.label": "Порт", + "sql.ir.powershell.script.saved": "Сценарий PowerShell сохранен", + "sql.ir.ps.script.collapsed": "Сценарий PowerShell свернут", + "sql.ir.ps.script.expanded": "Сценарий PowerShell развернут", "sql.migration.status.prefetchobjects": "Упреждающая выборка объектов", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "SSD (цен. категория \"Премиум\")", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "SSD (цен. категория \"Премиум\") версии 2", "sql.migration.sku.azureConfiguration.premiumSeries": "Серия Premium", "sql.migration.copy.status.preparingforcopy": "Подготовка", + "sql.ir.powershell.prereq": "Необходимое условие: требуется PowerShell с правами администратора на выполнение. ", "sql.login.migration.status.page.previous.button.title": "Назад (отключено)", "sql.migration.tde.migrate.results.heading.previous": "Предыдущие результаты миграции сертификатов:", "sql.migration.provide.unique.containers": "Укажите уникальный контейнер для каждой целевой базы данных. Затронутые базы данных: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "Не удалось обновить список учетных данных из целевого объекта", "sql.login.migration.refresh.login.data.successful": "Список учетных данных обновлен. Найдены исходные учетные данные: {0}, найдены целевые учетные данные: {1}", "sql.migration.resourceGroups": "Группа ресурсов", + "sql.migration.storage.account.resource.group.label": "Группа ресурсов", "sql.migration.rg.created": "Создана группа ресурсов", "sql.migration.services.resource.group": "Группа ресурсов для Azure Database Migration Service.", "sql.migration.dms.resource_group": "Группа ресурсов для целевого Azure SQL. Будут показаны только группы ресурсов, содержащие службу.", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "Файлы журналов SQL", "sql.migration.sql.assessment.notebook.title": "Оценка миграции SQL", "sql.migration.sku.sql.temp": "SQL tempdb", + "sql.migration.target.provisioning.save": "Сохранить", + "sql.migration.target.provisioning.title": "Сохранить шаблон", "sql.migration.save.close": "Сохранить и закрыть", "sql.migration.save.assessment.report": "Сохранить отчет об оценке", "sql.migration.save.recommendation.report": "Сохранить отчет о рекомендациях", + "sql.ir.save.script": "Сохранить сценарий", + "sql.migration.target.upload.to.azure": "Сохранить в контейнере BLOB-объектов Azure", "sql.migration.saved.assessment.result": "Сохраненный сеанс", "sql.migration.sku.parameters.scale.factor": "Коэффициент масштаба", "sql.migration.schema.data": "Схема и данные", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "Поиск резервных копий", "sql.migration.wizard.troubleshooting": "Дополнительные действия по устранению неполадок см. по ссылке: https://aka.ms/dms-migrations-troubleshooting.", "sql.migration.select": "Выбрать", + "sql.migration.select.storage.account.title": "Выберите учетную запись хранения Azure", "sql.migration.select.service.title": "Выбрать службу миграции баз данных", "sql.migration.select.service.prompt": "Выберите службу Database Migration Service", "sql.migration.select.service.select.a.service": "Выберите службу Database Migration Service", "sql.migration.invalid.migration.service.offline.error": "Выберите службу Database Migration Service, подключенную к какому-либо узлу.", "sql.migration.status.select.service.MESSAGE": "Выберите службу Database Migration Service для отслеживания миграций.", + "sql.migration.select.storage.select.a.storage.account": "Выбрать учетную запись хранения", "sql.migration.blob.container.select": "Сначала выберите значение контейнера больших двоичных объектов.", "sql.migration.sku.import.performance.data.dialog.open.folder": "Выберите папку", "sql.migration.sku.import.performance.data.dialog.helper.message": "Выберите папку на локальном диске", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "Остановить проверку", "sql.migration.sku.azureRecommendation.stop.popup": "Остановка сбора данных о производительности…", "sql.migration.sku.targetStorageConfiguration.storage": "Хранилище", - "sql.migration.storage.account": "Учетная запись хранения", + "sql.migration.select.storage.account.label": "Учетная запись хранения", + "sql.migration.storage.account.details.label": "Учетная запись хранения", "sql.migration.network.share.azure.header": "Сведения об учетной записи хранения", "sql.migration.subscription": "Подписка", "sql.migration.blob.storage.subscription.label": "Подписка", "sql.migration.dms.subscription": "Имя подписки для Azure Database Migration Service", "sql.migration.services.subscription": "Имя подписки для Azure Database Migration Service.", "sql.migration.sku.subscription": "Имя подписки для целевого объекта Azure SQL", + "sql.migration.storage.account.subscription": "Имя подписки для учетной записи хранения", "sql.migration.state.succeeded": "Выполнено", "sql.migration.tde.validation.status.succeeded": "Успешно", "sql.migration.copy.status.succeeded": "Успешно", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "Тип объекта", "sql.migration.username.label": "Имя целевого пользователя", "sql.migration.target.version": "Целевая версия", + "sql.migration.target.provisioning.save.template.success": "Шаблон сохранен", + "sql.migration.target.provisioning.upload.template.success": "Шаблон успешно отправлен", "sql.migration.test.connection": "Проверить подключение", "sql.migration.dashboard.help.description.migrateUsingADS": "Расширение миграции Azure SQL для Azure Data Studio предоставляет возможности для оценки, получения правильных рекомендаций Azure и миграции баз данных SQL Server в Azure.", "sql.migration.sqldb.not.ready": "Сервер базы данных SQL \"{0}\" недоступен для миграции, поскольку сейчас он находится в состоянии \"{1}\". Чтобы продолжить, выберите доступный сервер базы данных SQL.", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "Выполняется отправка файлов журнала", "sql.migration.sqldb.column.usedparallelcopies": "Использованные параллельные копии", "sql.migration.path.user.account": "Учетная запись пользователя", + "sql.migration.network.share.user.account.label": "Учетная запись пользователя", "sql.migration.username": "Имя пользователя", + "sql.migration.database.assessment.qds.label": "Использование хранилища данных запросов (этот параметр доступен для Microsoft SQL Server 2016 и более поздних версий)", + "sql.migration.database.assessment.xevents.label": "Использование расширенного сеанса событий", "sql.migration.starting.login": "Выполняется проверка и миграция учетных данных", "sql.login.migration.establish.user.mappings": "Проверка и миграция учетных данных завершена.\r\n\r\nУстановка сопоставлений пользователей.", "sql.migration.starting.login.failed": "Сбой проверки и миграции учетных данных", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "Были выполнены следующие шаги:", "sql.login.migration.wizard.target.data.migration.warning": "Рекомендуется перенести базы данных в целевой объект Azure SQL перед началом миграции имен для входа, чтобы избежать сбоев. Однако этот процесс миграции можно запускать в любое время, если цель — обновить сопоставление пользователей для недавно перенесенных баз данных.\r\n\r\n Если имена источника и базы данных не совпадают, некоторые разрешения могут быть применены неправильно.", "sql.migration.blob.storage.folder.info": "При отправке резервных копий баз данных в контейнер BLOB-объектов убедитесь, что файлы резервных копий из разных баз данных хранятся в отдельных папках. Поддерживается только корень контейнера и папок глубиной не более одного уровня.", + "sql.ir.local.ir.setup.note": "При нажатии кнопки \"Выполнить сценарий\" расположенный ниже сценарий PowerShell автоматически скачает программное обеспечение локальной среды выполнения интеграции, а также установит и зарегистрирует его в Azure Database Migration Service. Чтобы проверить состояние подключения IR, вернитесь на предыдущий экран и обновите страницу. ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "Где вы хотите сохранить собранные данные?", "sql.migration.network.share.windows.user.label": "Учетная запись пользователя Windows с доступом на чтение сетевой папки", "sql.migration.network.share.windows.user.info": "Учетная запись пользователя Windows с доступом на чтение сетевой папки.", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Имя ресурса Azure Database Migration Service", "sql.migration.sku.resource": "Имя целевого ресурса Azure SQL", "sql.migration.sku.resource.port": "Номер вашего целевого ресурса порта Azure SQL: 0–65535", + "sql.migration.storage.account.blob.container": "Имя контейнера BLOB-объектов", + "sql.migration.storage.account": "Имя учетной записи хранения", "sql.migration.pre.req.4": "Сведения о расположении резервной копии базы данных: сетевой общей папке или контейнере Хранилища BLOB-объектов Azure (не требуется для целевых Баз данных SQL Azure).", "sql.migration.wizard.sku.assessment.error.detail": "[Нет результатов оценки для проверки готовности к миграции базы данных. При установке этого флажка вы подтверждаете, что хотите продолжить миграцию базы данных в требуемый Azure SQL целевой объект.]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-zh-hans/CHANGELOG.md b/i18n/ads-language-pack-zh-hans/CHANGELOG.md index 0154b7f3874f..2fc03943e826 100644 --- a/i18n/ads-language-pack-zh-hans/CHANGELOG.md +++ b/i18n/ads-language-pack-zh-hans/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-zh-hans" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-zh-hans/package.json b/i18n/ads-language-pack-zh-hans/package.json index 2044efd42d6d..0af21876d342 100644 --- a/i18n/ads-language-pack-zh-hans/package.json +++ b/i18n/ads-language-pack-zh-hans/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-zh-hans", "displayName": "Chinese (Simplified) (简体中文) Language Pack for Azure Data Studio", "description": "Language pack extension for Chinese (Simplified)", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.mssql.i18n.json index 90fb8f21d9fc..bdd3df8e405e 100644 --- a/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "文件组", "objectManagement.databaseProperties.filegrowthLimitError": "文件增长不能大于文件的最大文件大小", "objectManagement.databaseProperties.filesText": "文件", - "objectManagement.optionsSectionHeader": "文件", + "objectManagement.filesSectionHeader": "文件", "objectManagement.databaseProperties.filestreamFilesText": "文件流文件", "objectManagement.filterSectionTitle": "筛选器", "objectManagement.findText": "查找", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "操作模式(实际)", "objectManagement.databaseProperties.requestedOperationModeText": "操作模式(要求)", "objectManagement.optimizeAdHocWorkloadsLabel": "优化临时工作负载", + "objectManagement.optionsSectionHeader": "选项", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "原始文件名", "objectManagement.overwriteExistingBackups": "覆盖所有现有备份集", "objectManagement.backupOverwriteMedia": "覆盖媒体", diff --git a/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.notebook.i18n.json index 95f08280240f..971a95b56793 100644 --- a/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "浏览", - "configurePython.installationType": "安装类型", - "configurePython.newInstall": "新 Python 安装", "configurePythyon.noVersionsFound": "找不到支持的 Python 版本。", "configurePython.descriptionWithoutKernel": "笔记本内核要求配置 Python 运行时并安装依赖项。", - "configurePython.locationTextBoxText": "Python 安装位置", - "configurePython.pythonConfigured": "Python 运行时已配置!", + "configurePython.locationTextBoxText": "Python 位置", "configurePython.selectFileLabel": "选择", "configurePython.descriptionWithKernel": "\"{0}\" 内核要求配置 Python 运行时并安装依赖项。", - "configurePython.existingInstall": "使用现有 Python 安装", + "configurePythyon.existingInstance": "{0} (当前 Python 实例)", "configurePythyon.customPathLabel": "{0} (自定义)", - "configurePythyon.defaultPathLabel": "{0} (默认)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "需要笔记本路径" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "将关闭活动 Python 笔记本会话以进行更新。是否要立即继续?", "msgWaitingForInstall": "另一个 Python 安装正在进行中。请等待它完成。", - "msgPythonRunningError": "在 Python 运行时无法覆盖现有 Python 安装。请关闭所有活动笔记本，再继续操作。", - "dontAskAgain": "不再询问", - "msgDownloadPython": "正在将平台 {0} 的本地 python 下载到 {1}", - "msgPythonDownloadPending": "正在下载 python 包", "msgGetPythonUserDirFailed": "获取 Python 用户路径时遇到错误: {0}", "msgPackageRetrievalFailed": "尝试检索已安装的包列表时遇到错误: {0}", - "msgPythonDirectoryError": "创建 python 安装目录时出错", - "msgPythonDownloadError": "下载 python 安装程序时出错", - "msgPythonUnpackError": "解压 Python 捆绑包时出错", "msgTaskName": "正在安装笔记本依赖项", "msgDependenciesInstallationFailed": "安装笔记本依赖项失败，错误: {0}", "msgInstallPkgStart": "正在安装笔记本依赖项；有关详细信息，请参阅“任务”视图", - "no": "否", "msgInstallPkgFinish": "笔记本依赖项安装完毕", - "msgInstallPkgProgress": "正在安装笔记本依赖项", - "msgPythonDownloadComplete": "Python 下载完毕", - "msgPythonVersionUpdatePrompt": "Python {0} 现已在 Azure Data Studio 中提供。当前 Python 版本 (3.6.6) 将于 2021 年 12 月不再受支持。是否要立即更新到 Python {0}?", - "msgPythonVersionUpdateWarning": "将安装 Python {0} ，并将替换 Python 3.6.6。某些包可能不再与新版本兼容，或者可能需要重新安装。将创建一个笔记本来帮助你重新安装所有 pip 包。是否要立即继续更新?", - "msgPythonUnpackPending": "正在解压 python 包", - "yes": "是" + "msgInstallPkgProgress": "正在安装笔记本依赖项" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "关闭笔记本服务器失败: {0}" diff --git a/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.sql-migration.i18n.json index 9c0c0c6b618b..b205af307293 100644 --- a/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-zh-hans/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "SQL 托管实例迁移直接转换到业务关键服务层需要的时间可能远多于常规用途，因为必须为始终打开高可用性组设置三个次要副本的种子。该操作持续时间取决于数据的大小。在 90% 的情况下，设置种子的速度为 220 GB/小时或更高。", "sql.migration.dashboard.help.description.dmsGuide": "提供有关在 Azure 中迁移和现代化数据资产分步指南的迁移文章中心。", "sql.migration.resource.group.description": "资源组是保管 Azure 解决方案的相关资源的容器。", + "sql.migration.target.provisioning.template.display.limit": "单个 ARM 模板的部署限制为最多 50 个 Azure SQL 数据库。前 50 个数据库的模板如下所示。要查看所有模板，请将模板 JSON 文件保存在本地存储或 Azure Blob 存储中。", "sql.migration.pre.req.2": "在本地或 Azure 虚拟机中的 SQL Server 或云(私有、公共)中运行的任何虚拟机上的源 SQL Server 数据库。", "sql.migration.dashboard.help.description.sqldb": "将数据库从 SQL Server 实例(本地或 Azure 虚拟机中)迁移到 Azure SQL 数据库的分步教程。", "sql.migration.dashboard.help.description.mi": "以最短故障时间将数据库从 SQL Server 实例(本地或 Azure 虚拟机)迁移到 Azure SQL 托管实例的分步教程。", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "已还原的所有备份", "sql.migration.view.all": "所有数据库迁移", "sql.migration.all.fields.required": "所有字段均为必填。", + "sql.ir.version.mismatch": "所有节点都应在同一版本上进行配置", "sql.migration.all.source.tables.empty": "所有源表均为空。没有表可供选择以用于数据迁移。但是，如果它们在目标上不存在，则可用于架构迁移。", "sql.migration.unavailable.source.tables.heading": "下面的所有表均为空。没有表可供选择以用于数据迁移。但如果目标上不存在它们，则可以使用架构迁移。", "sql.migration.missing.tables.heading": "目标上缺少以下所有表。若要迁移这些表中的数据，请选择上面的迁移架构选项。", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "是否确实要取消此迁移?", "sql.delete.migration.confirmation": "确定要删除此迁移吗?", "sql.migration.migration.list.ascending.label": "升序", - "sql.migration.database.assessment.xevents.title": "评估扩展事件会话", + "sql.migration.database.assessment.xevents.title": "评估临时或动态 SQL", "sql.migration.assessed.dbs.label": "评估的数据库: {0}", "sql.migration.assessment.findings.label": "评估结果", "sql.migration.assessment.in.progress": "正在进行评估", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Azure 数据库迁移服务", "sql.migration.service.ready": "Azure 数据库迁移服务 \"{0}\" 连接到在节点上运行的自承载集成运行时 - {1}\r\n\r\n为了提高性能和高可用性，你可以注册其他节点。", "sql.migration.service.ready.below": "Azure 数据库迁移服务“{0}”连接到在节点上运行的自承载集成运行时 - {1}\r\n\r\n为了提高性能和高可用性，你可以注册其他节点。请参阅下面的注册说明。", + "sql.migration.service.ready.without.nodes": "Azure 数据库迁移服务“{0}”已连接到在以下节点上运行的自承载集成运行时", "sql.migration.service.header": "Azure 数据库迁移服务“{0}”详细信息:", "sql.migration.service.not.ready": "未注册 Azure 数据库迁移服务。Azure 数据库迁移服务“{0}”需要向任意节点上的自承载集成运行时进行注册。", "sql.migration.service.not.ready.below": "未注册 Azure 数据库迁移服务。Azure 数据库迁移服务“{0}”需要向任意节点上的自承载集成运行时进行注册。\r\n\r\n请参阅下面的注册说明。", + "sql.migration.ir.container.description": "Azure 数据库迁移服务利用 Azure 数据工厂的自承载集成运行时将备份从本地网络文件共享上传到 Azure。根据上一页上的选择，需要设置自承载集成运行时。", "sql.migration.service.container.container.description1": "Azure 数据库迁移服务利用 Azure 数据工厂的自承载集成运行时处理源和目标之间的连接，并将备份从本地网络文件共享上传到 Azure (适用时)。", "sql.migration.services.name": "Azure 数据库迁移服务名称。", "sql.migration.ir.page.description": "Azure 数据库迁移服务(DMS)协调数据库迁移活动并跟踪其进度。如果之前已经创建，则可以选择现有数据库迁移服务，或在下面创建一个新的服务。", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "Azure 数据库迁移服务的 Azure 区域。将仅显示包含服务的区域。", "sql.migration.services.location": "适用于 Azure 数据库迁移服务的 Azure 区域。此区域应与目标 Azure SQL 相同。", "sql.migration.sku.location": "Azure SQL 目标的 Azure 区域。将仅显示包含符合迁移条件的目标的区域。", + "sql.migration.storage.account.location": "存储帐户的 Azure 区域。将仅显示包含存储帐户的区域。", "sql.migration.summary.azure.storage": "Azure 存储", "sql.migration.validate.ir.validation.result.label.storage": "Azure 存储连接", "sql.migration.summary.azure.storage.subscription": "Azure 存储订阅", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "备份大小(MB)", "sql.migration.backup.start.time": "备份开始时间", "sql.migration.wizard.sku.all": "根据评估结果，你的联机状态下的所有 {0} 个数据库都可以迁移到 Azure SQL。", + "sql.migration.target.provisioning.description": "下面是建议的目标 SKU 的 ARM 脚本。可以将脚本另存为模板。", "sql.migration.sku.targetStorageConfiguration.info": "下面是满足存储性能需求所需的目标存储配置。", "sql.migration.blob.container.title": "Blob 容器", "sql.migration.blob.container.label": "Blob 容器资源组", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "单击以查看错误详细信息", "sql.migration.service.details.button.label": "关闭", "sql.migration.close": "关闭", + "sql.migration.target.provisioning.close": "关闭", "sql.migration.sku.azureRecommendation.collectData.method": "立即收集性能数据", "sql.login.migration.collecting.target.logins.failed": "收集目标登录失败，错误代码为 {0}", "sql.migration.status.collectioncompleted": "收集已完成", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "在不还原所有备份的情况下完成直接转换可能导致数据丢失。", "sql.migration.restore.status.completing.migration": "正在完成迁移", "sql.migration.save.close.popup": "已保存配置。性能数据收集将保持在后台运行。你可以在需要时停止收集。", + "sql.migration.configure.ir": "配置集成运行时", + "sql.ir.configure.manually": "手动配置 ", + "sql.ir.configure.powershellscript": "使用 PowerShell 脚本进行配置 ", "sql.migration.connection.label": "连接", "sql.migration.community.support.description": "与 Microsoft Community 联系", "sql.migration.wizard.target.connection.error": "连接错误: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "说明", "sql.migration.details.title": "详细信息", "sql.migration.details.copied": "已复制详细信息", + "sql.migration.validate.ir.error.message": "必须提供 {0} 详细信息，但缺少此信息。", "sql.migration.field.label.deteected.files": "检测到的文件", "sql.migration.dashboard.description": "确定 SQL Server 实例的迁移准备情况，确定建议的 Azure SQL 目标，并完成 SQL Server 实例向 Azure SQL 托管实例、Azure 虚拟机上的 SQL Server 或 Azure SQL 数据库的迁移。", "sql.migration.restore.backuptype.differentialdatabase": "差异数据库", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "输入用于连接到 SQL Server 实例 {0} 的 Windows 身份验证凭据。这些凭据将用于连接到 SQL Server 实例并标识有效的备份文件。", "sql.migration.source.details.windowAuth.db": "输入用于连接到 SQL Server 实例 {0} 的 Windows 身份验证凭据。这些凭据将用于从自承载集成运行时连接到 SQL Server 实例。", "sql.migration.enter.your.sql.cred": "输入源 SQL Server 实例的凭据。将数据库迁移到 Azure SQL 时将使用这些凭据。", + "sql.migration.select.storage.account.heading": "输入下面的详细信息以选择 Azure 存储帐户并将脚本另存为模板", "sql.migration.services.container.description": "在下面输入信息以添加新的 Azure 数据库迁移服务。", "sql.migration.services.container.description.network": "输入下面的信息以添加新 Azure 数据库迁移服务。若要注册自承载集成运行时，请在上一页上选择“我的数据库备份位于网络共享上”。", "sql.migration.sku.parameters.text": "输入以下信息以编辑建议参数。", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "错误: Azure SQL 托管实例支持每个实例的最大 {0} 用户数据库数。选择 {0} 或减少数据库数量以继续。", "sql.login.migration.migrate.server.roles.and.set.permissions": "建立用户映射已完成。\r\n\r\n当前正在迁移服务器角色、建立服务器映射和设置权限。这需要一些时间。", "sql.login.migration.establish.user.mappings.failed": "建立用户映射失败", + "sql.ir.powershellscript": "执行脚本 ", + "sql.ir.executing.powershellscript": "已开始执行并监视打开的 PowerShell 窗口。 ", "sql.migration.support.resources.description": "浏览文档", "sql.migration.tde.wizard.optionads": "将我的证书和私钥导出到目标。", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "将 {0} 个登录迁移到 {1} \"{2}\" 失败", "sql.migration.notebook.open.error": "未能打开迁移笔记本。", "sql.migration.dms.provision.failed": "未能预配数据库迁移服务。请等待几分钟，然后重试。", + "sql.migration.target.provisioning.save.template.fail": "未能保存 ARM 模板", + "sql.migration.target.provisioning.upload.template.fail": "未能上传 ARM 模板", "sql.migration.tab.button.feedback.description": "反馈", "sql.migration.tab.button.feedback.label": "反馈", "sql.migration.feedback.issue.title": "有关迁移体验的反馈", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "按照下面的说明安装自承载集成运行时。", "sql.migration.database.table.selection.description": "对于下面的每个数据库，单击“编辑”以选择要从源迁移到目标的表。然后，在单击“下一步”之前，单击“运行验证”来验证提供的配置。", "sql.migration.sql.vm.page.blob.info": "对于运行 SQL Server 2014 或更低版本的目标服务器，必须将数据库备份存储在 Azure 存储 Blob 容器中，而不是使用网络共享选项上传它们。此外，必须将备份文件存储为页 Blob，因为运行 SQL Server 2016 或更高版本的目标仅支持块 blob。要了解详细信息，请访问: {0}", - "sql.migration.database.assessment.xevents.description": "对于所选数据库，可以选择提供扩展事件会话文件以评估临时或动态 SQL 查询或通过应用程序数据层启动的任何 DML 语句。{0}", + "sql.migration.database.assessment.xevents.description": "对于所选数据库，可选择提供扩展事件会话文件以评估临时或动态 SQL 查询或通过应用程序数据层启动的任何 DML 语句。", "sql.migration.full.backup.files": "一个或多个完整备份文件", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "常规用途", + "sql.migration.target.provisioning.generate.template": "生成模板", "sql.migration.status.generatingscript": "正在生成脚本", "sql.migration.status.generatingcompleted": "脚本生成已完成", "sql.migration.sku.get.recommendation": "获取 Azure 建议", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "我确认没有要提供的其他日志备份，并且希望完成直接转换。", "sql.migration.tde.wizard.optionadsconfirm": "我同意使用我的凭据访问证书。", "sql.migration.tde.wizard.optionmanual": "我已将证书和私钥迁移到目标。", + "sql.ir.local.ir.definition": "我想在另一台 Windows 计算机上设置自承载集成运行时，该计算机不是我的本地计算机。", "sql.migration.sku.io.memory.requirement": "IO 延迟要求", + "sql.ir.ip.address": "IP 地址", + "sql.ir.config.type": "IR 配置类型", + "sql.ir.ir.version": "IR 版本", "sql.migration.empty.table.subtext": "如果结果在预期内，请验证与 SQL Server 实例的连接。", "sql.migration.wizard.cancel.reason.others.input.box.note": "如果选择了“其他”，请撰写简短备注。", "sql.migration.impact": "影响", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "将评估导入到 Azure SQL", "sql.migration.sku.import.performance.data": "导入性能数据", "sql.migration.sku.import.performance.data.dialog.description": "如果已使用“数据迁移助手”收集此数据文件，请从现有文件夹导入此数据文件。", + "sql.ir.important": "重要说明", "sql.migration.database.migration.migration.mode.tool.tip": "在 Azure 数据库迁移服务中，可以在脱机或联机时迁移数据库。脱机迁移期间，应用程序停机时间在迁移开始时开始。如果要在迁移后将故障时间限制为要直接转换到新环境的时间，请使用联机迁移。", "sql.migration.tde.validation.requirements.message": "为了使证书迁移成功，必须满足下面列出的所有要求。\r\n\r\n单击“运行验证”以检查是否满足要求。", "sql.migration.copy.status.inprogress": "进行中", @@ -484,6 +506,8 @@ "sql.login.migration.type": "登录类型", "sql.migration.sku.logs.iops.requirement": "日志 IOPS 要求", "sql.migration.field.label.mi.restore.state": "托管实例还原状态", + "sql.ir.manual.ir.collapsed": "手动 IR 配置已折叠", + "sql.ir.manual.ir.expanded": "手动 IR 配置已展开", "sql.migration.map.target.heading": "将所选源数据库映射到目标数据库以进行迁移", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "内存优化高级系列", "sql.migration.sku.memory.requirement": "内存要求", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "新建迁移", "sql.migration.newSupportRequest": "新建支持请求", "sql.migration.saved.assessment.next": "下一步", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "下一代常规用途", "sql.migration.no": "否", "sql.migration.no.sqldatabaseserver.found": "找不到 Azure SQL 数据库服务器。", "sql.migration.no.sqldatabase.found": "找不到 Azure SQL 数据库。", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "在 Azure 虚拟机上未发现迁移到 SQL Server 的问题。", "sql.migration.no.location.found": "找不到位置。", "sql.migration.no.managedInstance.found": "找不到托管实例。", + "sql.ir.no.node.found": "未找到节点", "sql.migration.no.pending.backups": "没有挂起的备份。请单击“刷新”以检查当前状态。", "sql.migration.cancel.feedback.no.reason.selected": "未选择原因", "sql.migration.wizard.sku.error.noRecommendation": "无可用建议", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "找不到订阅。", "sql.migration.select.target.label": "未选择目标。选择目标以查看评估摘要。", "sql.migration.no.virtualMachine.found": "找不到任何虚拟机。", + "sql.ir.node.name": "节点名称", "sql.migration.restore.status.none": "无", "sql.migration.restore.backupset.status.none": "无", "sql.migration.parallel.copy.type.none": "无", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "未就绪", "sql.migration.restore.status.not.started": "未启动", "sql.login.migration.steps.not.started": "未启动", + "sql.ir.recommended.link": "注意: 请参阅自承载 IR 建议", "sql.migration.backup.file.number.of.stripes": "条带数", "sql.migration.offline.caps": "脱机", "sql.migration.ok": "确定", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "对象已收集", "sql.migration.offline": "脱机", "sql.migration.database.migration.mode.offline.label": "脱机迁移", + "sql.ir.powershellscript.definition": "在 PowerShell 中执行后，下面显示的唯一脚本将下载并安装自承载集成运行时，并向 Azure 数据库迁移服务注册它。需要在目标计算机上安装 PowerShell。", "sql.migration.online": "联机", "sql.migration.database.migration.mode.online.label": "联机迁移", "sql.migration.open": "打开", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "请先选择数据库备份文件的位置，然后再继续。", "sql.migration.cancel.feedback.reason.container.description": "请花点时间告诉我们取消迁移的原因。这将有助于我们改进体验。", "sql.migration.port.label": "端口", + "sql.ir.powershell.script.saved": "PowerShell 脚本已保存", + "sql.ir.ps.script.collapsed": "PowerShell 脚本已折叠", + "sql.ir.ps.script.expanded": "PowerShell 脚本已展开", "sql.migration.status.prefetchobjects": "预提取对象", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "高级 SSD", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "高级 SSD v2", "sql.migration.sku.azureConfiguration.premiumSeries": "高级系列", "sql.migration.copy.status.preparingforcopy": "正在准备", + "sql.ir.powershell.prereq": "先决条件: 需要 PowerShell 具有以管理员身份执行的权限。 ", "sql.login.migration.status.page.previous.button.title": "上一个(已禁用)", "sql.migration.tde.migrate.results.heading.previous": "以前的证书迁移结果:", "sql.migration.provide.unique.containers": "为每个目标数据库提供唯一的容器。受影响的数据库有: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "从目标刷新登录列表失败", "sql.login.migration.refresh.login.data.successful": "已成功刷新登录列表。找到的源登录 {0}，找到的目标登录 {1}", "sql.migration.resourceGroups": "资源组", + "sql.migration.storage.account.resource.group.label": "资源组", "sql.migration.rg.created": "已创建资源组", "sql.migration.services.resource.group": "Azure 数据库迁移服务的资源组。", "sql.migration.dms.resource_group": "Azure SQL 目标的资源组。将仅显示包含服务的资源组。", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "SQL 日志文件", "sql.migration.sql.assessment.notebook.title": "SQL 迁移评估", "sql.migration.sku.sql.temp": "SQL tempdb", + "sql.migration.target.provisioning.save": "保存", + "sql.migration.target.provisioning.title": "保存模板", "sql.migration.save.close": "保存并关闭", "sql.migration.save.assessment.report": "保存评估报告", "sql.migration.save.recommendation.report": "保存建议报告", + "sql.ir.save.script": "保存脚本", + "sql.migration.target.upload.to.azure": "保存到 Azure Blob 容器", "sql.migration.saved.assessment.result": "已保存的会话", "sql.migration.sku.parameters.scale.factor": "比例因子", "sql.migration.schema.data": "架构和数据", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "正在搜索备份", "sql.migration.wizard.troubleshooting": "有关更多故障排除步骤，请参阅链接: https://aka.ms/dms-migrations-troubleshooting。", "sql.migration.select": "选择", + "sql.migration.select.storage.account.title": "选择 Azure 存储帐户", "sql.migration.select.service.title": "选择数据库迁移服务", "sql.migration.select.service.prompt": "选择一项数据库迁移服务", "sql.migration.select.service.select.a.service": "选择一项数据库迁移服务", "sql.migration.invalid.migration.service.offline.error": "选择连接到节点的数据库迁移服务。", "sql.migration.status.select.service.MESSAGE": "选择一项数据库迁移服务来监视迁移。", + "sql.migration.select.storage.select.a.storage.account": "选择存储帐户", "sql.migration.blob.container.select": "首先选择一个 Blob 容器值。", "sql.migration.sku.import.performance.data.dialog.open.folder": "选择一个文件夹", "sql.migration.sku.import.performance.data.dialog.helper.message": "选择本地驱动器上的文件夹", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "停止验证", "sql.migration.sku.azureRecommendation.stop.popup": "正在停止性能数据收集...", "sql.migration.sku.targetStorageConfiguration.storage": "存储", - "sql.migration.storage.account": "存储帐户", + "sql.migration.select.storage.account.label": "存储帐户", + "sql.migration.storage.account.details.label": "存储帐户", "sql.migration.network.share.azure.header": "存储帐户详细信息", "sql.migration.subscription": "订阅", "sql.migration.blob.storage.subscription.label": "订阅", "sql.migration.dms.subscription": "Azure 数据库迁移服务的订阅名称", "sql.migration.services.subscription": "Azure 数据库迁移服务的订阅名称。", "sql.migration.sku.subscription": "Azure SQL 目标的订阅名称", + "sql.migration.storage.account.subscription": "存储帐户的订阅名称", "sql.migration.state.succeeded": "成功", "sql.migration.tde.validation.status.succeeded": "成功", "sql.migration.copy.status.succeeded": "成功", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "目标类型", "sql.migration.username.label": "目标用户名", "sql.migration.target.version": "目标版本", + "sql.migration.target.provisioning.save.template.success": "已成功保存模板", + "sql.migration.target.provisioning.upload.template.success": "已成功上传模板", "sql.migration.test.connection": "测试连接", "sql.migration.dashboard.help.description.migrateUsingADS": "Azure Data Studio 的 Azure SQL 迁移扩展提供评估、获取适当大小的 Azure 建议以及将 SQL Server 数据库迁移到 Azure 的功能。", "sql.migration.sqldb.not.ready": "SQL 数据库服务器“{0}”不可用于迁移，因为它当前处于“{1}”状态。如果要继续，请选择可用的 SQL 数据库服务器。", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "上传日志备份", "sql.migration.sqldb.column.usedparallelcopies": "已用并行副本", "sql.migration.path.user.account": "用户帐户", + "sql.migration.network.share.user.account.label": "用户帐户", "sql.migration.username": "用户名", + "sql.migration.database.assessment.qds.label": "使用查询数据存储(此选项适用于 Microsoft SQL Server 2016 及更高版本)", + "sql.migration.database.assessment.xevents.label": "使用扩展事件会话", "sql.migration.starting.login": "正在验证和迁移登录", "sql.login.migration.establish.user.mappings": "已完成验证和迁移登录。\r\n\r\n正在建立用户映射。", "sql.migration.starting.login.failed": "验证和迁移登录失败", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "我们运行了以下步骤:", "sql.login.migration.wizard.target.data.migration.warning": "建议在开始登录迁移之前，先将数据库迁移到 Azure SQL 目标，以避免过程中出现故障。但是，如果目标是更新最近迁移的数据库的用户映射，你可以根据需要随时运行此迁移过程。\r\n\r\n如果源名称和数据库名称不同，则某些权限可能无法正确应用。", "sql.migration.blob.storage.folder.info": "将数据库备份上传到 blob 容器时，请确保不同数据库中的备份文件存储在单独的文件夹中。仅支持容器的根目录和最高级别的深层文件夹。", + "sql.ir.local.ir.setup.note": "单击“执行脚本”后，下面的 PowerShell 脚本将自动下载自承载集成运行时软件、安装并将其注册到 Azure 数据库迁移服务。若要检查 IR 的连接状态，请返回到上一个屏幕并刷新。 ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "要将收集的数据保存到何处?", "sql.migration.network.share.windows.user.label": "具有对网络共享位置读取权限的 Windows 用户账户。", "sql.migration.network.share.windows.user.info": "具有对网络共享位置读取权限的 Windows 用户账户。", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "Azure 数据库迁移服务资源名称", "sql.migration.sku.resource": "Azure SQL 目标资源名称", "sql.migration.sku.resource.port": "你的 Azure SQL 目标资源端口号: 0 - 65535", + "sql.migration.storage.account.blob.container": "Blob 容器名称", + "sql.migration.storage.account": "存储帐户名称", "sql.migration.pre.req.4": "你的数据库备份位置详细信息，可以是网络文件共享或 Azure Blob 存储容器(非 Azure SQL 数据库目标所需)。", "sql.migration.wizard.sku.assessment.error.detail": "[没有评估结果来验证数据库迁移的准备情况。选中此框即表示你确认要继续将数据库迁移到所需的 Azure SQL 目标。]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/i18n/ads-language-pack-zh-hant/CHANGELOG.md b/i18n/ads-language-pack-zh-hant/CHANGELOG.md index 5965d15bd478..0db1dc8a1461 100644 --- a/i18n/ads-language-pack-zh-hant/CHANGELOG.md +++ b/i18n/ads-language-pack-zh-hant/CHANGELOG.md @@ -2,7 +2,8 @@ All notable changes to the "ads-language-pack-zh-hant" language pack will be documented in this file. ## [Released] -* February 23, 2023 - Release for Azure Data Studio 1.48 +* May 13, 2024 - Release for Azure Data Studio 1.49 +* February 23, 2024 - Release for Azure Data Studio 1.48 * October 31, 2023 - Release for Azure Data Studio 1.47 * September 14, 2023 - Release for Azure Data Studio 1.46 * July 10, 2023 - Release for Azure Data Studio 1.45 diff --git a/i18n/ads-language-pack-zh-hant/package.json b/i18n/ads-language-pack-zh-hant/package.json index 975318188fbb..29af653eef37 100644 --- a/i18n/ads-language-pack-zh-hant/package.json +++ b/i18n/ads-language-pack-zh-hant/package.json @@ -2,7 +2,7 @@ "name": "ads-language-pack-zh-hant", "displayName": "Chinese (Traditional) Language Pack for Azure Data Studio", "description": "Language pack extension for Chinese (Traditional)", - "version": "1.48.0", + "version": "1.49.0", "publisher": "Microsoft", "repository": { "type": "git", @@ -11,7 +11,7 @@ "license": "SEE MIT License IN LICENSE.txt", "engines": { "vscode": "*", - "azdata": "^1.48.0" + "azdata": "^1.49.0" }, "icon": "languagepack.png", "categories": [ diff --git a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.cms.i18n.json b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.cms.i18n.json index 5251d89a6e73..92c5c501b3bf 100644 --- a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.cms.i18n.json +++ b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.cms.i18n.json @@ -133,7 +133,7 @@ "cms.connectionOptions.enclaveAttestationProtocol.description": "指定用來證明與有安全記憶體保護區的 Always Encrypted 一起使用的伺服器端記憶體保護區的通訊協定", "cms.connectionOptions.enclaveAttestationUrl.description": "指定用來證明與有安全記憶體保護區的 Always Encrypted 一起使用的伺服器端記憶體保護區的端點", "cms.connectionOptions.authType.description": "指定向 SQL Server 驗證的方法", - "cms.connectionOptions.encrypt.categoryValues.strict": "Strict (supported for SQL Server 2022 and Azure SQL)", + "cms.connectionOptions.encrypt.categoryValues.strict": "嚴格 (支援 SQL Server 2022 和 Azure SQL)", "cms.description": "管理 SQL Server 中央管理伺服器的支援", "cms.connectionOptions.currentLanguage.description": "SQL Server 語言記錄名稱", "cms.connectionOptions.commandTimeout.description": "終止嘗試並產生錯誤前，要等待命令執行的時間長度 (以秒為單位)", diff --git a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.mssql.i18n.json b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.mssql.i18n.json index 8b4a5040ee07..8804b7d74170 100644 --- a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.mssql.i18n.json +++ b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.mssql.i18n.json @@ -219,7 +219,7 @@ "objectManagement.filegroupsSectionHeader": "檔案群組", "objectManagement.databaseProperties.filegrowthLimitError": "Filegrowth 不能大於檔案的檔案大小上限", "objectManagement.databaseProperties.filesText": "檔案", - "objectManagement.optionsSectionHeader": "檔案", + "objectManagement.filesSectionHeader": "檔案", "objectManagement.databaseProperties.filestreamFilesText": "Filestream 檔案", "objectManagement.filterSectionTitle": "篩選", "objectManagement.findText": "尋找", @@ -309,6 +309,7 @@ "objectManagement.databaseProperties.actualOperationModeText": "作業模式 (實際)", "objectManagement.databaseProperties.requestedOperationModeText": "作業模式 (要求)", "objectManagement.optimizeAdHocWorkloadsLabel": "針對臨機工作負載進行最佳化", + "objectManagement.optionsSectionHeader": "選項", "objectManagement.restoreDatabase.restorePlan.originalFileNameText": "原始檔案名稱", "objectManagement.overwriteExistingBackups": "覆寫所有現有的備份集", "objectManagement.backupOverwriteMedia": "覆寫媒體", @@ -678,7 +679,7 @@ "mssql.connectionOptions.enclaveAttestationUrl.description": "指定用來證明與有安全記憶體保護區的 Always Encrypted 一起使用的伺服器端記憶體保護區的端點", "mssql.connectionOptions.authType.description": "指定向 SQL Server 驗證的方法", "databasesListProperties.status": "狀態", - "mssql.connectionOptions.encrypt.categoryValues.strict": "Strict (supported for SQL Server 2022 and Azure SQL)", + "mssql.connectionOptions.encrypt.categoryValues.strict": "嚴格 (支援 SQL Server 2022 和 Azure SQL)", "mssql.connectionOptions.currentLanguage.description": "SQL Server 語言記錄名稱", "mssql.executionPlan.expensiveOperationMetric": "用來在查詢執行計畫中醒目提示成本高的作業的預設計量", "mssql.connectionOptions.commandTimeout.description": "終止嘗試並產生錯誤前，要等待命令執行的時間長度 (以秒為單位)", diff --git a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.notebook.i18n.json b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.notebook.i18n.json index 280a4573703d..6343da82707f 100644 --- a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.notebook.i18n.json +++ b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.notebook.i18n.json @@ -108,17 +108,13 @@ }, "dist/dialog/configurePython/configurePathPage": { "configurePython.browseButtonText": "瀏覽", - "configurePython.installationType": "安裝類型", - "configurePython.newInstall": "新增 Python 安裝", "configurePythyon.noVersionsFound": "找不到支援的 Python 版本。", "configurePython.descriptionWithoutKernel": "Notebook 核心需要設定 Python 執行階段並安裝相依性。", - "configurePython.locationTextBoxText": "Python 安裝位置", - "configurePython.pythonConfigured": "已設定 Python 執行階段!", + "configurePython.locationTextBoxText": "Python 位置", "configurePython.selectFileLabel": "選取", "configurePython.descriptionWithKernel": "'{0}' 核心需要設定 Python 執行階段並安裝相依性。", - "configurePython.existingInstall": "使用現有的 Python 安裝", + "configurePythyon.existingInstance": "{0} (目前的 Python 執行個體)", "configurePythyon.customPathLabel": "{0} (自訂)", - "configurePythyon.defaultPathLabel": "{0} (預設)", "configurePythyon.dropdownPathLabel": "{0} (Python {1})" }, "dist/dialog/configurePython/configurePythonWizard": { @@ -190,28 +186,14 @@ "errNotebookUriMissing": "筆記本路徑為必要項" }, "dist/jupyter/jupyterServerInstallation": { - "msgShutdownNotebookSessions": "為了進行更新，將關閉使用中的 Python 筆記本工作階段。您要立即繼續嗎?", "msgWaitingForInstall": "目前在進行另一個 Python 安裝。請等它完成。", - "msgPythonRunningError": "當 Python 正在執行時，無法覆寫現有的 Python 安裝。請先關閉所有使用中的筆記本再繼續。", - "dontAskAgain": "不要再詢問", - "msgDownloadPython": "正在將平台的本機 python: {0} 下載至 {1}", - "msgPythonDownloadPending": "正在下載 python 套件", "msgGetPythonUserDirFailed": "取得 Python 使用者路徑時發生錯誤: {0}", "msgPackageRetrievalFailed": "嘗試擷取已安裝套件的清單時發生錯誤: {0}", - "msgPythonDirectoryError": "建立 python 安裝目錄時發生錯誤", - "msgPythonDownloadError": "下載 python 設定時發生錯誤", - "msgPythonUnpackError": "將 python 套件組合解壓縮時發生錯誤", "msgTaskName": "正在安裝 Notebook 相依性", "msgDependenciesInstallationFailed": "安裝 Notebook 相依性失敗。錯誤: {0}", "msgInstallPkgStart": "正在安裝 Notebook 相依性，請參閱 [工作] 檢視以取得詳細資訊", - "no": "否", "msgInstallPkgFinish": "Notebook 相依性安裝完成", - "msgInstallPkgProgress": "正在安裝 Notebook 相依性", - "msgPythonDownloadComplete": "Python 下載完成", - "msgPythonVersionUpdatePrompt": "Azure Data Studio 現已提供 Python {0}。目前的 Python 版本 (3.6.6) 將在 2021 年 12 月時取消支援。您要立即更新為 Python {0} 嗎?", - "msgPythonVersionUpdateWarning": "將安裝 Python {0} 並取代 Python 3.6.6。某些套件可能不再與新版本相容，或可能需要重新安裝。將建立筆記本以協助您重新安裝所有 pip 套件。您要立即繼續更新嗎?", - "msgPythonUnpackPending": "正在解壓縮 python 套件", - "yes": "是" + "msgInstallPkgProgress": "正在安裝 Notebook 相依性" }, "dist/jupyter/jupyterServerManager": { "shutdownError": "無法關閉 Notebook 伺服器: {0}" diff --git a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.sql-migration.i18n.json b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.sql-migration.i18n.json index 6e2d0988afd0..99e2923a6c6a 100644 --- a/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.sql-migration.i18n.json +++ b/i18n/ads-language-pack-zh-hant/translations/extensions/Microsoft.sql-migration.i18n.json @@ -28,6 +28,7 @@ "sql.migration.bc.info": "因為必須將三個次要複本設為 Always On 高可用性群組，所以企業關鍵服務層的 SQL 受控執行個體完全移轉所花費的時間會明顯超出一般用途。作業的持續時間取決於資料的大小。90% 案例的植入速度為 220 GB/小時或更高。", "sql.migration.dashboard.help.description.dmsGuide": "移轉文章的中樞，提供在 Azure 中移轉和讓資料資產現代化的逐步指引。", "sql.migration.resource.group.description": "資源群組是能夠存放 Azure 解決方案相關資源的容器。", + "sql.migration.target.provisioning.template.display.limit": "單一 ARM 範本的部署限制上限為 50 Azure SQL 資料庫。前 50 個資料庫的範本顯示如下。若要檢視所有範本，請將範本 JSON 檔案儲存在本機儲存體或 Azure Blob 儲存體中。", "sql.migration.pre.req.2": "在內部部署或 Azure 虛擬機器上的 SQL Server 上執行的來源 SQL Server 資料庫，或雲端中執行的任何虛擬機器 (私人、公用)。", "sql.migration.dashboard.help.description.sqldb": "將資料庫從 SQL Server 執行個體 (內部部署或 Azure 虛擬機器) 移轉至 Azure SQL 資料庫的逐步教學課程。", "sql.migration.dashboard.help.description.mi": "將資料庫從 SQL Server 執行個體 (內部部署或 Azure 虛擬機器) 移轉到 Azure SQL 受控執行個體的逐步教學課程，停機時間最短。", @@ -43,6 +44,7 @@ "sql.migration.all.backups.restored": "已還原所有備份", "sql.migration.view.all": "所有資料庫移轉", "sql.migration.all.fields.required": "所有欄位都是必要欄位。", + "sql.ir.version.mismatch": "所有節點都應位於相同的版本，才能設定", "sql.migration.all.source.tables.empty": "所有來源資料表都是空白。沒有資料表可供選取以進行資料移轉。但若它們不存在於目標上，則它們可供結構描述移轉使用。", "sql.migration.unavailable.source.tables.heading": "下列所有資料表都是空白。沒有資料表可供選取以進行資料移轉。但如果它們不存在於目標上，則結構描述移轉可供使用。", "sql.migration.missing.tables.heading": "目標上遺漏下列所有資料表。若要移轉這些資料表中的資料，請選取上方的 [移轉結構描述] 選項。", @@ -78,7 +80,7 @@ "sql.cancel.migration.confirmation": "確定要取消此移轉嗎?", "sql.delete.migration.confirmation": "確定要刪除此刪除嗎?", "sql.migration.migration.list.ascending.label": "遞增", - "sql.migration.database.assessment.xevents.title": "評估擴充事件工作階段", + "sql.migration.database.assessment.xevents.title": "評估臨機操作或動態 SQL", "sql.migration.assessed.dbs.label": "評定的資料庫: {0}", "sql.migration.assessment.findings.label": "評定結果", "sql.migration.assessment.in.progress": "評定正在進行中", @@ -102,9 +104,11 @@ "sql.migration.ir.page.title": "Azure 資料庫移轉服務", "sql.migration.service.ready": "Azure 資料庫移轉服務 '{0}' 已連線到執行自我裝載整合執行階段的節點 - {1}\r\n\r\n為了提升效能和高可用性，您可以註冊其他節點。", "sql.migration.service.ready.below": "Azure 資料庫移轉服務 '{0}' 已連線到執行自我裝載整合執行階段的節點 - {1}\r\n\r\n為了提升效能和高可用性，您可以註冊其他節點。請參閱下方的註冊指示。", + "sql.migration.service.ready.without.nodes": "Azure 資料庫移轉服務 '{0}' 已連線到在下列節點上執行的自我裝載整合執行階段", "sql.migration.service.header": "Azure 資料庫移轉服務 \"{0}\" 詳細資料:", "sql.migration.service.not.ready": "Azure 資料庫移轉服務未註冊。Azure 資料庫移轉服務 '{0}' 必須向在任何節點上的自我裝載整合執行階段註冊。", "sql.migration.service.not.ready.below": "未註冊 Azure 資料庫移轉服務。Azure 資料庫移轉服務 '{0} ' 必須向在任何節點上的自我裝載整合執行階段註冊。\r\n\r\n請參閱下方的註冊指示。", + "sql.migration.ir.container.description": "Azure 資料庫移轉服務利用 Azure Data Factory 的自我裝載整合執行階段，將備份從內部部署網路檔案共用上傳到 Azure。根據上一頁的選取項目，您必須設定自我裝載整合執行階段。", "sql.migration.service.container.container.description1": "Azure 資料庫移轉服務利用 Azure Data Factory 的自我裝載整合執行階段，處理來源與目標之間的連線，並將內部部署網路檔案共用的備份上傳到 Azure (若適用)。", "sql.migration.services.name": "Azure 資料庫移轉服務名稱。", "sql.migration.ir.page.description": "Azure 資料庫移轉服務可協調資料庫移轉活動並追蹤其進度。如果您之前已建立資料庫移轉服務，可選取現有的資料庫移轉服務，或是在下方建立一個新的。", @@ -138,6 +142,7 @@ "sql.migration.dms.location": "您的 Azure 資料庫移轉服務的 Azure 區域。只會顯示包含服務的區域。", "sql.migration.services.location": "Azure 資料庫移轉服務的 Azure 區域。這應該是與目標 Azure SQL 相同的區域。", "sql.migration.sku.location": "您的 Azure SQL 目標的 Azure 區域。只會顯示包含符合移轉目標的區域。", + "sql.migration.storage.account.location": "儲存體帳戶的 Azure 地區。只會顯示包含儲存體帳戶的區域。", "sql.migration.summary.azure.storage": "Azure 儲存體", "sql.migration.validate.ir.validation.result.label.storage": "Azure 儲存體連線能力", "sql.migration.summary.azure.storage.subscription": "Azure 儲存體訂用帳戶", @@ -149,6 +154,7 @@ "sql.migration.backup.file.backup.size": "備份大小 (MB)", "sql.migration.backup.start.time": "備份開始時間", "sql.migration.wizard.sku.all": "根據評定結果，您所有在線上狀態的 {0} 個資料庫都可以移轉到 Azure SQL。", + "sql.migration.target.provisioning.description": "以下是建議的目標 SKU 的 ARM 指令碼。您可以將指令碼儲存為範本。", "sql.migration.sku.targetStorageConfiguration.info": "以下是滿足儲存體效能需求所需的目標儲存體設定。", "sql.migration.blob.container.title": "Blob 容器", "sql.migration.blob.container.label": "Blob 容器資源群組", @@ -202,6 +208,7 @@ "sql.migration.error.aria.view.details": "按一下以檢視錯誤詳細資料", "sql.migration.service.details.button.label": "關閉", "sql.migration.close": "關閉", + "sql.migration.target.provisioning.close": "關閉", "sql.migration.sku.azureRecommendation.collectData.method": "立即收集效能資料", "sql.login.migration.collecting.target.logins.failed": "收集目標登入失敗，錯誤碼為 {0}", "sql.migration.status.collectioncompleted": "收集完成", @@ -219,6 +226,9 @@ "sql.migration.completing.cutover.warning": "完成完全移轉而不還原所有備份可能會造成資料遺失。", "sql.migration.restore.status.completing.migration": "正在完成移轉", "sql.migration.save.close.popup": "已儲存設定。效能資料收集仍會在背景執行。您可以在想要時停止集合。", + "sql.migration.configure.ir": "設定整合執行階段", + "sql.ir.configure.manually": "手動設定 ", + "sql.ir.configure.powershellscript": "使用 PowerShell 指令碼設定 ", "sql.migration.connection.label": "連線", "sql.migration.community.support.description": "連結 Microsoft 社群", "sql.migration.wizard.target.connection.error": "連線錯誤: {0}", @@ -305,6 +315,7 @@ "sql.migration.description": "描述", "sql.migration.details.title": "詳細資料", "sql.migration.details.copied": "已複製詳細資料", + "sql.migration.validate.ir.error.message": "{0} 的詳細資料為必要但現缺少。", "sql.migration.field.label.deteected.files": "偵測到的檔案", "sql.migration.dashboard.description": "判斷您 SQL Server 執行個體的移轉整備度、識別建議的 Azure SQL 目標，並完成將您的 SQL Server 執行個體移轉到 Azure SQL 受控執行個體、Azure 虛擬機器上的 SQL Server 或 Azure SQL Database。", "sql.migration.restore.backuptype.differentialdatabase": "差異資料庫", @@ -344,6 +355,7 @@ "sql.migration.source.details.windowAuth.nonDb": "輸入用來連線到 SQL Server 執行個體 {0} 的 Windows 驗證認證。這些認證將用來連線到 SQL Server 執行個體，並識別有效的備份檔案。", "sql.migration.source.details.windowAuth.db": "輸入用來連線到 SQL Server 執行個體 {0} 的 Windows 驗證認證。這些認證將用來將自我裝載整合執行階段連線到 SQL Server 執行個體。", "sql.migration.enter.your.sql.cred": "輸入來源 SQL Server 執行個體的認證。將資料庫移轉到 Azure SQL 時，將會使用此認證。", + "sql.migration.select.storage.account.heading": "在下方輸入詳細資料以選取 Azure 儲存體帳戶，並將指令碼儲存為範本", "sql.migration.services.container.description": "請在下方輸入資訊，以新增 Azure 資料庫移轉服務。", "sql.migration.services.container.description.network": "請在下方輸入資訊，以新增一個新的 Azure 資料庫移轉服務。若要註冊自我裝載整合執行階段，請在上一頁選取 [我的資料庫備份在網路共用上]。", "sql.migration.sku.parameters.text": "請在下方輸入資訊以編輯建議參數。", @@ -362,6 +374,8 @@ "sql.migration.select.azure.mi.db.count.threshold.exceeds.error": "錯誤: Azure SQL 受控執行個體的每個執行個體最多支援 {0} 個使用者資料庫。請選取 {0} 個以下的資料庫才能繼續。", "sql.login.migration.migrate.server.roles.and.set.permissions": "建立使用者對應已完成。\r\n\r\n目前正在移轉伺服器角色、建立伺服器對應及設定權限。這需要一些時間。", "sql.login.migration.establish.user.mappings.failed": "建立使用者對應失敗", + "sql.ir.powershellscript": "執行指令碼 ", + "sql.ir.executing.powershellscript": "已開始執行並監視開啟的 PowerShell 視窗。 ", "sql.migration.support.resources.description": "探索文件", "sql.migration.tde.wizard.optionads": "將我的憑證和私密金鑰匯出到目標。", "sql.migration.schema.fastfirstrow": "FASTFIRSTROW", @@ -376,6 +390,8 @@ "sql.login.migration.status.page.description.failed": "無法將 {0} 登入移轉至 {1} '{2}'", "sql.migration.notebook.open.error": "無法開啟移轉筆記本。", "sql.migration.dms.provision.failed": "無法佈建資料庫移轉服務。請稍待幾分鐘後再試一次。", + "sql.migration.target.provisioning.save.template.fail": "無法儲存 ARM 範本", + "sql.migration.target.provisioning.upload.template.fail": "無法上傳 ARM 範本", "sql.migration.tab.button.feedback.description": "意見反應", "sql.migration.tab.button.feedback.label": "意見反應", "sql.migration.feedback.issue.title": "對移轉體驗的意見反應", @@ -397,10 +413,11 @@ "sql.migration.service.container.container.description2": "請遵循下方的指示，設定自我裝載整合執行階段。", "sql.migration.database.table.selection.description": "針對下列每個資料庫，按一下 [編輯] 以選取要從來源移轉至目標的資料表。然後，在按一下 [下一步] 之前，請按一下 [執行驗證] 以驗證提供的設定。", "sql.migration.sql.vm.page.blob.info": "對於執行 SQL Server 2014 或更低版本的目標伺服器，您必須將資料庫備份儲存在 Azure 儲存體 Blob 容器中，而非使用網路共用選項將其上傳。此外，您必須將備份檔案儲存為分頁 Blob，因為只有執行 SQL Server 2016 或更新版本的目標才支援區塊 Blob。深入了解: {0}", - "sql.migration.database.assessment.xevents.description": "對於選取的資料庫，請選擇性地提供擴充事件工作階段檔案來評估臨機操作或動態 SQL 查詢，或透過應用程式資料圖層起始的任何 DML 陳述式。{0}", + "sql.migration.database.assessment.xevents.description": "對於選取的資料庫，請選擇性地提供擴充事件工作階段檔案來評估臨機操作或動態 SQL 查詢，或透過應用程式資料圖層起始的任何 DML 陳述式。", "sql.migration.full.backup.files": "完整備份檔案", "sql.migration.sku.azureConfiguration.gen5": "Gen5", "sql.migration.sku.azureConfiguration.generalPurpose": "一般目的", + "sql.migration.target.provisioning.generate.template": "產生範本", "sql.migration.status.generatingscript": "產生指令碼", "sql.migration.status.generatingcompleted": "產生指令碼完成", "sql.migration.sku.get.recommendation": "取得 Azure 建議", @@ -417,7 +434,11 @@ "sql.migration.confirm.checkbox.message": "我確認沒有其他記錄備份可提供並想要完成完全移轉。", "sql.migration.tde.wizard.optionadsconfirm": "我同意使用我的登入資訊來存取憑證。", "sql.migration.tde.wizard.optionmanual": "我已經將憑證和私密金鑰移轉到目標。", + "sql.ir.local.ir.definition": "我想要在另一部不是我的本機電腦的 Windows 電腦上設定自我裝載整合執行階段。", "sql.migration.sku.io.memory.requirement": "IO 延遲需求", + "sql.ir.ip.address": "IP 位址", + "sql.ir.config.type": "整合執行階段設定類型", + "sql.ir.ir.version": "整合執行階段版本", "sql.migration.empty.table.subtext": "如果預期結果，請驗證 SQL Server 執行個體的連線。", "sql.migration.wizard.cancel.reason.others.input.box.note": "如果您選取其他項目，請撰寫簡短備註。", "sql.migration.impact": "影響", @@ -427,6 +448,7 @@ "sql.migration.tab.import.migration.description": "將評定匯入 Azure SQL", "sql.migration.sku.import.performance.data": "匯入效能資料", "sql.migration.sku.import.performance.data.dialog.description": "從現有資料夾匯入此資料檔案 (如果您已使用 Data Migration Assistant 收集)。", + "sql.ir.important": "重要", "sql.migration.database.migration.migration.mode.tool.tip": "在 Azure 資料移轉服務中，您可以離線或在連線時移轉您的資料庫。在離線移轉中，應用程式停機時間會在移轉開始時開始。若要將停機時間限制為移轉後移轉至新環境所需的時間，請使用線上移轉。", "sql.migration.tde.validation.requirements.message": "為了讓憑證移轉成功，您必須符合下列所有需求。 \r\n\r\n按一下 [執行驗證] 以檢查是否符合需求。", "sql.migration.copy.status.inprogress": "進行中", @@ -484,6 +506,8 @@ "sql.login.migration.type": "登入類型", "sql.migration.sku.logs.iops.requirement": "記錄 IOPS 需求", "sql.migration.field.label.mi.restore.state": "受控執行個體還原狀態", + "sql.ir.manual.ir.collapsed": "手動整合執行階段設定已摺疊", + "sql.ir.manual.ir.expanded": "手動整合執行階段設定已展開", "sql.migration.map.target.heading": "將選取的來源資料庫對應到目標資料庫以進行移轉", "sql.migration.sku.azureConfiguration.premiumSeriesMemoryOptimized": "記憶體最佳化進階系列", "sql.migration.sku.memory.requirement": "記憶體需求", @@ -565,6 +589,7 @@ "sql.migration.tab.button.migration.label": "新增移轉", "sql.migration.newSupportRequest": "新增支援要求", "sql.migration.saved.assessment.next": "下一步", + "sql.migration.sku.azureConfiguration.nextGenGeneralPurpose": "新一代一般用途", "sql.migration.no": "否", "sql.migration.no.sqldatabaseserver.found": "找不到 Azure SQL Database 伺服器。", "sql.migration.no.sqldatabase.found": "找不到 Azure SQL 資料庫。", @@ -582,6 +607,7 @@ "sql.migration.no.issues.vm": "找不到在 Azure 虛擬機器上移轉到 SQL Server 的問題。", "sql.migration.no.location.found": "找不到任何位置。", "sql.migration.no.managedInstance.found": "找不到任何受控執行個體。", + "sql.ir.no.node.found": "找不到節點", "sql.migration.no.pending.backups": "沒有擱置的備份。按一下 [重新整理] 以檢查目前的狀態。", "sql.migration.cancel.feedback.no.reason.selected": "未選取原因", "sql.migration.wizard.sku.error.noRecommendation": "沒有可用的建議", @@ -591,6 +617,7 @@ "sql.migration.no.subscription.found": "找不到任何訂用帳戶。", "sql.migration.select.target.label": "未選取目標。選取目標以檢視評定摘要。", "sql.migration.no.virtualMachine.found": "找不到任何虛擬機器。", + "sql.ir.node.name": "節點名稱", "sql.migration.restore.status.none": "無", "sql.migration.restore.backupset.status.none": "無", "sql.migration.parallel.copy.type.none": "無", @@ -600,6 +627,7 @@ "sql.migration.not.ready": "未就緒", "sql.migration.restore.status.not.started": "未啟動", "sql.login.migration.steps.not.started": "未啟動", + "sql.ir.recommended.link": "注意: 請參閱自我裝載整合執行階段建議", "sql.migration.backup.file.number.of.stripes": "條紋數", "sql.migration.offline.caps": "OFFLINE", "sql.migration.ok": "確定", @@ -609,6 +637,7 @@ "sql.migration.schema.objects.collection": "物件已收集", "sql.migration.offline": "離線", "sql.migration.database.migration.mode.offline.label": "離線移轉", + "sql.ir.powershellscript.definition": "在 Powershell 中執行之後，下方顯示的唯一指令碼將會下載，並安裝自我裝載整合執行階段，然後向 Azure 資料移轉服務註冊。您必須在目標電腦上安裝 PowerShell。", "sql.migration.online": "上線", "sql.migration.database.migration.mode.online.label": "線上移轉", "sql.migration.open": "開啟", @@ -633,11 +662,15 @@ "sql.migration.service.selection.location.msg": "請選取資料庫備份檔案的位置，再繼續。", "sql.migration.cancel.feedback.reason.container.description": "請花一點時間告訴我們取消移轉的原因。這將協助我們改進體驗。", "sql.migration.port.label": "連接埠", + "sql.ir.powershell.script.saved": "Powershell 指令碼已儲存", + "sql.ir.ps.script.collapsed": "Powershell 指令碼已摺疊", + "sql.ir.ps.script.expanded": "Powershell 指令碼已展開", "sql.migration.status.prefetchobjects": "預先擷取物件", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsd": "進階 SSD", "sql.migration.sku.targetStorageConfiguration.disktype.PremiumSsdV2": "進階 SSD v2", "sql.migration.sku.azureConfiguration.premiumSeries": "進階系列", "sql.migration.copy.status.preparingforcopy": "正在準備", + "sql.ir.powershell.prereq": "必要條件: 需要具有執行身分系統管理員權限的 PowerShell。 ", "sql.login.migration.status.page.previous.button.title": "上一個 (已停用)", "sql.migration.tde.migrate.results.heading.previous": "之前的憑證移轉結果:", "sql.migration.provide.unique.containers": "為每個目標資料庫提供唯一的容器。受影響的資料庫: ", @@ -677,6 +710,7 @@ "sql.login.migration.refresh.target.login.data.failed": "從目標重新整理登入清單失敗", "sql.login.migration.refresh.login.data.successful": "重新整理登入清單成功。發現來源登入 {0}，找到目標登入 {1}", "sql.migration.resourceGroups": "資源群組", + "sql.migration.storage.account.resource.group.label": "資源群組", "sql.migration.rg.created": "已建立資源群組", "sql.migration.services.resource.group": "Azure 資料庫移轉服務的資源群組。", "sql.migration.dms.resource_group": "您的 Azure SQL 目標的資源群組。只會顯示包含服務的資源群組。", @@ -728,9 +762,13 @@ "sql.migration.sku.sql.logDisk": "SQL 記錄檔案", "sql.migration.sql.assessment.notebook.title": "SQL 移轉評定", "sql.migration.sku.sql.temp": "SQL tempdb", + "sql.migration.target.provisioning.save": "儲存", + "sql.migration.target.provisioning.title": "儲存範本", "sql.migration.save.close": "儲存後關閉", "sql.migration.save.assessment.report": "儲存評定報表", "sql.migration.save.recommendation.report": "儲存建議報告", + "sql.ir.save.script": "儲存指令碼", + "sql.migration.target.upload.to.azure": "儲存至 Azure Blob 容器", "sql.migration.saved.assessment.result": "已儲存的工作階段", "sql.migration.sku.parameters.scale.factor": "比例因素", "sql.migration.schema.data": "結構描述和資料", @@ -755,11 +793,13 @@ "sql.migration.restore.status.searching.backups": "正在搜尋備份", "sql.migration.wizard.troubleshooting": "如需更多疑難排解步驟，請參閱連結: https://aka.ms/dms-migrations-troubleshooting。", "sql.migration.select": "選取", + "sql.migration.select.storage.account.title": "選取 Azure 儲存體帳戶", "sql.migration.select.service.title": "選取資料庫移轉服務", "sql.migration.select.service.prompt": "選取資料庫移轉服務", "sql.migration.select.service.select.a.service": "選取資料庫移轉服務", "sql.migration.invalid.migration.service.offline.error": "選取連線到節點的資料庫移轉服務。", "sql.migration.status.select.service.MESSAGE": "選取要監視移轉的資料庫移轉服務。", + "sql.migration.select.storage.select.a.storage.account": "選取儲存體帳戶", "sql.migration.blob.container.select": "請先選取 BLOb 容器值。", "sql.migration.sku.import.performance.data.dialog.open.folder": "選取資料夾", "sql.migration.sku.import.performance.data.dialog.helper.message": "選取您本機磁碟機上的資料夾", @@ -857,13 +897,15 @@ "sql.migration.validate.ir.stop.validation": "停止驗證", "sql.migration.sku.azureRecommendation.stop.popup": "正在停止效能資料收集...", "sql.migration.sku.targetStorageConfiguration.storage": "儲存體", - "sql.migration.storage.account": "儲存體帳戶", + "sql.migration.select.storage.account.label": "儲存體帳戶", + "sql.migration.storage.account.details.label": "儲存體帳戶", "sql.migration.network.share.azure.header": "儲存體帳戶詳細資料", "sql.migration.subscription": "訂用帳戶", "sql.migration.blob.storage.subscription.label": "訂用帳戶", "sql.migration.dms.subscription": "Azure 資料庫移轉服務的訂用帳戶名稱", "sql.migration.services.subscription": "Azure 資料庫移轉服務的訂用帳戶名稱。", "sql.migration.sku.subscription": "Azure SQL 目標的訂用帳戶名稱", + "sql.migration.storage.account.subscription": "您儲存體帳戶的訂用帳戶名稱", "sql.migration.state.succeeded": "已成功", "sql.migration.tde.validation.status.succeeded": "已成功", "sql.migration.copy.status.succeeded": "已成功", @@ -910,6 +952,8 @@ "sql.migration.azure.sql.target": "目標類型", "sql.migration.username.label": "目標使用者名稱", "sql.migration.target.version": "目標版本", + "sql.migration.target.provisioning.save.template.success": "已成功儲存範本", + "sql.migration.target.provisioning.upload.template.success": "已成功上傳範本", "sql.migration.test.connection": "測試連接", "sql.migration.dashboard.help.description.migrateUsingADS": "Azure Data Studio 的 Azure SQL 移轉擴充功能提供評估、取得正確大小的 Azure 建議，以及將 SQL Server 資料庫移轉至 Azure 的功能。", "sql.migration.sqldb.not.ready": "SQL Database 伺服器 '{0}' 無法用於移轉，因為它目前處於'{1}'狀態。若要繼續，請選取可用的 SQL Database 伺服器。", @@ -983,7 +1027,10 @@ "sql.migration.status.uploadinglogbackup": "正在上傳記錄備份", "sql.migration.sqldb.column.usedparallelcopies": "使用的平行複本數", "sql.migration.path.user.account": "使用者帳戶", + "sql.migration.network.share.user.account.label": "使用者帳戶", "sql.migration.username": "使用者名稱", + "sql.migration.database.assessment.qds.label": "使用查詢資料存放區 (此選項適用於 Microsoft SQL Server 2016 及更新版本)", + "sql.migration.database.assessment.xevents.label": "使用擴充事件工作階段", "sql.migration.starting.login": "正在驗證及移轉登入", "sql.login.migration.establish.user.mappings": "驗證及移轉登入已完成。\r\n\r\n正在建立使用者對應。", "sql.migration.starting.login.failed": "驗證及移轉登入失敗", @@ -1021,6 +1068,7 @@ "sql.migration.completed.multi.steps.heading": "我們已執行以下步驟:", "sql.login.migration.wizard.target.data.migration.warning": "建議您先將資料庫移轉到 Azure SQL 目標，再開始登入移轉，以避免流程中發生失敗。不過，如果您的目標是更新最近移轉資料庫的使用者對應，您可以隨時執行此移轉流程。\r\n\r\n如果來源與資料庫名稱不同，則可能無法正確套用某些權限。", "sql.migration.blob.storage.folder.info": "將資料庫備份上傳到 Blob 容器時，請確定來自不同資料庫的備份檔案儲存在不同的資料夾中。只支援容器與資料夾最多一層深的根目錄。", + "sql.ir.local.ir.setup.note": "當您按下 [執行指令碼] 時，下方的 PowerShell 指令碼會自動下載自我裝載整合執行階段軟體、安裝，並與您的 Azure 資料移轉服務註冊。若要檢查整合執行階段的連線狀態，請返回上一個畫面並重新整理。 ", "sql.migration.sku.azureRecommendation.data.collection.popup.message.label": "您要將收集的資料儲存在哪裡?", "sql.migration.network.share.windows.user.label": "具有網路共用位置讀取存取權的 Windows 使用者帳戶。", "sql.migration.network.share.windows.user.info": "具有網路共用位置讀取存取權的 Windows 使用者帳戶。", @@ -1033,6 +1081,8 @@ "sql.migration.dms.resource": "您的 Azure 資料庫移轉服務資源名稱。", "sql.migration.sku.resource": "您的 Azure SQL 目標資源名稱", "sql.migration.sku.resource.port": "您的 Azure SQL 目標資源連接埠號碼: 0 - 65535", + "sql.migration.storage.account.blob.container": "您的 Blob 容器名稱", + "sql.migration.storage.account": "您的儲存體帳戶名稱", "sql.migration.pre.req.4": "您的資料庫備份位置詳細資料，網路檔案共用或 Azure Blob 儲存體容器 (Azure SQL Database 目標不需要)。", "sql.migration.wizard.sku.assessment.error.detail": "[沒有評定結果可驗證資料庫移轉的整備程度。選取此方塊，即表示您確認要繼續將資料庫移轉至所需的 Azure SQL 目標。]", "sql.migration.network.share.path.format": "\\\\Servername.domainname.com\\Backupfolder", diff --git a/resources/xlf/de/Microsoft.mssql.de.xlf b/resources/xlf/de/Microsoft.mssql.de.xlf index ac532423ab06..a16b57390960 100644 --- a/resources/xlf/de/Microsoft.mssql.de.xlf +++ b/resources/xlf/de/Microsoft.mssql.de.xlf @@ -845,7 +845,7 @@ Hinweis: Ein selbstsigniertes Zertifikat bietet nur eingeschränkten Schutz und Files Dateien - + Files Dateien @@ -1205,6 +1205,10 @@ Hinweis: Ein selbstsigniertes Zertifikat bietet nur eingeschränkten Schutz und Optimize Ad Hoc Workloads Ad-hoc-Workloads optimieren + + Options + Optionen + Original File Name Ursprünglicher Dateiname diff --git a/resources/xlf/de/Microsoft.notebook.de.xlf b/resources/xlf/de/Microsoft.notebook.de.xlf index 85f298867047..01f613bee7d0 100644 --- a/resources/xlf/de/Microsoft.notebook.de.xlf +++ b/resources/xlf/de/Microsoft.notebook.de.xlf @@ -384,14 +384,6 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern.Browse Durchsuchen - - Installation Type - Installationstyp - - - New Python installation - Neue Python-Installation - No supported Python versions found. Keine unterstützten Python-Versionen gefunden. @@ -401,12 +393,8 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern.Für Notebook-Kernel ist die Konfiguration einer Python-Runtime und die Installation von Abhängigkeiten erforderlich. - Python Install Location - Python-Installationsspeicherort - - - Python runtime configured! - Python-Runtime konfiguriert! + Python Location + Python-Speicherort Select @@ -416,18 +404,14 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern.The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. Für den "{0}"-Kernel ist die Konfiguration einer Python-Runtime und die Installation von Abhängigkeiten erforderlich. - - Use existing Python installation - Vorhandene Python-Installation verwenden + + {0} (Current Python Instance) + {0} (aktuelle Python-Instanz) {0} (Custom) {0} (Benutzerdefiniert) - - {0} (Default) - {0} (Standard) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern. - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - Aktive Python-Notebooksitzungen werden heruntergefahren, um sie zu aktualisieren. Möchten Sie jetzt fortfahren? - Another Python installation is currently in progress. Waiting for it to complete. Aktuell wird eine weitere Python-Installation ausgeführt. Es wird auf den Abschluss des Vorgangs gewartet. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Eine vorhandene Python-Installation kann nicht überschrieben werden, während Python ausgeführt wird. Schließen Sie alle aktiven Notebooks, bevor Sie fortfahren. - - - Don't Ask Again - Nicht mehr fragen - - - Downloading local python for platform: {0} to {1} - Lokales Python für die Plattform "{0}" wird nach "{1}" heruntergeladen. - - - Downloading python package - Das Python-Paket wird heruntergeladen. - Encountered an error when getting Python user path: {0} Fehler beim Abrufen des Python-Benutzerpfads: {0} @@ -708,18 +672,6 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern.Encountered an error when trying to retrieve list of installed packages: {0} Fehler beim Abrufen der Liste installierter Pakete: {0} - - Error while creating python installation directory - Fehler beim Erstellen des Python-Installationsverzeichnisses. - - - Error while downloading python setup - Fehler beim Herunterladen des Python-Setups. - - - Error while unpacking python bundle - Fehler beim Entpacken des Python-Pakets. - Installing Notebook dependencies Notebook-Abhängigkeiten werden installiert. @@ -732,10 +684,6 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern.Installing Notebook dependencies, see Tasks view for more information Notebook-Abhängigkeiten werden installiert. Weitere Informationen finden Sie in der Aufgabenansicht. - - No - Nein - Notebook dependencies installation is complete Die Installation von Notebook-Abhängigkeiten ist abgeschlossen. @@ -744,26 +692,6 @@ Die Datei wurde in "{2}" umbenannt, um einen Datenverlust zu verhindern.Notebook dependencies installation is in progress Notebook-Abhängigkeiten werden installiert. - - Python download is complete - Der Python-Download ist abgeschlossen. - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Python {0} ist jetzt in Azure Data Studio verfügbar. Die aktuelle Python-Version (3.6.6) wird ab Dezember 2021 nicht mehr unterstützt. Möchten Sie jetzt auf Python {0} aktualisieren? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Python {0} wird installiert und ersetzt Python 3.6.6. Einige Pakete sind möglicherweise nicht mehr mit der neuen Version kompatibel oder müssen neu installiert werden. Ein Notizbuch wird erstellt, damit Sie alle PIP-Pakete neu installieren können. Möchten Sie das Update jetzt fortsetzen? - - - Unpacking python package - Python-Paket entpacken - - - Yes - Ja - diff --git a/resources/xlf/de/Microsoft.sql-migration.de.xlf b/resources/xlf/de/Microsoft.sql-migration.de.xlf index f1b00c8d60ad..db75c77bac2e 100644 --- a/resources/xlf/de/Microsoft.sql-migration.de.xlf +++ b/resources/xlf/de/Microsoft.sql-migration.de.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. Eine Ressourcengruppe ist ein Container, der zugehörige Ressourcen für eine Azure-Lösung enthält. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + Für eine einzelne ARM-Vorlage gilt eine Bereitstellungsbeschränkung von maximal 50 Azure SQL-Datenbanken. Die Vorlage für die ersten 50 Datenbanken wird unten angezeigt. Um alle Vorlagen anzuzeigen, speichern Sie die JSON-Vorlagendatei in einem lokalen Speicher oder Azure Blob Storage. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). Eine oder mehrere SQL Server-Quelldatenbanken, die lokal oder auf SQL Server auf einer Azure-VM oder einem beliebigen virtuellen Computer in der Cloud (privat, öffentlich) ausgeführt werden. @@ -138,6 +142,10 @@ All fields are required. Alle Felder müssen ausgefüllt werden. + + All nodes should be on the same version to be configured + Alle Knoten müssen die gleiche Version aufweisen, um konfiguriert zu werden. + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. Alle Quelltabellen sind leer. Für die Datenmigration ist keine Tabelle zur Auswahl verfügbar. Sie sind jedoch für die Schemamigration verfügbar, wenn sie nicht auf dem Ziel vorhanden sind. @@ -279,8 +287,8 @@ Aufsteigend - Assess extended event sessions - Erweiterte Ereignissitzungen bewerten + Assess Ad-hoc or dynamic SQL + Ad-hoc- oder dynamisches SQL bewerten Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node Für bessere Leistung und Hochverfügbarkeit können Sie zusätzliche Knoten registrieren. Anweisungen zur Registrierung finden Sie unten. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure Database Migration Service „{0}“ ist mit einer selbstgehosteten Integration Runtime verbunden, die auf den folgenden Knoten ausgeführt wird + Azure Database Migration Service "{0}" details:` Details zum Azure Database Migration Service "{0}": @@ -398,6 +410,10 @@ See below for registration instructions. Anweisungen zur Registrierung finden Sie unten. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure Database Migration Service nutzt die selbstgehostete Integration Runtime von Azure Data Factory, um Sicherungen von der lokalen Netzwerk-Dateifreigabe in Azure hochzuladen. Basierend auf der Auswahl auf der vorherigen Seite müssen Sie eine selbstgehostete Integration Runtime einrichten. + 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). Azure Database Migration Service nutzt die selbstgehostete Integration Runtime von Azure Data Factory, um die Konnektivität zwischen Quelle und Ziel zu verarbeiten und Sicherungen von einer lokalen Netzwerkdateifreigabe in Azure hochzuladen (falls zutreffend). @@ -530,6 +546,10 @@ Anweisungen zur Registrierung finden Sie unten. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Azure-Region für Ihr Azure SQL-Ziel. Es werden nur Regionen angezeigt, die ein für die Migration geeignetes Ziel enthalten. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + Azure-Region für Ihr Speicherkonto. Es werden nur Regionen angezeigt, die ein Speicherkonto enthalten. + Azure storage Azure-Speicher @@ -574,6 +594,10 @@ Anweisungen zur Registrierung finden Sie unten. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. Basierend auf den Bewertungsergebnissen können alle {0} Ihrer Datenbanken in einem Onlinezustand zu Azure SQL migriert werden. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + Unten finden Sie das ARM-Skript für die empfohlene Ziel-SKU. Sie können das Skript als Vorlage speichern. + Below is the target storage configuration required to meet your storage performance needs. Unten finden Sie die Zielspeicherkonfiguration, die zur Erfüllung Ihrer Speicherleistungsanforderungen erforderlich ist. @@ -786,6 +810,10 @@ Anweisungen zur Registrierung finden Sie unten. Close Schließen + + Close + Schließen + Collect performance data now Leistungsdaten jetzt sammeln @@ -854,6 +882,18 @@ Anweisungen zur Registrierung finden Sie unten. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Konfiguration gespeichert. Die Leistungsdatensammlung wird weiterhin im Hintergrund ausgeführt. Sie können die Sammlung beenden, wenn Sie möchten. + + Configure Integration Runtime + Integration Runtime konfigurieren + + + Configure manually + Manuell konfigurieren + + + Configure using PowerShell script + Konfigurieren mithilfe eines PowerShell-Skripts + Connect Verbinden @@ -1198,6 +1238,10 @@ Anweisungen zur Registrierung finden Sie unten. Details copied Details kopiert + + Details for {0} are mandatory and missing. + Details zu „{0}“ sind obligatorisch und fehlen. + Detected files Erkannte Dateien @@ -1354,6 +1398,10 @@ Anweisungen zur Registrierung finden Sie unten. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Geben Sie die Anmeldeinformationen für die Quelle der SQL Server-Instanz ein. Diese Anmeldeinformationen werden beim Migrieren von Datenbanken zu Azure SQL verwendet. + + Enter the details below to select the Azure Storage account and save the script as template + Geben Sie unten die Details ein, um das Azure Storage-Konto auszuwählen und das Skript als Vorlage zu speichern. + Enter the information below to add a new Azure Database Migration Service. Geben Sie die folgenden Informationen ein, um einen neuen Azure Database Migration Service hinzuzufügen. @@ -1434,6 +1482,14 @@ Aktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berecht Establishing user mappings failed Fehler beim Einrichten von Benutzerzuordnungen. + + Execute script + Skript ausführen + + + Execution started and monitor the PowerShell window opened. + Die Ausführung wurde gestartet, und das geöffnete PowerShell-Fenster wird überwacht. + Explore documentation Dokumentation erkunden @@ -1490,6 +1546,14 @@ Aktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berecht Failed to provision a Database Migration Service. Wait a few minutes and then try again. Fehler beim Bereitstellen eines Database Migration Service. Warten Sie einige Minuten, und versuchen Sie es dann erneut. + + Failed to save ARM Template + Fehler beim Speichern der ARM-Vorlage + + + Failed to upload ARM Template + Fehler beim Hochladen der ARM-Vorlage + Feedback Feedback @@ -1575,8 +1639,8 @@ Aktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berecht Für Zielserver, auf denen SQL Server 2014 oder niedriger ausgeführt wird, müssen Sie Ihre Datenbanksicherungen in einem Azure Storage Blob Container speichern, anstatt sie mithilfe der Netzwerkfreigabeoption hochzuladen. Darüber hinaus müssen Sie die Sicherungsdateien als Seitenblobs speichern, da Blockblobs nur für Ziele unterstützt werden, die SQL Server 2016 oder höher ausführen. Weitere Informationen: {0} - 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} - Stellen Sie für die ausgewählten Datenbanken optional Sitzungsdateien für erweiterte Ereignisse bereit, um Ad-hoc- oder dynamische SQL-Abfragen oder DML-Anweisungen zu bewerten, die über die Anwendungsdatenschicht initiiert wurden. {0} + 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. + Stellen Sie für die ausgewählten Datenbanken optional Sitzungsdateien für erweiterte Ereignisse bereit, um Ad-hoc- oder dynamische SQL-Abfragen oder DML-Anweisungen zu bewerten, die über die Anwendungsdatenschicht initiiert wurden. Full backup file(s) @@ -1590,6 +1654,10 @@ Aktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berecht General purpose Allgemein + + Generate Template + Vorlage generieren + Generating script Skript wird generiert @@ -1654,10 +1722,26 @@ Aktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berecht I have already migrated my certificates and private keys to the target. Ich habe meine Zertifikate und privaten Schlüssel bereits zum Ziel migriert. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + Ich möchte die selbstgehostete Integration Runtime auf einem anderen Windows-Computer einrichten, der nicht mein lokaler Computer ist. + IO latency requirement E/A-Latenzanforderung + + IP address + IP-Adresse + + + IR configuration type + IR-Konfigurationstyp + + + IR version + IR-Version + If results were expected, verify the connection to the SQL Server instance. Wenn Ergebnisse erwartet wurden, überprüfen Sie die Verbindung mit der SQL Server-Instanz. @@ -1694,6 +1778,10 @@ Aktuell werden Serverrollen migriert, Serverzuordnungen eingerichtet und Berecht Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Importieren Sie diese Datendatei aus einem vorhandenen Ordner, wenn Sie diese Daten bereits mit dem Datenmigrations-Assistenten gesammelt haben. + + Important + Wichtig + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. In Azure Database Migration Service können Sie Ihre Datenbanken offline oder online migrieren. Bei einer Offline-Migration beginnt die Downtime der Anwendung, wenn die Migration beginnt. Um die Downtime auf die Zeit zu begrenzen, die Sie benötigen, um nach der Migration auf die neue Umgebung umzuschalten, verwenden Sie eine Online-Migration. @@ -1926,6 +2014,14 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Managed instance restore state Wiederherstellungsstatus der verwalteten Instanz + + Manual IR configuration collapsed + Manuelle IR-Konfiguration reduziert + + + Manual IR configuration expanded + Manuelle IR-Konfiguration erweitert + Map selected source databases to target databases for migration Zuordnen ausgewählter Quelldatenbanken zu Zieldatenbanken für die Migration @@ -2250,6 +2346,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Next Weiter + + Next-gen General Purpose + Universell der nächsten Generation + No Nein @@ -2318,6 +2418,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu No managed instances found. Keine verwalteten Instanzen gefunden. + + No node found + Kein Knoten gefunden. + No pending backups. Click refresh to check current status. Keine ausstehenden Sicherungen. Klicken Sie auf "Aktualisieren", um den aktuellen Status zu prüfen. @@ -2354,6 +2458,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu No virtual machines found. Keine VMs gefunden. + + Node name + Knotenname + None Keine @@ -2390,6 +2498,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Not started Nicht gestartet + + Note: Refer Self-hosted IR recommendations + Hinweis: Empfehlungen zur selbstgehosteten Integration Runtime + Number of stripes Anzahl von Bereichsstreifen @@ -2426,6 +2538,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Offline migration Offlinemigration + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + Nach der Ausführung in PowerShell lädt das unten gezeigte eindeutige Skript die selbstgehostete Integration Runtime herunter, installiert sie und registriert sie beim Azure Database Migration Service. PowerShell muss auf dem Zielcomputer installiert sein. + Online Online @@ -2522,6 +2638,18 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Port Port + + PowerShell script saved + PowerShell-Skript gespeichert + + + Powershell script collapsed + PowerShell-Skript reduziert + + + Powershell script expanded + PowerShell-Skript erweitert + Prefetch objects Objekte vorab abrufen @@ -2542,6 +2670,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Preparing Wird vorbereitet + + Prerequisite: Need PowerShell with execute as admin privileges. + Voraussetzung: Benötigen Sie PowerShell mit Ausführungsberechtigungen als Administrator. + Previous (Disabled) Zurück (deaktiviert) @@ -2698,6 +2830,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Resource group Ressourcengruppe + + Resource group + Ressourcengruppe + Resource group created Ressourcengruppe erstellt @@ -2902,6 +3038,14 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu SQL tempdb SQL tempdb + + Save + Speichern + + + Save Template + Vorlage speichern + Save and close Speichern und schließen @@ -2914,6 +3058,14 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Save recommendation report Empfehlungsbericht speichern + + Save script + Skript speichern + + + Save to Azure blob container + Speichern in Azure-Blob-Container + Saved session Gespeicherte Sitzung @@ -3010,6 +3162,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Select Auswählen + + Select Azure Storage Account + Azure Storage-Konto auswählen + Select Database Migration Service Database Migration Service auswählen @@ -3030,6 +3186,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Select a Database Migration Service to monitor migrations. Wählen Sie eine Database Migration Service aus, um Migrationen zu überwachen. + + Select a Storage Account + Speicherkonto auswählen + Select a blob container value first. Wählen Sie zuerst einen BLOB-Containerwert aus. @@ -3418,7 +3578,11 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Storage Speicher - + + Storage Account + Speicherkonto + + Storage account Speicherkonto @@ -3446,6 +3610,10 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Subscription name for your Azure SQL target Abonnementname für Ihr Azure SQL-Ziel + + Subscription name for your Storage Account + Abonnementname für Ihr Speicherkonto + Succeeded Erfolgreich @@ -3630,6 +3798,14 @@ Klicken Sie auf "Überprüfung ausführen", um zu überprüfen, ob die Anforderu Target version Zielversion + + Template saved successfully + Vorlage erfolgreich gespeichert + + + Template uploaded successfully + Vorlage erfolgreich hochgeladen + Test connection Verbindung testen @@ -3926,10 +4102,22 @@ Es ist jedoch zulässig, die Schemamigration fortzusetzen, und Azure Database Mi User account Benutzerkonto + + User account + Benutzerkonto + User name Benutzername + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + Mit Abfragedatenspeicher (diese Option ist für Microsoft SQL Server 2016 und höher verfügbar) + + + Using extended event session + Erweiterte Ereignissitzungen verwenden + Validating and migrating logins are in progress Überprüfen und Migrieren der Anmeldungen ist in Bearbeitung @@ -4090,6 +4278,10 @@ Wenn die Namen von Quelle und Datenbank nicht übereinstimmen, werden einige Ber When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. Stellen Sie beim Hochladen von Datenbanksicherungen in Ihren Blobcontainer sicher, dass Sicherungsdateien aus verschiedenen Datenbanken in separaten Ordnern gespeichert werden. Nur der Stamm des Containers und die Ordner auf höchstens einer Ebene werden unterstützt. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + Wenn Sie auf „Skript ausführen“ klicken, lädt das folgende PowerShell-Skript automatisch selbstgehostete Integration Runtime-Software herunter, installiert sie und registriert sie bei Ihrem Azure Database Migration Service. Um den Verbindungsstatus der IR zu überprüfen, wechseln Sie zurück zum vorherigen Bildschirm, und aktualisieren Sie. + Where do you want to save collected data? Wo möchten Sie gesammelte Daten speichern? @@ -4138,6 +4330,14 @@ Wenn die Namen von Quelle und Datenbank nicht übereinstimmen, werden einige Ber Your Azure SQL target resource port number : 0 - 65535 Ihre Azure SQL-Portnummer der Zielressource: 0 – 65535 + + Your Blob Container name + Name Ihres Blobcontainers + + + Your Storage Account name + Geben Sie einen Speicherkontonamen ein. + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). Details zum Speicherort Ihrer Datenbanksicherung, entweder eine Netzwerkdateifreigabe oder ein Azure Blob Storage- Container (für Azure SQL-Datenbankziele nicht erforderlich). diff --git a/resources/xlf/es/Microsoft.mssql.es.xlf b/resources/xlf/es/Microsoft.mssql.es.xlf index 5703668b8f03..021ff4031844 100644 --- a/resources/xlf/es/Microsoft.mssql.es.xlf +++ b/resources/xlf/es/Microsoft.mssql.es.xlf @@ -845,7 +845,7 @@ Nota: Un certificado autofirmado solo ofrece una protección limitada y no es un Files Archivos - + Files Archivos @@ -1205,6 +1205,10 @@ Nota: Un certificado autofirmado solo ofrece una protección limitada y no es un Optimize Ad Hoc Workloads Optimizar cargas de trabajo ad hoc + + Options + Opciones + Original File Name Nombre de archivo original diff --git a/resources/xlf/es/Microsoft.notebook.es.xlf b/resources/xlf/es/Microsoft.notebook.es.xlf index 16e17b617838..8e1d8d56cbe0 100644 --- a/resources/xlf/es/Microsoft.notebook.es.xlf +++ b/resources/xlf/es/Microsoft.notebook.es.xlf @@ -384,14 +384,6 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos.Browse Examinar - - Installation Type - Tipo de instalación - - - New Python installation - Nueva instalación de Python - No supported Python versions found. No se ha encontrado ninguna versión de Python compatible. @@ -401,12 +393,8 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos.Los kernel del cuaderno requieren que se configure un entorno de ejecución de Python y que se instalen dependencias. - Python Install Location - Ubicación de la instalación de Python - - - Python runtime configured! - El entorno de ejecución de Python se ha configurado. + Python Location + Ubicación de Python Select @@ -416,18 +404,14 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos.The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. El kernel de "{0}" requiere que se configure un entorno de ejecución de Python y que se instalen dependencias. - - Use existing Python installation - Usar la instalación de Python existente + + {0} (Current Python Instance) + {0} (Instancia de Python actual) {0} (Custom) {0} (personalizada) - - {0} (Default) - {0} (predeterminada) - {0} (Python {1}) {0} ({1} de Python) @@ -676,30 +660,10 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos. - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - Las sesiones del cuaderno de Python activas se cerrarán para poder actualizarse. ¿Desea continuar ahora? - Another Python installation is currently in progress. Waiting for it to complete. Otra instalación de Python está actualmente en curso. Esperando a que se complete. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - No se puede sobrescribir una instalación de Python existente mientras Python se está ejecutando. Cierre los cuadernos activos antes de continuar. - - - Don't Ask Again - No volver a preguntar - - - Downloading local python for platform: {0} to {1} - Descargando Python local para la plataforma: {0} a {1} - - - Downloading python package - Descargando paquete de Python - Encountered an error when getting Python user path: {0} Se ha encontrado un error al obtener la ruta de acceso del usuario de Python: {0} @@ -708,18 +672,6 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos.Encountered an error when trying to retrieve list of installed packages: {0} Se ha encontrado un error al intentar recuperar la lista de paquetes instalados: {0} - - Error while creating python installation directory - Error al crear el directorio de instalación de Python - - - Error while downloading python setup - Error al descargar la configuración de Python - - - Error while unpacking python bundle - Error al desempaquetar el paquete de Python - Installing Notebook dependencies Instalando dependencias de Notebook @@ -732,10 +684,6 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos.Installing Notebook dependencies, see Tasks view for more information Instalando dependencias de Notebook, consulte la vista Tareas para obtener más información - - No - No - Notebook dependencies installation is complete La instalación de las dependencias de Notebook se ha completado @@ -744,26 +692,6 @@ Se ha cambiado el nombre del archivo a {2} para evitar la pérdida de datos.Notebook dependencies installation is in progress La instalación de dependencias de Notebook está en curso - - Python download is complete - La descarga de Python está completa - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Python {0} ya está disponible en Azure Data Studio. La versión actual de Python (3.6.6) dejará de recibir soporte en diciembre de 2021. ¿Le gustaría actualizar a Python {0} ahora? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Se instalará Python {0} y reemplazará a Python 3.6.6. Es posible que algunos paquetes ya no sean compatibles con la nueva versión o que sea necesario volver a instalarlos. Se creará un cuaderno para ayudarle a reinstalar todos los paquetes de PIP. ¿Desea continuar con la actualización ahora? - - - Unpacking python package - Desempaquetando paquete de Python - - - Yes - Sí - diff --git a/resources/xlf/es/Microsoft.sql-migration.es.xlf b/resources/xlf/es/Microsoft.sql-migration.es.xlf index bc63b6ede840..3f65c0f8dc99 100644 --- a/resources/xlf/es/Microsoft.sql-migration.es.xlf +++ b/resources/xlf/es/Microsoft.sql-migration.es.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. Un grupo de recursos es un contenedor que tiene los recursos relacionados de una solución de Azure. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + Una sola plantilla de ARM tiene una limitación de implementación de un máximo de 50 bases de datos de Azure SQL. La plantilla de las primeras 50 bases de datos se muestra a continuación. Para ver todas las plantillas, guarde el archivo JSON de plantilla en un almacenamiento local o en Azure Blob Storage. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). Una(s) base(s) de datos SQL Server de origen que se ejecuta(n) localmente, o en SQL Server en Azure Virtual Machine o en cualquier máquina virtual que se ejecute en la nube (privada, pública). @@ -138,6 +142,10 @@ All fields are required. Todos los campos son obligatorios. + + All nodes should be on the same version to be configured + Todos los nodos deben estar en la misma versión que se va a configurar + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. Todas las tablas de origen están vacías. No hay ninguna tabla disponible para seleccionar para la migración de datos. Pero están disponibles para la migración de esquemas si no existen en el destino. @@ -279,8 +287,8 @@ Ascendente - Assess extended event sessions - Evaluar sesiones de eventos extendidos + Assess Ad-hoc or dynamic SQL + Evaluar SQL ad hoc o dinámico Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node Para mejorar el rendimiento y la alta disponibilidad, puede registrar nodos adicionales. Consulte la información siguiente para ver las instrucciones de registro. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure Database Migration Service "{0}" está conectado al entorno de ejecución de integración autohospedado que se ejecuta en los siguientes nodos + Azure Database Migration Service "{0}" details:` Detalles de Azure Database Migration Service "{0}":` @@ -398,6 +410,10 @@ See below for registration instructions. Consulte a continuación las instrucciones de registro. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure Database Migration Service aprovecha el entorno de ejecución de integración autohospedado de Azure Data Factory para cargar copias de seguridad desde un recurso compartido de archivos de red local en Azure. En función de las selecciones de la página anterior, deberá configurar un entorno de ejecución de integración autohospedado. + 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). 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). @@ -530,6 +546,10 @@ Consulte a continuación las instrucciones de registro. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Región de Azure para el destino de Azure SQL. Solo se mostrarán las regiones que contienen un destino apto para la migración. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + Región de Azure para la cuenta de almacenamiento. Solo se mostrarán las regiones que contengan una cuenta de almacenamiento. + Azure storage Azure Storage @@ -574,6 +594,10 @@ Consulte a continuación las instrucciones de registro. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. Según los resultados de la evaluación, las {0} bases de datos en estado de conexión se pueden migrar a Azure SQL. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + A continuación, se muestra el script de ARM para la SKU de destino recomendada. Puede guardar el script como plantilla. + Below is the target storage configuration required to meet your storage performance needs. A continuación se muestra la configuración de almacenamiento de destino necesaria para satisfacer sus necesidades de rendimiento de almacenamiento. @@ -786,6 +810,10 @@ Consulte a continuación las instrucciones de registro. Close Cerrar + + Close + Cerrar + Collect performance data now Recopilar datos de rendimiento ahora @@ -854,6 +882,18 @@ Consulte a continuación las instrucciones de registro. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Configuración guardada. La recopilación de datos de rendimiento seguirá ejecutándose en segundo plano. Puede detener la recopilación cuando desee. + + Configure Integration Runtime + Configuración del entorno de ejecución de integración + + + Configure manually + Configurar manualmente + + + Configure using PowerShell script + Configuración mediante el script de PowerShell + Connect Conectar @@ -1198,6 +1238,10 @@ Consulte a continuación las instrucciones de registro. Details copied Detalles copiados + + Details for {0} are mandatory and missing. + Los detalles de {0} son obligatorios; faltan estos detalles. + Detected files Archivos detectados @@ -1354,6 +1398,10 @@ Consulte a continuación las instrucciones de registro. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Escriba las credenciales para la instancia de SQL Server de origen. Estas credenciales se usarán al migrar las bases de datos a Azure SQL. + + Enter the details below to select the Azure Storage account and save the script as template + Escriba los detalles siguientes para seleccionar la cuenta de Azure Storage y guardar el script como plantilla. + Enter the information below to add a new Azure Database Migration Service. Escriba la información siguiente para agregar una nueva Azure Database Migration Service. @@ -1434,6 +1482,14 @@ Actualmente, migrando roles de servidor, estableciendo asignaciones de servidor Establishing user mappings failed Error al establecer asignaciones de usuario + + Execute script + Ejecutar script + + + Execution started and monitor the PowerShell window opened. + Se inició la ejecución y se supervisa la ventana de PowerShell abierta. + Explore documentation Explorar la documentación @@ -1490,6 +1546,14 @@ Actualmente, migrando roles de servidor, estableciendo asignaciones de servidor Failed to provision a Database Migration Service. Wait a few minutes and then try again. No se pudo aprovisionar el Database Migration Service. Espere unos minutos y vuelva a intentarlo. + + Failed to save ARM Template + No se pudo guardar la plantilla de ARM + + + Failed to upload ARM Template + No se pudo cargar la plantilla de ARM + Feedback Comentarios @@ -1575,8 +1639,8 @@ Actualmente, migrando roles de servidor, estableciendo asignaciones de servidor Para los servidores de destino que ejecutan SQL Server 2014 o inferior, debe almacenar las copias de seguridad de la base de datos en un contenedor de Azure Storage Blob en lugar de cargarlas mediante la opción de recurso compartido de red. Además, debe almacenar los archivos de copia de seguridad como blobs en páginas, ya que los blobs en bloques solo se admiten para destinos que ejecutan SQL Server 2016 o posterior. Más información: {0} - 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} - Para las bases de datos seleccionadas, puede proporcionar archivos de sesión de eventos extendidos para evaluar consultas SQL ad hoc o dinámicas, o cualquier instrucción DML iniciada a través de la capa de datos de la aplicación. {0} + 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. + Para las bases de datos seleccionadas, puede proporcionar archivos de sesión de eventos extendidos para evaluar consultas SQL ad hoc o dinámicas, o cualquier instrucción DML iniciada a través de la capa de datos de la aplicación. Full backup file(s) @@ -1590,6 +1654,10 @@ Actualmente, migrando roles de servidor, estableciendo asignaciones de servidor General purpose Uso general + + Generate Template + Generar plantilla + Generating script Generando script @@ -1654,10 +1722,26 @@ Actualmente, migrando roles de servidor, estableciendo asignaciones de servidor I have already migrated my certificates and private keys to the target. Ya he migrado mis certificados y claves privadas al destino. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + Quiero configurar el entorno de ejecución de integración autohospedado en otra máquina Windows que no sea mi equipo local. + IO latency requirement Requisito de latencia de E/S + + IP address + Dirección IP + + + IR configuration type + Tipo de configuración de IR + + + IR version + Versión de IR + If results were expected, verify the connection to the SQL Server instance. Si esperaba ver resultados, compruebe la conexión a la instancia de SQL Server. @@ -1694,6 +1778,10 @@ Actualmente, migrando roles de servidor, estableciendo asignaciones de servidor Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Importe este archivo de datos desde una carpeta existente, si ya lo ha recopilado mediante Data Migration Assistant. + + Important + Importante + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. En Azure Database Migration Service, puede migrar las bases de datos sin conexión o mientras están en línea. En una migración sin conexión, el tiempo de inactividad de la aplicación se inicia cuando se inicia la migración. Para limitar el tiempo de inactividad al tiempo que se tarda en pasar al nuevo entorno después de la migración, use una migración en línea. @@ -1926,6 +2014,14 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Managed instance restore state Estado de restauración de la instancia administrada + + Manual IR configuration collapsed + Configuración manual de IR contraída + + + Manual IR configuration expanded + Configuración manual de IR expandida + Map selected source databases to target databases for migration Asigne las bases de datos de origen seleccionadas a las bases de datos de destino para la migración @@ -2250,6 +2346,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Next Siguiente + + Next-gen General Purpose + De uso general de próxima generación + No No @@ -2318,6 +2418,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos No managed instances found. No se han encontrado instancias administradas. + + No node found + No se encontró ningún nodo + No pending backups. Click refresh to check current status. No hay copias de seguridad pendientes. Haga clic en actualizar para comprobar el estado actual. @@ -2354,6 +2458,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos No virtual machines found. No se encontró ninguna máquina virtual. + + Node name + Nombre del nodo + None Ninguno @@ -2390,6 +2498,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Not started No iniciado + + Note: Refer Self-hosted IR recommendations + Nota: Consulte las recomendaciones de IR autohospedado + Number of stripes Número de franjas @@ -2426,6 +2538,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Offline migration Migración sin conexión + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + Una vez ejecutado en PowerShell, el script único que se muestra a continuación se descargará, se instalará el entorno de ejecución de integración autohospedado y se registrará con Azure Database Migration Service. Deberá tener PowerShell instalado en la máquina de destino. + Online En línea @@ -2522,6 +2638,18 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Port Puerto + + PowerShell script saved + Script de PowerShell guardado + + + Powershell script collapsed + Script de PowerShell contraído + + + Powershell script expanded + Script de PowerShell expandido + Prefetch objects Captura previa de objetos @@ -2542,6 +2670,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Preparing Preparando + + Prerequisite: Need PowerShell with execute as admin privileges. + Requisito previo: necesita PowerShell con privilegios de ejecución como administrador. + Previous (Disabled) Anterior (deshabilitado) @@ -2698,6 +2830,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Resource group Grupo de recursos + + Resource group + Grupo de recursos + Resource group created Grupo de recursos creado @@ -2902,6 +3038,14 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos SQL tempdb Tempdb de SQL + + Save + Guardar + + + Save Template + Guardar plantilla + Save and close Guardar y cerrar @@ -2914,6 +3058,14 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Save recommendation report Guardar informe de recomendaciones + + Save script + Guardar script + + + Save to Azure blob container + Guardar contenedor de blobs de Azure + Saved session Sesión guardada @@ -3010,6 +3162,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Select Seleccionar + + Select Azure Storage Account + Seleccionar cuenta de Azure Storage + Select Database Migration Service Seleccionar Database Migration Service @@ -3030,6 +3186,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Select a Database Migration Service to monitor migrations. Seleccionar Database Migration Service para supervisar las migraciones. + + Select a Storage Account + Seleccionar una cuenta de almacenamiento + Select a blob container value first. Seleccione primero un valor de contenedor de blobs. @@ -3418,7 +3578,11 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Storage Almacenamiento - + + Storage Account + Cuenta de almacenamiento + + Storage account Cuenta de almacenamiento @@ -3446,6 +3610,10 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Subscription name for your Azure SQL target Nombre de la suscripción para su destino de Azure SQL + + Subscription name for your Storage Account + Nombre de suscripción de la cuenta de almacenamiento + Succeeded Correcto @@ -3630,6 +3798,14 @@ Haga clic en "Ejecutar validación" para comprobar que se cumplen los requisitos Target version Versión de destino + + Template saved successfully + La plantilla se guardó correctamente + + + Template uploaded successfully + Plantilla cargada correctamente + Test connection Conexión de prueba @@ -3926,10 +4102,22 @@ Sin embargo, se permite continuar con la migración del esquema y Azure Database User account Cuenta de usuario + + User account + Cuenta de usuario + User name Nombre de usuario + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + Utilizando el Almacén de datos de consultas (esta opción está disponible para Microsoft SQL Server 2016 y versiones posteriores) + + + Using extended event session + Utilizando la sesión de eventos extendidos + Validating and migrating logins are in progress Validación y migración de inicios de sesión en curso @@ -4090,6 +4278,10 @@ Esta operación puede tardar varios minutos. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. Al cargar copias de seguridad de bases de datos en el contenedor de blobs, asegúrese de que los archivos de copia de seguridad de diferentes bases de datos se almacenan en carpetas independientes. Solo se admite la raíz del contenedor y las carpetas con un nivel máximo de profundidad. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + Al hacer clic en "Ejecutar script", el siguiente script de PowerShell descargará automáticamente el software del entorno de ejecución de integración autohospedado, lo instalará y lo registrará con su Azure Database Migration Service. Para comprobar el estado de conexión del entorno de ejecución de integración, vuelva a la pantalla anterior y actualice. + Where do you want to save collected data? ¿Dónde desea guardar los datos recopilados? @@ -4138,6 +4330,14 @@ Esta operación puede tardar varios minutos. Your Azure SQL target resource port number : 0 - 65535 Nombre del puerto del recurso de destino de Azure SQL: 0 - 65535 + + Your Blob Container name + Nombre del contenedor de blobs + + + Your Storage Account name + Nombre de la cuenta de almacenamiento + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). Los detalles de la ubicación de la copia de seguridad de la base de datos, ya sea un recurso compartido de archivos de red o un contenedor de Azure Blob Storage (no es necesario para los destinos de Azure SQL Database). diff --git a/resources/xlf/fr/Microsoft.cms.fr.xlf b/resources/xlf/fr/Microsoft.cms.fr.xlf index 2a2fb9640b46..e36e978885c3 100644 --- a/resources/xlf/fr/Microsoft.cms.fr.xlf +++ b/resources/xlf/fr/Microsoft.cms.fr.xlf @@ -480,7 +480,7 @@ Strict (supported for SQL Server 2022 and Azure SQL) - Strict (supported for SQL Server 2022 and Azure SQL) + Strict (pris en charge pour SQL Server 2022 et Azure SQL) Support for managing SQL Server Central Management Servers diff --git a/resources/xlf/fr/Microsoft.mssql.fr.xlf b/resources/xlf/fr/Microsoft.mssql.fr.xlf index 0cb9a65b9453..0d9f10a4e8f5 100644 --- a/resources/xlf/fr/Microsoft.mssql.fr.xlf +++ b/resources/xlf/fr/Microsoft.mssql.fr.xlf @@ -845,7 +845,7 @@ Remarque : un certificat auto-signé offre uniquement une protection limitée et Files Fichiers - + Files Fichiers @@ -1205,6 +1205,10 @@ Remarque : un certificat auto-signé offre uniquement une protection limitée et Optimize Ad Hoc Workloads Optimiser les charges de travail ad hoc + + Options + Options + Original File Name Nom de fichier d'origine @@ -2668,7 +2672,7 @@ Remarque : un certificat auto-signé offre uniquement une protection limitée et Strict (supported for SQL Server 2022 and Azure SQL) - Strict (supported for SQL Server 2022 and Azure SQL) + Strict (pris en charge pour SQL Server 2022 et Azure SQL) The SQL Server language record name diff --git a/resources/xlf/fr/Microsoft.notebook.fr.xlf b/resources/xlf/fr/Microsoft.notebook.fr.xlf index c3ccc1d313c9..3eef88087ae9 100644 --- a/resources/xlf/fr/Microsoft.notebook.fr.xlf +++ b/resources/xlf/fr/Microsoft.notebook.fr.xlf @@ -384,14 +384,6 @@ Browse Parcourir - - Installation Type - Type d'installation - - - New Python installation - Nouvelle installation de Python - No supported Python versions found. Aucune version de Python prise en charge. @@ -401,12 +393,8 @@ Les noyaux de notebook nécessitent la configuration d'un runtime Python et l'installation de dépendances. - Python Install Location - Emplacement d'installation de Python - - - Python runtime configured! - Runtime python configuré ! + Python Location + Emplacement Python Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. Le noyau ’{0}’ nécessite la configuration d'un runtime Python et l'installation de dépendances. - - Use existing Python installation - Utiliser l'installation existante de Python + + {0} (Current Python Instance) + {0} (instance Python actuelle) {0} (Custom) {0} (Personnalisé) - - {0} (Default) - {0} (Par défaut) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - Les sessions de bloc-notes python actives seront arrêtées pour permettre la mise à jour. Voulez-vous continuer maintenant ? - Another Python installation is currently in progress. Waiting for it to complete. Une autre installation de Python est actuellement en cours. En attente de la fin de l'installation. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Impossible de remplacer une installation Python existante quand Python est en cours d'exécution. Fermez tous les notebooks actifs avant de continuer. - - - Don't Ask Again - Ne plus me poser la question - - - Downloading local python for platform: {0} to {1} - Téléchargement de la version locale de Python pour la plateforme : {0} dans {1} - - - Downloading python package - Téléchargement du package Python - Encountered an error when getting Python user path: {0} Erreur pendant l'obtention du chemin de l'utilisateur Python : {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} Erreur pendant la tentative de récupération de la liste des packages installés : {0} - - Error while creating python installation directory - Erreur de création du répertoire d'installation de Python - - - Error while downloading python setup - Erreur de téléchargement du programme d'installation de Python - - - Error while unpacking python bundle - Erreur de décompression du bundle Python - Installing Notebook dependencies Installation des dépendances de notebook @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information Installation des dépendances de notebook, consultez la vue Tâches pour plus d'informations - - No - Non - Notebook dependencies installation is complete L'installation des dépendances de notebook est terminée @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress L'installation des dépendances de notebook est en cours - - Python download is complete - Le téléchargement de Python est terminé - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Python {0} est désormais disponible dans Azure Data Studio. La version actuelle de Python (3.6.6) n’est plus prise en charge en décembre 2021. Voulez-vous effectuer une mise à jour vers python {0} maintenant ? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Python {0} sera installé et va remplacer python 3.6.6. Certains packages ne sont peut-être plus compatibles avec la nouvelle version ou doivent peut-être être réinstallés. Un bloc-notes va être créé pour vous aider à réinstaller tous les packages PIP. Voulez-vous continuer la mise à jour maintenant ? - - - Unpacking python package - Décompression du package Python - - - Yes - Oui - diff --git a/resources/xlf/fr/Microsoft.sql-migration.fr.xlf b/resources/xlf/fr/Microsoft.sql-migration.fr.xlf index 8ebb73e6264b..70e6818b9a5b 100644 --- a/resources/xlf/fr/Microsoft.sql-migration.fr.xlf +++ b/resources/xlf/fr/Microsoft.sql-migration.fr.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. Un groupe de ressources est un conteneur qui inclut les ressources associées à une solution Azure. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + Un modèle ARM unique a une limite de déploiement de 50 bases de données Azure SQL maximum. Le modèle des 50 premières bases de données est affiché ci-dessous. Pour afficher tous les modèles, enregistrez le fichier JSON de modèle dans un stockage local ou un stockage Blob Azure. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). Une ou plusieurs bases de données SQL Server sources s’exécutant localement ou sur SQL Server sur une machine virtuelle Azure ou une machine virtuelle exécutée dans le cloud (privé, public). @@ -138,6 +142,10 @@ All fields are required. Tous les champs sont requis. + + All nodes should be on the same version to be configured + Tous les nœuds doivent être sur la même version pour être configurés + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. Toutes les tables sources sont vides. Aucune table n’est disponible pour la migration des données. Mais ils sont disponibles pour la migration de schéma s’ils n’existent pas sur la cible. @@ -279,8 +287,8 @@ Ordre croissant - Assess extended event sessions - Évaluer les sessions d’événements étendues + Assess Ad-hoc or dynamic SQL + Évaluer SQL ad hoc ou dynamique Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node Pour une performance améliorée et une disponibilité élevée, vous pouvez inscrire des nœuds supplémentaires. Voir ci-dessous pour les instructions d’inscription. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure Database Migration Service « {0} » est connecté au runtime d'intégration auto-hébergé exécuté sur le(s) nœud(s) suivant(s) + Azure Database Migration Service "{0}" details:` Détails Azure Database Migration Service « {0} » : @@ -398,6 +410,10 @@ See below for registration instructions. Voir ci-dessous pour les instructions d’inscription. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure Database Migration Service exploite Microsoft Integration Runtime d’Azure Data Factory pour télécharger des sauvegardes depuis le partage de fichiers réseau sur site vers Azure. Sur la base des sélections de la page précédente, vous devrez configurer Microsoft Integration Runtime. + 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). Azure Database Migration Service tire parti du runtime d’intégration auto-hébergé de Azure Data Factory pour gérer la connectivité entre la source et la cible, et charger des sauvegardes à partir d’un partage de fichiers réseau local vers Azure (le cas échéant). @@ -530,6 +546,10 @@ Voir ci-dessous pour les instructions d’inscription. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Région Azure pour votre cible Azure SQL. Seules les régions qui contiennent une cible éligible pour la migration sont affichées. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + Région Azure pour votre compte de stockage. Seules les régions qui contiennent un compte de stockage sont affichées. + Azure storage Stockage Azure @@ -574,6 +594,10 @@ Voir ci-dessous pour les instructions d’inscription. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. En fonction des résultats de l’évaluation, toutes les {0} de vos bases de données dans un état en ligne peuvent être migrées vers Azure SQL. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + Vous trouverez ci-dessous le script ARM pour la référence SKU cible recommandée. Vous pouvez enregistrer le script en tant que modèle. + Below is the target storage configuration required to meet your storage performance needs. Vous trouverez ci-dessous la configuration de stockage cible requise pour répondre à vos besoins en termes de performances de stockage. @@ -786,6 +810,10 @@ Voir ci-dessous pour les instructions d’inscription. Close Fermer + + Close + Fermer + Collect performance data now Collectez les données de performance maintenant @@ -854,6 +882,18 @@ Voir ci-dessous pour les instructions d’inscription. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Configuration enregistrée. La collecte des données de performances continuera de s’exécuter en arrière-plan. Vous pouvez arrêter la collecte quand vous le souhaitez. + + Configure Integration Runtime + Configurer Microsoft Integration Runtime + + + Configure manually + Configurer manuellement + + + Configure using PowerShell script + Configurer à l’aide d’un script PowerShell + Connect Connecter @@ -1198,6 +1238,10 @@ Voir ci-dessous pour les instructions d’inscription. Details copied Détails copiés + + Details for {0} are mandatory and missing. + Les détails des {0} sont obligatoires et manquants. + Detected files Fichiers détectés @@ -1354,6 +1398,10 @@ Voir ci-dessous pour les instructions d’inscription. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Entrez les informations d’identification de l’instance de SQL Server source. Ces informations d’identification seront utilisées lors de la migration des bases de données vers Azure SQL. + + Enter the details below to select the Azure Storage account and save the script as template + Entrez les détails ci-dessous pour sélectionner le compte de stockage Azure et enregistrer le script en tant que modèle + Enter the information below to add a new Azure Database Migration Service. Entrez les informations ci-dessous pour ajouter une nouvelle Azure Database Migration Service. @@ -1434,6 +1482,14 @@ Actuellement, migration des rôles de serveur, établissement des mappages de se Establishing user mappings failed Échec de l’établissement du mappage d'utilisateur + + Execute script + Exécuter le script + + + Execution started and monitor the PowerShell window opened. + L’exécution a démarré et surveille la fenêtre PowerShell ouverte. + Explore documentation Explorer la documentation @@ -1490,6 +1546,14 @@ Actuellement, migration des rôles de serveur, établissement des mappages de se Failed to provision a Database Migration Service. Wait a few minutes and then try again. Échec de la mise en service d’un Database Migration Service. Patientez quelques minutes, puis réessayez. + + Failed to save ARM Template + Échec de l’enregistrement du modèle ARM + + + Failed to upload ARM Template + Échec du chargement du modèle ARM + Feedback Commentaires @@ -1575,8 +1639,8 @@ Actuellement, migration des rôles de serveur, établissement des mappages de se Pour les serveurs cibles exécutant SQL Server 2014 ou une version antérieure, vous devez stocker vos sauvegardes de base de données dans un conteneur Azure Storage Blob au lieu de les charger à l’aide de l’option de partage réseau. En outre, vous devez stocker les fichiers de sauvegarde sous forme d’objets blob de pages, car les objets blob de blocs sont pris en charge uniquement pour les cibles qui exécutent SQL Server 2016 ou version ultérieure. En savoir plus : {0} - 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} - Pour les bases de données sélectionnées, fournissez éventuellement des fichiers de session d’événements étendus pour évaluer les requêtes SQL ad hoc ou dynamiques, ou les instructions DML lancées via la couche données de l’application. {0} + 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. + Pour les bases de données sélectionnées, fournissez éventuellement des fichiers de session d'événements étendus pour évaluer les requêtes SQL ad hoc ou dynamiques ou toute instruction DML initiée via la couche de données d'application. Full backup file(s) @@ -1590,6 +1654,10 @@ Actuellement, migration des rôles de serveur, établissement des mappages de se General purpose Usage général + + Generate Template + Générer un modèle + Generating script Génération du script @@ -1654,10 +1722,26 @@ Actuellement, migration des rôles de serveur, établissement des mappages de se I have already migrated my certificates and private keys to the target. J'ai déjà migré mes certificats et clés privées vers la cible. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + Je souhaite configurer le runtime d'intégration auto-hébergé sur une autre machine Windows qui n'est pas ma machine locale. + IO latency requirement Exigence de latence d’E/S + + IP address + Adresse IP + + + IR configuration type + Type de configuration IR + + + IR version + Version du runtime d’intégration + If results were expected, verify the connection to the SQL Server instance. Si des résultats étaient attendus, vérifiez la connexion à l’instance SQL Server. @@ -1694,6 +1778,10 @@ Actuellement, migration des rôles de serveur, établissement des mappages de se Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Importez ce fichier de données à partir d'un dossier existant, si vous l'avez déjà collecté à l'aide de Data Migration Assistant. + + Important + Important + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. Dans Azure Database Migration Service, vous pouvez migrer vos bases de données hors connexion ou lorsqu'elles sont en ligne. Dans une migration hors ligne, le temps d'arrêt de l'application commence au démarrage de la migration. Pour limiter les temps d'arrêt au temps qu'il vous faut pour basculer vers le nouvel environnement après la migration, utilisez une migration en ligne. @@ -1926,6 +2014,14 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Managed instance restore state État de restauration de Managed Instance + + Manual IR configuration collapsed + Configuration du runtime d’intégration manuel réduite + + + Manual IR configuration expanded + Configuration IR manuelle étendue + Map selected source databases to target databases for migration Mapper les bases de données source sélectionnées aux bases de données cible pour la migration @@ -2250,6 +2346,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Next Suivant + + Next-gen General Purpose + La nouvelle génération d’appareils à usage général + No Non @@ -2318,6 +2418,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son No managed instances found. Aucune instance managée trouvée. + + No node found + Aucun nœud trouvé + No pending backups. Click refresh to check current status. Aucune sauvegarde en attente. Cliquez sur Actualiser pour vérifier l’état actuel. @@ -2354,6 +2458,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son No virtual machines found. Aucune machine virtuelle trouvée. + + Node name + Nom du nœud + None Aucun(e) @@ -2390,6 +2498,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Not started Non démarré + + Note: Refer Self-hosted IR recommendations + Remarque : consulter les recommandations du runtime d’IR auto-hébergé + Number of stripes Nombre de franges @@ -2426,6 +2538,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Offline migration Migration hors connexion + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + Une fois exécuté dans PowerShell, le script unique présenté ci-dessous téléchargera et installera le runtime d'intégration auto-hébergé et l'enregistrera auprès d’Azure Database Migration Service. Vous devrez avoir PowerShell installé sur la machine cible. + Online En ligne @@ -2522,6 +2638,18 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Port Port + + PowerShell script saved + Script PowerShell enregistré + + + Powershell script collapsed + Le script Powershell s'est effondré + + + Powershell script expanded + Script PowerShell développé + Prefetch objects Pré-récupérer des objets @@ -2542,6 +2670,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Preparing Préparation + + Prerequisite: Need PowerShell with execute as admin privileges. + Prérequis : Vous avez besoin de PowerShell avec des privilèges d’exécution en tant qu’administrateur. + Previous (Disabled) Précédent (désactivé) @@ -2698,6 +2830,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Resource group Groupe de ressources + + Resource group + Groupe de ressources + Resource group created Groupe de ressources créé @@ -2902,6 +3038,14 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son SQL tempdb base de données SQL + + Save + Enregistrer + + + Save Template + Enregistrer le modèle + Save and close Enregistrer et fermer @@ -2914,6 +3058,14 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Save recommendation report Enregistrer le rapport de recommandation + + Save script + Enregistrer le script + + + Save to Azure blob container + Enregistrer dans un conteneur blob Azure + Saved session Session enregistrée @@ -3010,6 +3162,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Select Sélectionner + + Select Azure Storage Account + Sélectionner le compte de stockage Azure + Select Database Migration Service Sélectionner Database Migration Service @@ -3030,6 +3186,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Select a Database Migration Service to monitor migrations. Sélectionnez un Database Migration Service pour surveiller les migrations. + + Select a Storage Account + Sélectionner un compte de stockage + Select a blob container value first. Sélectionnez d’abord une valeur de conteneur d’objets Blob. @@ -3418,7 +3578,11 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Storage Stockage - + + Storage Account + Compte de stockage + + Storage account Compte de stockage @@ -3446,6 +3610,10 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Subscription name for your Azure SQL target Nom de l’abonnement pour votre cible Azure SQL + + Subscription name for your Storage Account + Nom de l’abonnement pour votre compte de stockage + Succeeded Réussite @@ -3630,6 +3798,14 @@ Cliquez sur « Exécuter la validation » pour vérifier que les exigences son Target version Version cible + + Template saved successfully + Enregistrement du modèle réussi + + + Template uploaded successfully + Le modèle a été chargé avec succès + Test connection Tester la connexion @@ -3926,10 +4102,22 @@ Toutefois, il est autorisé à poursuivre la migration du schéma et Azure Datab User account Compte utilisateur + + User account + Compte utilisateur + User name Nom d'utilisateur + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + Utilisation du Magasin de données des requêtes (cette option est disponible pour Microsoft SQL Server 2016 et versions ultérieures) + + + Using extended event session + Utilisation d’une session d’événements étendue + Validating and migrating logins are in progress La validation et la migration des connexions sont en cours @@ -4090,6 +4278,10 @@ Si les noms de la source et de la base de données ne sont pas identiques, il es When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. Lorsque vous chargez des sauvegardes de base de données dans votre conteneur d'objets blob, assurez-vous que les fichiers de sauvegarde de différentes bases de données sont stockés dans des dossiers distincts. Seule la racine du conteneur et les dossiers d'au plus un niveau de profondeur sont pris en charge. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + Lorsque vous cliquez sur « exécuter le script », le script PowerShell ci-dessous télécharge automatiquement le logiciel d'exécution d'intégration auto-hébergé, l'installe et l'enregistre auprès de votre Database Migration Service Azure. Pour vérifier l’état de connexion du runtime d’intégration, revenez à l’écran précédent et actualisez. + Where do you want to save collected data? Où souhaitez-vous sauvegarder les données collectées ? @@ -4138,6 +4330,14 @@ Si les noms de la source et de la base de données ne sont pas identiques, il es Your Azure SQL target resource port number : 0 - 65535 Votre Azure SQL numéro de port de ressource cible : 0 - 65535 + + Your Blob Container name + Nom de votre conteneur Blob + + + Your Storage Account name + Votre nom de compte de stockage + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). Les détails de l’emplacement de sauvegarde de votre base de données, un partage de fichiers réseau ou un conteneur Stockage Blob Azure (non requis pour Azure SQL Database cibles). diff --git a/resources/xlf/it/Microsoft.mssql.it.xlf b/resources/xlf/it/Microsoft.mssql.it.xlf index 0174fa5b7474..a03f50f62ecc 100644 --- a/resources/xlf/it/Microsoft.mssql.it.xlf +++ b/resources/xlf/it/Microsoft.mssql.it.xlf @@ -845,7 +845,7 @@ Nota: un certificato autofirmato offre solo una protezione limitata e non è una Files File - + Files File @@ -1206,6 +1206,10 @@ Nota: un certificato autofirmato offre solo una protezione limitata e non è una Optimize Ad Hoc Workloads Ottimizza carichi di lavoro ad hoc + + Options + Opzioni + Original File Name Nome file originale diff --git a/resources/xlf/it/Microsoft.notebook.it.xlf b/resources/xlf/it/Microsoft.notebook.it.xlf index 2474292e017a..5def95ab7a05 100644 --- a/resources/xlf/it/Microsoft.notebook.it.xlf +++ b/resources/xlf/it/Microsoft.notebook.it.xlf @@ -384,14 +384,6 @@ Browse Sfoglia - - Installation Type - Tipo di installazione - - - New Python installation - Nuova installazione di Python - No supported Python versions found. Non sono state trovate versioni Python supportate. @@ -401,12 +393,8 @@ I kernel dei notebook richiedono la configurazione di un runtime Python e l'installazione delle dipendenze. - Python Install Location - Percorso di installazione di Python - - - Python runtime configured! - Il runtime Python è stato configurato. + Python Location + Percorso di Python Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. Il kernel '{0}' richiede la configurazione di un runtime Python e l'installazione delle dipendenze. - - Use existing Python installation - Usa l'installazione esistente di Python + + {0} (Current Python Instance) + {0} (Istanza Python corrente) {0} (Custom) {0} (Personalizzato) - - {0} (Default) - {0} (Predefinito) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - Le sessioni del notebook di Python attive verranno arrestate per l'aggiornamento. Procedere ora? - Another Python installation is currently in progress. Waiting for it to complete. È già in corso un'altra installazione di Python. Attendere che venga completata. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Non è possibile sovrascrivere un'installazione esistente di Python mentre Python è in esecuzione. Chiudere gli eventuali notebook attivi prima di procedere. - - - Don't Ask Again - Non chiedere più - - - Downloading local python for platform: {0} to {1} - Download della versione locale di Python per la piattaforma {0} in {1} - - - Downloading python package - Download del pacchetto Python - Encountered an error when getting Python user path: {0} Si è verificato un errore durante il recupero del percorso utente di Python: {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} Si è verificato un errore durante il tentativo di recuperare l'elenco dei pacchetti installati: {0} - - Error while creating python installation directory - Si è verificato un errore durante la creazione della directory di installazione di Python - - - Error while downloading python setup - Si è verificato un errore durante il download della configurazione di Python - - - Error while unpacking python bundle - Si è verificato un errore durante la decompressione del bundle di Python - Installing Notebook dependencies Installazione delle dipendenze di Notebook @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information Installazione delle dipendenze di Notebook. Per altre informazioni, vedere la visualizzazione attività - - No - No - Notebook dependencies installation is complete L'installazione delle dipendenze di Notebook è stata completata @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress L'installazione delle dipendenze di Notebook è in corso - - Python download is complete - Il download di Python è stato completato - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Python {0} è ora disponibile in Azure Data Studio. La versione corrente di Python (3.6.6) non sarà supportata da dicembre 2021. Eseguire ora l'aggiornamento a Python {0} ? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Python {0} verrà installato e sostituirà Python 3.6.6. Alcuni pacchetti potrebbero non essere più compatibili con la nuova versione o potrebbero dover essere reinstallati. Verrà creato un notebook che consente di reinstallare tutti i pacchetti pip. Continuare con l'aggiornamento ora? - - - Unpacking python package - Decompressione del pacchetto Python - - - Yes - Sì - diff --git a/resources/xlf/it/Microsoft.sql-migration.it.xlf b/resources/xlf/it/Microsoft.sql-migration.it.xlf index 07d1478a4635..79826d6be558 100644 --- a/resources/xlf/it/Microsoft.sql-migration.it.xlf +++ b/resources/xlf/it/Microsoft.sql-migration.it.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. Un gruppo di risorse è un contenitore che include le risorse correlate per una soluzione di Azure. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + Un singolo modello di ARM prevede un limite di distribuzione di un massimo di 50 database SQL di Azure. Il modello per i primi 50 database è visualizzato di seguito. Per visualizzare tutti i modelli, salvare il file JSON del modello in una risorsa di archiviazione locale o in una risorsa di archiviazione BLOB di Azure. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). Un database di SQL Server di origine in esecuzione in locale o in SQL Server su macchina virtuale di Azure o su qualsiasi macchina virtuale in esecuzione nel cloud (privato, pubblico). @@ -138,6 +142,10 @@ All fields are required. Tutti i campi sono obbligatori. + + All nodes should be on the same version to be configured + Tutti i nodi devono essere della stessa versione per essere configurati + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. Tutte le tabelle di origine sono vuote. Nessuna tabella disponibile per la selezione per la migrazione dei dati. Sono tuttavia disponibili per la migrazione dello schema se non esistono nella destinazione. @@ -279,8 +287,8 @@ Crescente - Assess extended event sessions - Valutare le sessioni di eventi estesi + Assess Ad-hoc or dynamic SQL + Valuta SQL ad hoc o dinamico Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node Per migliorare le prestazioni e la disponibilità elevata, è possibile registrare nodi aggiuntivi. Per istruzioni sulla registrazione, vedere di seguito. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Il Servizio Migrazione del database di Azure '{0}' è connesso al runtime di integrazione self-hosted in esecuzione sui seguenti nodi. + Azure Database Migration Service "{0}" details:` Dettagli sul Servizio Migrazione del database di Azure "{0}":` @@ -398,6 +410,10 @@ See below for registration instructions. Vedere di seguito per le istruzioni di registrazione. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Il Servizio Migrazione del database di Azure sfrutta il Microsoft Integration runtime di integrazione self-hosted di Azure Data Factory per caricare i backup dalla condivisione di rete locale in Azure. In base alle selezioni nella pagina precedente, sarà necessario configurare un Integration Runtime self-hosted. + 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). 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). @@ -530,6 +546,10 @@ Vedere di seguito per le istruzioni di registrazione. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Area di Azure per la destinazione Azure SQL. Verranno visualizzate solo le aree che contengono una destinazione idonea per la migrazione. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + Area di Azure per l'account di archiviazione. Verranno visualizzate solo le aree che contengono un account di archiviazione. + Azure storage Archiviazione di Azure @@ -574,6 +594,10 @@ Vedere di seguito per le istruzioni di registrazione. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. In base ai risultati della valutazione, è possibile eseguire la migrazione di tutti e {0} i database in stato online ad Azure SQL. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + Di seguito è riportato lo script ARM per lo SKU di destinazione consigliato. È possibile salvare lo script come modello. + Below is the target storage configuration required to meet your storage performance needs. Di seguito è riportata la configurazione dell'archiviazione di destinazione necessaria per soddisfare le esigenze di prestazioni di archiviazione. @@ -786,6 +810,10 @@ Vedere di seguito per le istruzioni di registrazione. Close Chiudi + + Close + Chiudi + Collect performance data now Raccogli ora i dati delle prestazioni @@ -854,6 +882,18 @@ Vedere di seguito per le istruzioni di registrazione. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Configurazione salvata. La raccolta dei dati sulle prestazioni rimarrà in esecuzione in background. È possibile arrestare la raccolta quando si vuole. + + Configure Integration Runtime + Configura Microsoft Integration Runtime + + + Configure manually + Configurazione manuale + + + Configure using PowerShell script + Configura usando lo script di PowerShell + Connect Connettere @@ -1198,6 +1238,10 @@ Vedere di seguito per le istruzioni di registrazione. Details copied Copia dei dettagli completata + + Details for {0} are mandatory and missing. + I dettagli per {0} sono obbligatori e mancanti. + Detected files File rilevati @@ -1354,6 +1398,10 @@ Vedere di seguito per le istruzioni di registrazione. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Immettere le credenziali per l'istanza di SQL Server di origine. Queste credenziali verranno usate durante la migrazione dei database ad Azure SQL. + + Enter the details below to select the Azure Storage account and save the script as template + Immettere i dettagli seguenti per selezionare l'account Archiviazione di Azure e salvare lo script come modello + Enter the information below to add a new Azure Database Migration Service. Immettere le informazioni di seguito per aggiungere un nuovo Servizio Migrazione del database di Azure. @@ -1434,6 +1482,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Establishing user mappings failed La definizione dei mapping utente non è riuscita + + Execute script + Esegui script + + + Execution started and monitor the PowerShell window opened. + Esecuzione avviata e monitoraggio della finestra di PowerShell aperta. + Explore documentation Esplora la documentazione @@ -1490,6 +1546,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Failed to provision a Database Migration Service. Wait a few minutes and then try again. Non è stato possibile effettuare il provisioning di un Servizio Migrazione del database. Attendere qualche minuto, quindi riprovare. + + Failed to save ARM Template + Non è stato possibile salvare il modello di ARM + + + Failed to upload ARM Template + Non è stato possibile caricare il modello di ARM + Feedback Feedback @@ -1575,8 +1639,8 @@ Currently, migrating server roles, establishing server mappings and setting perm Per i server di destinazione che eseguono SQL Server 2014 o versione precedente, è necessario archiviare i backup dei database in un contenitore BLOB del servizio di archiviazione di Azure invece di caricarli usando l'opzione condivisione di rete. È inoltre necessario archiviare i file di backup come BLOB di pagine, perché i BLOB in blocchi sono supportati solo per le destinazioni che eseguono SQL Server 2016 o versione successiva. Altre informazioni: {0} - 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} - È 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} + 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. + È 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. Full backup file(s) @@ -1590,6 +1654,10 @@ Currently, migrating server roles, establishing server mappings and setting perm General purpose Utilizzo generico + + Generate Template + Genera modello + Generating script Generazione dello script @@ -1654,10 +1722,26 @@ Currently, migrating server roles, establishing server mappings and setting perm I have already migrated my certificates and private keys to the target. Ho già eseguito la migrazione dei certificati e delle chiavi private alla destinazione. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + Voglio configurare il runtime di integrazione self-hosted in un altro computer Windows che non è il computer locale. + IO latency requirement Requisito latenza I/O + + IP address + Indirizzo IP + + + IR configuration type + Tipo di configurazione runtime di integrazione + + + IR version + Versione runtime di integrazione + If results were expected, verify the connection to the SQL Server instance. Se sono previsti risultati, verificare la connessione all'istanza di SQL Server. @@ -1694,6 +1778,10 @@ Currently, migrating server roles, establishing server mappings and setting perm Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Importa questo file di dati da una cartella esistente, se è già stato raccolto tramite Data Migration Assistant. + + Important + Importante + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. In Servizio Migrazione del database di Azure è possibile eseguire la migrazione dei database offline o mentre sono online. In una migrazione offline, il tempo di inattività dell'applicazione viene avviato all'avvio della migrazione. Per limitare il tempo di inattività al tempo necessario per eseguire il cutover nel nuovo ambiente dopo la migrazione, usare una migrazione online. @@ -1926,6 +2014,14 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Managed instance restore state Stato di ripristino dell'istanza gestita + + Manual IR configuration collapsed + Configurazione runtime di integrazione manuale compressa + + + Manual IR configuration expanded + Configurazione runtime di integrazione manuale espansa + Map selected source databases to target databases for migration Eseguire il mapping dei database di origine selezionati ai database di destinazione per la migrazione @@ -2250,6 +2346,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Next Avanti + + Next-gen General Purpose + Per utilizzo generico di nuova generazione + No No @@ -2318,6 +2418,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti No managed instances found. Non sono state trovate istanze gestite. + + No node found + Nessun nodo trovato + No pending backups. Click refresh to check current status. Nessun backup in sospeso. Fare clic su Aggiorna per controllare lo stato corrente. @@ -2354,6 +2458,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti No virtual machines found. Non sono state trovate macchine virtuali. + + Node name + Nome nodo + None Nessuno @@ -2390,6 +2498,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Not started Non avviato + + Note: Refer Self-hosted IR recommendations + Nota: vedere gli elementi consigliati del runtime di integrazione self-hosted + Number of stripes Numero di strisce @@ -2426,6 +2538,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Offline migration Migrazione offline + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + Una volta eseguito in PowerShell, lo script univoco visualizzato di seguito scaricherà e installerà il runtime di integrazione self-hosted e lo registrerà con il Servizio Migrazione del database di Azure. PowerShell deve essere installato nel computer di destinazione. + Online Online @@ -2522,6 +2638,18 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Port Porta + + PowerShell script saved + Script PowerShell salvato + + + Powershell script collapsed + Script PowerShell compresso + + + Powershell script expanded + Script powershell espanso + Prefetch objects Prelettura oggetti @@ -2542,6 +2670,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Preparing Preparazione + + Prerequisite: Need PowerShell with execute as admin privileges. + Prerequisito: è necessario PowerShell con privilegi di esecuzione come amministratore. + Previous (Disabled) Precedente (disabilitato) @@ -2698,6 +2830,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Resource group Gruppo di risorse + + Resource group + Gruppo di risorse + Resource group created Il gruppo di risorse è stato creato @@ -2902,6 +3038,14 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti SQL tempdb Tempdb SQL + + Save + Salva + + + Save Template + Salva modello + Save and close Salva e chiudi @@ -2914,6 +3058,14 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Save recommendation report Salvare report delle raccomandazioni + + Save script + Salva script + + + Save to Azure blob container + Salva in Contenitore BLOB di Azure + Saved session Sessione salvata @@ -3010,6 +3162,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Select Seleziona + + Select Azure Storage Account + Seleziona account di archiviazione di Azure + Select Database Migration Service Seleziona Servizio Migrazione del database @@ -3030,6 +3186,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Select a Database Migration Service to monitor migrations. Selezionare un Servizio di Migrazione del database per monitorare le migrazioni. + + Select a Storage Account + Selezionare un account di archiviazione + Select a blob container value first. Selezionare prima un valore del contenitore BLOB. @@ -3418,7 +3578,11 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Storage Archiviazione - + + Storage Account + Account di archiviazione + + Storage account Account di archiviazione @@ -3446,6 +3610,10 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Subscription name for your Azure SQL target Nome sottoscrizione per l’SQL Azure di destinazione + + Subscription name for your Storage Account + Nome della sottoscrizione per l'account di archiviazione + Succeeded Riuscito @@ -3630,6 +3798,14 @@ Fare clic su "Esegui convalida" per verificare che i requisiti siano soddisfatti Target version Versione di destinazione + + Template saved successfully + Salvataggio del modello completato + + + Template uploaded successfully + Il modello è stato caricato + Test connection Verifica connessione @@ -3926,10 +4102,22 @@ Esaminare quindi i risultati della valutazione e assicurarsi che tutti i problem User account Account utente + + User account + Account utente + User name Nome utente + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + Utilizzo di Query Data Store (questa opzione è disponibile per Microsoft SQL Server 2016 e versioni successive) + + + Using extended event session + Utilizzo della sessione eventi estesa + Validating and migrating logins are in progress La convalida e la migrazione degli account di accesso sono in corso @@ -4090,6 +4278,10 @@ L'operazione potrebbe richiedere qualche minuto. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. Durante il caricamento dei backup del database nel contenitore BLOB, assicurarsi che i file di backup di database diversi siano archiviati in cartelle separate. Sono supportate solo la radice del contenitore e delle cartelle a un massimo di un livello. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + Quando si fa clic su "Esegui script", lo script PowerShell seguente scaricherà automaticamente il software del runtime di integrazione self-hosted, lo installerà e lo registrerà con il Servizio Migrazione del database di Azure. Per controllare lo stato della connessione del runtime di integrazione, tornare alla schermata precedente e aggiornare. + Where do you want to save collected data? Dove si vogliono salvare i dati raccolti? @@ -4138,6 +4330,14 @@ L'operazione potrebbe richiedere qualche minuto. Your Azure SQL target resource port number : 0 - 65535 Numero di porta della risorsa di destinazione Azure SQL: 0 - 65535 + + Your Blob Container name + Nome del contenitore BLOB + + + Your Storage Account name + Nome dell'account di archiviazione + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). Dettagli del percorso di backup del database, una condivisione file di rete o un contenitore di Archiviazione BLOB di Azure (non necessario per destinazioni database SQL di Azure). diff --git a/resources/xlf/ja/Microsoft.mssql.ja.xlf b/resources/xlf/ja/Microsoft.mssql.ja.xlf index d8eaf68a3a0b..0c3e7ac151f8 100644 --- a/resources/xlf/ja/Microsoft.mssql.ja.xlf +++ b/resources/xlf/ja/Microsoft.mssql.ja.xlf @@ -845,7 +845,7 @@ Note: A self-signed certificate offers only limited protection and is not a reco Files ファイル - + Files ファイル @@ -1205,6 +1205,10 @@ Note: A self-signed certificate offers only limited protection and is not a reco Optimize Ad Hoc Workloads アドホック ワークロードの最適化 + + Options + オプション​​ + Original File Name 元のファイル名 diff --git a/resources/xlf/ja/Microsoft.notebook.ja.xlf b/resources/xlf/ja/Microsoft.notebook.ja.xlf index d1b9bd4b657c..5bea41eaeda1 100644 --- a/resources/xlf/ja/Microsoft.notebook.ja.xlf +++ b/resources/xlf/ja/Microsoft.notebook.ja.xlf @@ -384,14 +384,6 @@ Browse 参照 - - Installation Type - インストールの種類 - - - New Python installation - 新しい Python インストール - No supported Python versions found. サポートされている Python バージョンが見つかりません。 @@ -401,12 +393,8 @@ Notebook カーネルには、Python ランタイムが構成され、依存関係がインストールされている必要があります。 - Python Install Location - Python のインストール場所 - - - Python runtime configured! - Python ランタイムが構成されました! + Python Location + Python の場所 Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. '{0}' カーネルにって、Python ランタイムを構成し、依存関係をインストールする必要があります。 - - Use existing Python installation - 既存の Python インストールを使用する + + {0} (Current Python Instance) + {0} (現在の Python インスタンス) {0} (Custom) {0} (カスタム) - - {0} (Default) - {0} (既定値) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - 更新のために、アクティブな Python ノートブック セッションがシャットダウンされます。今すぐ続行しますか? - Another Python installation is currently in progress. Waiting for it to complete. 別の Python のインストールが現在進行中です。完了するのを待っています。 - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Python の実行中は、既存の Python インストールを上書きできません。続行する前に、アクティブなノートブックを閉じてください。 - - - Don't Ask Again - 今後このメッセージを表示しない - - - Downloading local python for platform: {0} to {1} - {0} から {1} にプラットフォーム用のローカル Python をダウンロードしています - - - Downloading python package - Python パッケージをダウンロードしています - Encountered an error when getting Python user path: {0} Python ユーザー パスの取得時にエラーが発生しました: {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} インストールされているパッケージの一覧を取得しようとしてエラーが発生しました: {0} - - Error while creating python installation directory - Python インストール ディレクトリの作成中にエラーが発生しました - - - Error while downloading python setup - Python セットアップのダウンロード中にエラーが発生しました - - - Error while unpacking python bundle - Python バンドルのアンパック中にエラーが発生しました - Installing Notebook dependencies Notebook 依存関係のインストール @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information Notebook 依存関係のインストールについて詳しくは、[タスク ビュー] を参照してください - - No - いいえ - Notebook dependencies installation is complete Notebook 依存関係のインストールが完了しました @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress Notebook 依存関係のインストールが進行中です - - Python download is complete - Python のダウンロードが完了しました - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Python {0} が Azure Data Studio で利用できるようになりました。現在の Python バージョン (3.6.6) は、2021 年 12 月にサポートされなくなります。今すぐ Python {0} に更新しますか? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Python {0} がインストールされ、Python 3.6.6 が置換されます。一部のパッケージは、新しいバージョンとの互換性がなくなったか、再インストールが必要になる可能性があります。すべての pip パッケージの再インストールを支援するためにノートブックが作成されます。今すぐ更新を続行しますか? - - - Unpacking python package - Python パッケージをアンパックしています - - - Yes - はい - diff --git a/resources/xlf/ja/Microsoft.sql-migration.ja.xlf b/resources/xlf/ja/Microsoft.sql-migration.ja.xlf index 57f4f7244e5b..a1458bd039b1 100644 --- a/resources/xlf/ja/Microsoft.sql-migration.ja.xlf +++ b/resources/xlf/ja/Microsoft.sql-migration.ja.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. リソース グループは、Azure のソリューションに関連するリソースを保持するコンテナーです。 + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + 1 つの ARM テンプレートには、最大 50 個の Azure SQL データベースというデプロイ制限があります。最初の 50 個のデータベースのテンプレートは、以下のように表示されます。すべてのテンプレートを表示するには、テンプレート JSON ファイルをローカル ストレージまたは Azure Blob Storage に保存します。 + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). オンプレミス、Azure 仮想マシン上のSQL Server、またはクラウドで実行されている任意の仮想マシン (プライベート、パブリック) で実行されているソース SQL Server データベース。 @@ -138,6 +142,10 @@ All fields are required. すべてのフィールドに入力してください。 + + All nodes should be on the same version to be configured + すべてのノードが同じバージョンに構成されている必要があります + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. すべてのソース テーブルが空です。データ移行用に選択できるテーブルはありません。ただし、ターゲットに存在しない場合は、スキーマの移行に使用できます。 @@ -279,8 +287,8 @@ 昇順 - Assess extended event sessions - 拡張イベント セッションの評価 + Assess Ad-hoc or dynamic SQL + アドホックまたは動的 SQL を評価する Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node パフォーマンスの向上と高可用性を実現したい場合は、追加のノードを登録できます。登録手順については以下をご覧ください。 + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure Database Migration Service '{0}' は、次のノードで実行されているセルフホステッド統合ランタイムに接続されています + Azure Database Migration Service "{0}" details:` Azure Database Migration Service ファイル "{0}" の詳細:` @@ -398,6 +410,10 @@ See below for registration instructions. 登録手順については以下をご覧ください。 + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure Database Migration Service は Azure Data Factory のセルフホステッド統合ランタイムを活用して、オンプレミスのネットワーク ファイル共有から Azure にバックアップをアップロードします。前のページの選択内容に基づいて、セルフホステッド統合ランタイムをセットアップする必要があります。 + 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). Azure Database Migration Service では、ソースとターゲットの間の接続の処理、および (該当する場合) オンプレミスのネットワーク ファイル共有から Azure へのバックアップのアップロードを、Azure Data Factory のセルフホステッド統合ランタイムを利用して行います。 @@ -530,6 +546,10 @@ See below for registration instructions. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Azure SQL ターゲット用途の Azure リージョン。移行先として適しているターゲットを含むリージョンのみが表示されます。 + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + ストレージ アカウントの Azure リージョン。ストレージ アカウントを含むリージョンのみが表示されます。 + Azure storage Azure Storage @@ -574,6 +594,10 @@ See below for registration instructions. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. 評価結果に基づくと、オンライン状態のデータベースのすべての {0} を Azure SQL に移行できます。 + + Below is the ARM script for the recommended target SKU. You can save the script as template. + おすすめのターゲット SKU の ARM スクリプトを次に示します。スクリプトをテンプレートとして保存できます。 + Below is the target storage configuration required to meet your storage performance needs. ストレージ パフォーマンスのニーズを満たすために必要なターゲット ストレージ構成を次に示します。 @@ -786,6 +810,10 @@ See below for registration instructions. Close 閉じる + + Close + 閉じる + Collect performance data now パフォーマンス データを今すぐ収集する @@ -854,6 +882,18 @@ See below for registration instructions. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. 構成が保存されました。パフォーマンス データの収集はバックグラウンドで実行されたままになります。必要に応じて、コレクションを停止できます。 + + Configure Integration Runtime + 統合ランタイムの構成 + + + Configure manually + 手動で構成 + + + Configure using PowerShell script + PowerShell スクリプトを使用して構成する + Connect 接続 @@ -1198,6 +1238,10 @@ See below for registration instructions. Details copied 詳細をコピー済み + + Details for {0} are mandatory and missing. + {0} の詳細は必須であり、見つかりません。 + Detected files 検出されたファイル @@ -1354,6 +1398,10 @@ See below for registration instructions. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. ソース SQL Server インスタンスの資格情報を入力します。これらの資格情報は、データベースを Azure SQL に移行する場合に使用されます。 + + Enter the details below to select the Azure Storage account and save the script as template + 以下に詳細を入力して Azure Storage アカウントを選択し、スクリプトをテンプレートとして保存します + Enter the information below to add a new Azure Database Migration Service. 以下の情報を入力して、新しい Azure Database Migration Service を追加します。 @@ -1434,6 +1482,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Establishing user mappings failed ユーザー マッピングの確立に失敗しました + + Execute script + スクリプトの実行 + + + Execution started and monitor the PowerShell window opened. + 実行が開始され、開かれた PowerShell ウィンドウを監視します。 + Explore documentation ドキュメントの探索 @@ -1490,6 +1546,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Failed to provision a Database Migration Service. Wait a few minutes and then try again. Database Migration Service をプロビジョニングできませんでした。数分待ってからもう一度やり直してください。 + + Failed to save ARM Template + ARM テンプレートを保存できませんでした + + + Failed to upload ARM Template + ARM テンプレートをアップロードできませんでした + Feedback フィードバック @@ -1575,8 +1639,8 @@ Currently, migrating server roles, establishing server mappings and setting perm SQL Server 2014 以下を実行しているターゲット サーバーでは、ネットワーク共有オプションを使用してデータベース バックアップをアップロードするのではなく、Azure Storage Blob コンテナーに格納する必要があります。また、ブロック BLOB はSQL Server 2016 以降を実行しているターゲットでのみサポートされているため、バックアップ ファイルをページ BLOB として保存する必要があります。詳細情報: {0} - 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} - 選択したデータベースに対して、必要に応じて拡張イベント セッション ファイルを提供して、アドホックまたは動的 SQL クエリ、またはアプリケーション データ レイヤーを介して開始された DML ステートメントを評価します。{0} + 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. + 選択したデータベースに対して、必要に応じて拡張イベント セッション ファイルを提供して、アドホックまたは動的 SQL クエリ、またはアプリケーション データ レイヤーを介して開始された DML ステートメントを評価します。 Full backup file(s) @@ -1590,6 +1654,10 @@ Currently, migrating server roles, establishing server mappings and setting perm General purpose 汎用 + + Generate Template + テンプレートの生成 + Generating script スクリプトを生成しています @@ -1654,10 +1722,26 @@ Currently, migrating server roles, establishing server mappings and setting perm I have already migrated my certificates and private keys to the target. 証明書と秘密鍵は既にターゲットに移行しています。 + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + ローカル マシンではない別の Windows マシンにセルフホステッド統合ランタイムをセットアップしたいと考えています。 + IO latency requirement IO 待機時間の要件 + + IP address + IP アドレス + + + IR configuration type + IR 構成の種類 + + + IR version + IR バージョン + If results were expected, verify the connection to the SQL Server instance. 結果が期待通りだった場合、SQL Server インスタンスへの接続を確認します。 @@ -1694,6 +1778,10 @@ Currently, migrating server roles, establishing server mappings and setting perm Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Data Migration Assistant を使用してこのデータ ファイルを既に収集している場合は、既存のフォルダーからインポートします。 + + Important + 重要 + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. Azure Database Migration Service では、データベースをオフラインにして移行するか、オンライン状態のまま移行することができます。オフライン移行では、移行の開始時にアプリケーションのダウンタイムが開始されます。ダウンタイムの長さを、移行後の新しい環境へのカットオーバー時間のみに限定するには、オンライン移行を使用します。 @@ -1926,6 +2014,14 @@ Click "Run validation" to check that requirements are met. Managed instance restore state マネージド インスタンスの復元状態 + + Manual IR configuration collapsed + 手動 IR 構成が折りたたまれています + + + Manual IR configuration expanded + 手動 IR 構成が展開されています + Map selected source databases to target databases for migration 選択したソース データベースを移行先データベースにマップする @@ -2250,6 +2346,10 @@ Click "Run validation" to check that requirements are met. Next 次へ + + Next-gen General Purpose + 次世代 General Purpose + No いいえ @@ -2318,6 +2418,10 @@ Click "Run validation" to check that requirements are met. No managed instances found. マネージド インスタンスが見つかりません。 + + No node found + ノードが見つかりません + No pending backups. Click refresh to check current status. 保留中のバックアップはありません。[最新の情報に更新] をクリックして、現在の状態を確認します。 @@ -2354,6 +2458,10 @@ Click "Run validation" to check that requirements are met. No virtual machines found. 仮想マシンが見つかりません。 + + Node name + ノード名 + None なし @@ -2390,6 +2498,10 @@ Click "Run validation" to check that requirements are met. Not started 未開始 + + Note: Refer Self-hosted IR recommendations + 注: セルフホステッド IR の推奨事項を参照してください + Number of stripes ストライプの数 @@ -2426,6 +2538,10 @@ Click "Run validation" to check that requirements are met. Offline migration オフライン移行 + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + PowerShell で実行すると、次に示す一意のスクリプトがダウンロードされ、セルフホステッド統合ランタイムがインストールされ、Azure Database Migration Service に登録されます。ターゲット マシンに PowerShell がインストールされている必要があります。 + Online オンライン @@ -2522,6 +2638,18 @@ Click "Run validation" to check that requirements are met. Port ポート + + PowerShell script saved + PowerShell スクリプトが保存されました + + + Powershell script collapsed + PowerShell スクリプトが折りたたまれています + + + Powershell script expanded + PowerShell スクリプトが展開されています + Prefetch objects プリフェッチ オブジェクト @@ -2542,6 +2670,10 @@ Click "Run validation" to check that requirements are met. Preparing 準備中 + + Prerequisite: Need PowerShell with execute as admin privileges. + 前提条件: 管理者特権として実行する PowerShell が必要です。 + Previous (Disabled) 前 (無効) @@ -2698,6 +2830,10 @@ Click "Run validation" to check that requirements are met. Resource group リソース グループ + + Resource group + リソース グループ + Resource group created リソース グループが作成されました @@ -2902,6 +3038,14 @@ Click "Run validation" to check that requirements are met. SQL tempdb SQL tempdb + + Save + 保存 + + + Save Template + テンプレートの保存 + Save and close 保存して閉じる @@ -2914,6 +3058,14 @@ Click "Run validation" to check that requirements are met. Save recommendation report 推奨事項レポートを保存する + + Save script + スクリプトの保存 + + + Save to Azure blob container + Azure BLOB コンテナーに保存する + Saved session 保存されたセッション @@ -3010,6 +3162,10 @@ Click "Run validation" to check that requirements are met. Select 選択 + + Select Azure Storage Account + Azure Storage アカウントの選択 + Select Database Migration Service Database Migration Service の選択 @@ -3030,6 +3186,10 @@ Click "Run validation" to check that requirements are met. Select a Database Migration Service to monitor migrations. 移行を監視する Database Migration Service を選択します。 + + Select a Storage Account + ストレージ アカウントの選択 + Select a blob container value first. 最初に BLOB コンテナーの値を選択します。 @@ -3418,7 +3578,11 @@ Click "Run validation" to check that requirements are met. Storage ストレージ - + + Storage Account + ストレージ アカウント + + Storage account ストレージ アカウント @@ -3446,6 +3610,10 @@ Click "Run validation" to check that requirements are met. Subscription name for your Azure SQL target Azure SQL ターゲットのサブスクリプション名 + + Subscription name for your Storage Account + ストレージ アカウントのサブスクリプション名 + Succeeded 成功 @@ -3630,6 +3798,14 @@ Click "Run validation" to check that requirements are met. Target version ターゲット バージョン + + Template saved successfully + テンプレートは正常に保存されました + + + Template uploaded successfully + テンプレートは正常にアップロードされました + Test connection 接続のテスト @@ -3926,10 +4102,22 @@ However, it is allowed to proceed the schema migration and Azure Database Migrat User account ユーザー アカウント + + User account + ユーザー アカウント + User name ユーザー名 + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + クエリ データ ストアの使用 (このオプションは Microsoft SQL Server 2016 以降で使用できます) + + + Using extended event session + 拡張イベント セッションの使用 + Validating and migrating logins are in progress ログインの検証と移行が進行中です @@ -4090,6 +4278,10 @@ This may take some time. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. データベースのバックアップを BLOB コンテナーにアップロードする際、異なるデータベースのバックアップ ファイルは必ず異なるフォルダーに保存してください。コンテナーのルートと深さ 1 レベルまでのフォルダーのみがサポートされています。 + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + 'スクリプトの実行' をクリックすると、以下の PowerShell スクリプトによって、セルフホステッド統合ランタイム ソフトウェアが自動的にダウンロードされ、インストールされ、Azure Database Migration Service に登録されます。IR の接続状態を確認するには、前の画面に戻って更新します。 + Where do you want to save collected data? 収集したデータをどこに保存しますか? @@ -4138,6 +4330,14 @@ This may take some time. Your Azure SQL target resource port number : 0 - 65535 Azure SQL ターゲット リソースのポート番号: 0 - 65535 + + Your Blob Container name + BLOB コンテナー名 + + + Your Storage Account name + ストレージ アカウント名 + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). データベースバックアップの場所の詳細、ネットワーク ファイル共有またはAzure Blob Storageコンテナー (Azure SQL データベース ターゲットには必要ありません)。 diff --git a/resources/xlf/ko/Microsoft.mssql.ko.xlf b/resources/xlf/ko/Microsoft.mssql.ko.xlf index 4aa6af11dc25..e335e09e5b9a 100644 --- a/resources/xlf/ko/Microsoft.mssql.ko.xlf +++ b/resources/xlf/ko/Microsoft.mssql.ko.xlf @@ -845,7 +845,7 @@ Note: A self-signed certificate offers only limited protection and is not a reco Files 파일 - + Files 파일 @@ -1205,6 +1205,10 @@ Note: A self-signed certificate offers only limited protection and is not a reco Optimize Ad Hoc Workloads 임시 워크로드 최적화 + + Options + 옵션 + Original File Name 원래 파일 이름 diff --git a/resources/xlf/ko/Microsoft.notebook.ko.xlf b/resources/xlf/ko/Microsoft.notebook.ko.xlf index 5b9a21dde087..752e5d062530 100644 --- a/resources/xlf/ko/Microsoft.notebook.ko.xlf +++ b/resources/xlf/ko/Microsoft.notebook.ko.xlf @@ -384,14 +384,6 @@ Browse 찾아보기 - - Installation Type - 설치 유형 - - - New Python installation - 새 Python 설치 - No supported Python versions found. 지원되는 Python 버전을 찾을 수 없습니다. @@ -401,12 +393,8 @@ Notebook 커널에서는 Python 런타임을 구성하고 종속성을 설치해야 합니다. - Python Install Location - Python 설치 위치 - - - Python runtime configured! - Python 런타임이 구성되었습니다. + Python Location + Python 위치 Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. ‘{0}’ 커널을 사용하려면 Python 런타임을 구성하고 종속성을 설치해야 합니다. - - Use existing Python installation - 기존 Python 설치 사용 + + {0} (Current Python Instance) + {0} (현재 Python 인스턴스) {0} (Custom) {0}(사용자 지정) - - {0} (Default) - {0}(기본값) - {0} (Python {1}) {0}(Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - 업데이트를 하기 위해 활성 Python Notebook 세션이 종료됩니다. 지금 계속하시겠습니까? - Another Python installation is currently in progress. Waiting for it to complete. 현재 다른 Python 설치를 진행 중입니다. 완료될 때까지 기다립니다. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Python이 실행되는 동안 기존 Python 설치를 덮어쓸 수 없습니다. 계속하기 전에 활성 Notebook을 닫으세요. - - - Don't Ask Again - 다시 묻지 않음 - - - Downloading local python for platform: {0} to {1} - {0} 플랫폼용 로컬 python을 {1}(으)로 다운로드하는 중 - - - Downloading python package - Python 패키지 다운로드 중 - Encountered an error when getting Python user path: {0} Python 사용자 경로를 가져올 때 오류가 발생했습니다. {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} 설치된 패키지 목록을 검색하는 동안 오류가 발생했습니다. {0} - - Error while creating python installation directory - Python 설치 디렉터리를 만드는 동안 오류가 발생했습니다. - - - Error while downloading python setup - Python 설정을 다운로드하는 동안 오류가 발생했습니다. - - - Error while unpacking python bundle - Python 번들 압축을 푸는 동안 오류가 발생했습니다. - Installing Notebook dependencies Notebook 종속성 설치 중 @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information Notebook 종속성을 설치하는 중입니다. 자세한 내용은 작업 보기를 참조하세요. - - No - 아니요 - Notebook dependencies installation is complete Notebook 종속성 설치를 완료했습니다. @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress Notebook 종속성 설치가 진행 중입니다. - - Python download is complete - Python 다운로드가 완료되었습니다. - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - 이제 python {0}에서 Azure Data Studio를 사용할 수 있습니다. 현재 Python 버전(3.6.6)은 2021년 12월에 지원되지 않습니다. 지금 Python {0}을(를) 업데이트하시겠습니까? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Python {0}이(가) 설치되고 Python 3.6.6을 대체합니다. 일부 패키지는 더 이상 새 버전과 호환되지 않거나 다시 설치해야 할 수 있습니다. 모든 pip 패키지를 다시 설치하는 데 도움이 되는 전자 필기장이 만들어집니다. 지금 업데이트를 계속하시겠습니까? - - - Unpacking python package - Python 패키지 압축을 푸는 중 - - - Yes - 네 - diff --git a/resources/xlf/ko/Microsoft.sql-migration.ko.xlf b/resources/xlf/ko/Microsoft.sql-migration.ko.xlf index 2ceedf9da8fe..ddcb649378f2 100644 --- a/resources/xlf/ko/Microsoft.sql-migration.ko.xlf +++ b/resources/xlf/ko/Microsoft.sql-migration.ko.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. 리소스 그룹은 Azure 솔루션에 대한 관련 리소스를 보유하는 컨테이너입니다. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + 단일 ARM 템플릿에는 최대 50개의 Azure SQL 데이터베이스 배포 제한이 있습니다. 처음 50개의 데이터베이스의 템플릿이 아래에 표시됩니다. 모든 템플릿을 보려면 템플릿 JSON 파일을 로컬 저장소 또는 Azure Blob 저장소에 저장하세요. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). 온-프레미스 또는 Azure Virtual Machine의 SQL Server 또는 클라우드(프라이빗, 퍼블릭)에서 실행되는 모든 가상 머신에서 실행되는 원본 SQL Server 데이터베이스입니다. @@ -138,6 +142,10 @@ All fields are required. 모든 필드가 필수 항목입니다. + + All nodes should be on the same version to be configured + 구성하려면 모든 노드가 동일한 버전에 있어야 합니다. + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. 원본 테이블이 모두 비어 있습니다. 데이터 마이그레이션을 위해 선택할 수 있는 테이블이 없습니다. 그러나 대상에 테이블이 없는 경우 스키마 마이그레이션을 사용할 수 있습니다. @@ -279,8 +287,8 @@ 오름차순 - Assess extended event sessions - 확장 이벤트 세션 평가 + Assess Ad-hoc or dynamic SQL + 임시 또는 동적 SQL 평가 Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node 향상된 성능과 고가용성을 위해 추가 노드를 등록할 수 있습니다. 아래에서 등록 지침을 확인하세요. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure Database Migration Service '{0}'이(가) 다음 노드에서 실행 중인 자체 호스팅 통합 런타임에 연결되어 있습니다. + Azure Database Migration Service "{0}" details:` Azure Database Migration Service "{0}" 세부 정보:' @@ -398,6 +410,10 @@ See below for registration instructions. 아래에서 등록 지침을 확인하세요. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure Database Migration Service는 Azure Data Factory의 자체 호스팅 통합 런타임을 활용하여 온-프레미스 네트워크 파일 공유에서 Azure로 백업을 업로드합니다. 이전 페이지의 선택 영역에 따라 자체 호스팅 통합 런타임을 설정해야 합니다. + 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). Azure Database Migration Service는 Azure Data Factory의 자체 호스팅 통합 런타임을 활용하여 원본과 대상 간의 연결을 처리하고 온-프레미스 네트워크 파일 공유에서 Azure로 백업을 업로드합니다(해당하는 경우). @@ -530,6 +546,10 @@ See below for registration instructions. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Azure SQL 대상의 Azure 지역입니다. 마이그레이션에 적합한 대상을 포함하는 지역만 표시합니다. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + 스토리지 계정의 Azure 지역입니다. 스토리지 계정이 포함된 지역만 표시됩니다. + Azure storage Azure Storage @@ -574,6 +594,10 @@ See below for registration instructions. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. 평가 결과에 따라 온라인 상태의 모든 {0} 데이터베이스를 Azure SQL로 마이그레이션할 수 있습니다. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + 다음은 권장 대상 SKU에 대한 ARM 스크립트입니다. 스크립트를 템플릿으로 저장할 수 있습니다. + Below is the target storage configuration required to meet your storage performance needs. 다음은 스토리지 성능 요구 사항을 충족하는 데 필요한 대상 스토리지 구성입니다. @@ -786,6 +810,10 @@ See below for registration instructions. Close 닫기 + + Close + 닫기 + Collect performance data now 지금 성능 데이터 수집 @@ -854,6 +882,18 @@ See below for registration instructions. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. 구성을 저장했습니다. 백그라운드에서 성능 데이터 수집을 계속 실행합니다. 원하는 경우 수집을 중지할 수 있습니다. + + Configure Integration Runtime + 통합 런타임 구성 + + + Configure manually + 수동으로 구성 + + + Configure using PowerShell script + PowerShell 스크립트를 사용하여 구성 + Connect 연결 @@ -1198,6 +1238,10 @@ See below for registration instructions. Details copied 세부 정보 복사됨 + + Details for {0} are mandatory and missing. + {0}에 대한 세부 정보는 필수이며 누락되었습니다. + Detected files 검색된 파일 @@ -1354,6 +1398,10 @@ See below for registration instructions. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. 원본 SQL Server 인스턴스에 대한 자격 증명을 입력합니다. 이러한 자격 증명은 데이터베이스를 Azure SQL로 마이그레이션하는 동안 사용됩니다. + + Enter the details below to select the Azure Storage account and save the script as template + 아래 세부 정보를 입력하여 Azure Storage 계정을 선택하고 스크립트를 템플릿으로 저장하세요. + Enter the information below to add a new Azure Database Migration Service. 새 Azure Database Migration Service를 추가하려면 아래 정보를 입력하세요. @@ -1434,6 +1482,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Establishing user mappings failed 사용자 매핑을 설정하지 못 함 + + Execute script + 스크립트 실행 + + + Execution started and monitor the PowerShell window opened. + 실행이 시작되었으며 열려 있는 PowerShell 창을 모니터링합니다. + Explore documentation 설명서 살펴보기 @@ -1490,6 +1546,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Failed to provision a Database Migration Service. Wait a few minutes and then try again. 데이터베이스 마이그레이션 서비스를 프로비전하지 못했습니다. 몇 분 기다렸다가 다시 시도하세요. + + Failed to save ARM Template + ARM 템플릿을 저장하지 못했습니다. + + + Failed to upload ARM Template + ARM 템플릿을 업로드하지 못했습니다. + Feedback 피드백 @@ -1575,8 +1639,8 @@ Currently, migrating server roles, establishing server mappings and setting perm SQL Server 2014 이하를 실행하는 대상 서버의 경우 데이터베이스를 백업할 때 네트워크 공유 옵션을 사용하여 업로드하는 대신 Azure Storage Blob 컨테이너에 저장해야 합니다. 또한 블록 Blob은 SQL Server 2016 이상을 실행하는 대상에만 지원되므로 백업 파일을 페이지 Blob으로 저장해야 합니다. 자세한 정보: {0} - 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} - 선택한 데이터베이스에 대해 확장 이벤트 세션 파일을 선택적으로 제공하여 임시 또는 동적 SQL 쿼리 또는 응용 프로그램 데이터 계층을 통해 시작된 모든 DML 문을 평가합니다. {0} + 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. + 선택한 데이터베이스에 대해 확장 이벤트 세션 파일을 선택적으로 제공하여 임시 또는 동적 SQL 쿼리 또는 응용 프로그램 데이터 계층을 통해 시작된 모든 DML 문을 평가합니다. Full backup file(s) @@ -1590,6 +1654,10 @@ Currently, migrating server roles, establishing server mappings and setting perm General purpose 범용 + + Generate Template + 템플릿 생성 + Generating script 스크립트 생성 @@ -1654,10 +1722,26 @@ Currently, migrating server roles, establishing server mappings and setting perm I have already migrated my certificates and private keys to the target. 이미 인증서와 프라이빗 키를 대상으로 마이그레이션했습니다. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + 내 로컬 컴퓨터가 아닌 다른 Windows 컴퓨터에서 자체 호스팅 통합 런타임을 설정하려고 합니다. + IO latency requirement IO 대기 시간 요구 사항 + + IP address + IP 주소 + + + IR configuration type + IR 구성 유형 + + + IR version + IR 버전 + If results were expected, verify the connection to the SQL Server instance. 결과가 예상되는 경우 SQL Server 인스턴스에 대한 연결을 확인하세요. @@ -1694,6 +1778,10 @@ Currently, migrating server roles, establishing server mappings and setting perm Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Data Migration Assistant를 사용하여 이미 수집한 경우 기존 폴더에서 이 데이터 파일을 가져옵니다. + + Important + 중요 + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. Azure Database Migration Service에서 오프라인 또는 온라인 상태일 때 데이터베이스를 마이그레이션할 수 있습니다. 오프라인 마이그레이션에서는 마이그레이션이 시작될 때 애플리케이션 가동 중지 시간이 시작됩니다. 가동 중지 시간을 마이그레이션 후 새 환경으로 컷오버하는 데 걸리는 시간으로 제한하려면 온라인 마이그레이션을 사용하세요. @@ -1926,6 +2014,14 @@ Click "Run validation" to check that requirements are met. Managed instance restore state 관리되는 인스턴스 복원 상태 + + Manual IR configuration collapsed + 수동 IR 구성을 축소함 + + + Manual IR configuration expanded + 수동 IR 구성을 확장함 + Map selected source databases to target databases for migration 선택한 원본 데이터베이스를 마이그레이션할 대상 데이터베이스에 매핑 @@ -2250,6 +2346,10 @@ Click "Run validation" to check that requirements are met. Next 다음 + + Next-gen General Purpose + 차세대 범용 + No 아니요 @@ -2318,6 +2418,10 @@ Click "Run validation" to check that requirements are met. No managed instances found. 관리되는 인스턴스를 찾을 수 없음. + + No node found + 노드를 찾을 수 없음 + No pending backups. Click refresh to check current status. 보류 중인 백업이 없습니다. 새로 고침을 클릭하여 현재 상태를 확인합니다. @@ -2354,6 +2458,10 @@ Click "Run validation" to check that requirements are met. No virtual machines found. 가상 머신이 없습니다. + + Node name + 노드 이름 + None 없음 @@ -2390,6 +2498,10 @@ Click "Run validation" to check that requirements are met. Not started 시작되지 않음 + + Note: Refer Self-hosted IR recommendations + 참고: 자체 호스팅 IR 권장 사항 참조 + Number of stripes 스트라이프 수 @@ -2426,6 +2538,10 @@ Click "Run validation" to check that requirements are met. Offline migration 오프라인 마이그레이션 + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + PowerShell에서 실행되면 아래 표시된 고유 스크립트가 자체 호스팅 통합 런타임을 다운로드하여 설치하고 Azure Database Migration Service로 등록합니다. 대상 컴퓨터에 PowerShell이 설치되어 있어야 합니다. + Online 온라인 @@ -2522,6 +2638,18 @@ Click "Run validation" to check that requirements are met. Port 포트 + + PowerShell script saved + PowerShell 스크립트를 저장함 + + + Powershell script collapsed + Powershell 스크립트를 축소함 + + + Powershell script expanded + Powershell 스크립트를 확장함 + Prefetch objects 개체 프리페치 @@ -2542,6 +2670,10 @@ Click "Run validation" to check that requirements are met. Preparing 준비 중 + + Prerequisite: Need PowerShell with execute as admin privileges. + 필수 구성 요소: 관리자 권한으로 실행할 수 있는 PowerShell이 필요합니다. + Previous (Disabled) 이전(사용 안 함) @@ -2698,6 +2830,10 @@ Click "Run validation" to check that requirements are met. Resource group 리소스 그룹 + + Resource group + 리소스 그룹 + Resource group created 리소스 그룹을 만들었습니다. @@ -2902,6 +3038,14 @@ Click "Run validation" to check that requirements are met. SQL tempdb SQL tempdb + + Save + 저장 + + + Save Template + 템플릿 저장 + Save and close 저장하고 닫기 @@ -2914,6 +3058,14 @@ Click "Run validation" to check that requirements are met. Save recommendation report 권장 사항 보고서 저장 + + Save script + 스크립트 저장 + + + Save to Azure blob container + Azure Blob 컨테이너에 저장 + Saved session 저장된 세션 @@ -3010,6 +3162,10 @@ Click "Run validation" to check that requirements are met. Select 선택 + + Select Azure Storage Account + Azure Storage 계정 선택 + Select Database Migration Service Database Migration Service 선택 @@ -3030,6 +3186,10 @@ Click "Run validation" to check that requirements are met. Select a Database Migration Service to monitor migrations. 마이그레이션을 모니터링할 Database Migration Service를 선택하세요. + + Select a Storage Account + 스토리지 계정 선택 + Select a blob container value first. 먼저 Blob 컨테이너 값을 선택합니다. @@ -3418,7 +3578,11 @@ Click "Run validation" to check that requirements are met. Storage 스토리지 - + + Storage Account + 스토리지 계정 + + Storage account 스토리지 계정 @@ -3446,6 +3610,10 @@ Click "Run validation" to check that requirements are met. Subscription name for your Azure SQL target Azure SQL 대상의 구독 이름 + + Subscription name for your Storage Account + 스토리지 계정의 구독 이름 + Succeeded 성공 @@ -3630,6 +3798,14 @@ Click "Run validation" to check that requirements are met. Target version 대상 버전 + + Template saved successfully + 템플릿을 저장했습니다. + + + Template uploaded successfully + 템플릿을 업로드함 + Test connection 연결 테스트 @@ -3926,10 +4102,22 @@ However, it is allowed to proceed the schema migration and Azure Database Migrat User account 사용자 계정 + + User account + 사용자 계정 + User name 사용자 이름 + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + 쿼리 데이터 저장소 사용(이 옵션은 Microsoft SQL Server 2016 이상에서 사용할 수 있음) + + + Using extended event session + 확장 이벤트 세션 사용 + Validating and migrating logins are in progress 로그인을 확인하고 마이그레이션하는 중입니다. @@ -4090,6 +4278,10 @@ This may take some time. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. 데이터베이스 백업을 Blob 컨테이너에 업로드할 때 서로 다른 데이터베이스의 백업 파일이 별도의 폴더에 저장되어 있는지 확인하세요. 최대 한 수준 깊이의 컨테이너와 폴더 루트만 지원됩니다. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + '스크립트 실행'을 클릭하면 아래 PowerShell 스크립트가 자동으로 자체 호스팅 통합 런타임 소프트웨어를 다운로드하고 설치한 후 Azure Database Migration Service로 등록합니다. IR의 연결 상태를 확인하려면 이전 화면으로 돌아가서 새로 고치세요. + Where do you want to save collected data? 수집된 데이터는 어디에 저장하시겠습니까? @@ -4138,6 +4330,14 @@ This may take some time. Your Azure SQL target resource port number : 0 - 65535 Azure SQL 대상 리소스 포트 번호: 0 - 65535 + + Your Blob Container name + Blob 컨테이너 이름 + + + Your Storage Account name + 스토리지 계정 이름 + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). 네트워크 파일 공유 또는 Azure Blob Storage 컨테이너(Azure SQL Database 대상에는 필요하지 않음)인 데이터베이스 백업 위치 세부 정보. diff --git a/resources/xlf/pt-br/Microsoft.mssql.pt-BR.xlf b/resources/xlf/pt-br/Microsoft.mssql.pt-BR.xlf index 74f936f38d6c..d7e1481f4efc 100644 --- a/resources/xlf/pt-br/Microsoft.mssql.pt-BR.xlf +++ b/resources/xlf/pt-br/Microsoft.mssql.pt-BR.xlf @@ -845,7 +845,7 @@ Observação: um certificado autoassinado oferece apenas proteção limitada e n Files Arquivos - + Files Arquivos @@ -1205,6 +1205,10 @@ Observação: um certificado autoassinado oferece apenas proteção limitada e n Optimize Ad Hoc Workloads Otimizar cargas de trabalho Ad Hoc + + Options + Opções + Original File Name Nome do Arquivo Original diff --git a/resources/xlf/pt-br/Microsoft.notebook.pt-BR.xlf b/resources/xlf/pt-br/Microsoft.notebook.pt-BR.xlf index 819f7d393a68..4c7382a4c33f 100644 --- a/resources/xlf/pt-br/Microsoft.notebook.pt-BR.xlf +++ b/resources/xlf/pt-br/Microsoft.notebook.pt-BR.xlf @@ -384,14 +384,6 @@ Browse Procurar - - Installation Type - Tipo de Instalação - - - New Python installation - Nova instalação do Python - No supported Python versions found. Não foram encontradas versões do Python com suporte. @@ -401,12 +393,8 @@ Os kernels do Notebook exigem que o runtime do Python seja configurado e as dependências sejam instaladas. - Python Install Location - Localização da Instalação do Python - - - Python runtime configured! - Runtime do Python configurado. + Python Location + Local do Python Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. O kernel '{0}' exige que um runtime do Python seja configurado e as dependências sejam instaladas. - - Use existing Python installation - Usar a instalação existente do Python + + {0} (Current Python Instance) + {0} (Instância Atual do Python) {0} (Custom) {0} (Personalizado) - - {0} (Default) - {0} (Padrão) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - As sessões ativas do bloco de anotações do Python serão encerradas para serem atualizadas. Deseja continuar agora? - Another Python installation is currently in progress. Waiting for it to complete. Outra instalação do Python está em andamento no momento. Esperando a conclusão. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Não é possível substituir uma instalação do Python existente enquanto o Python está em execução. Feche todos os notebooks ativos antes de prosseguir. - - - Don't Ask Again - Não perguntar novamente - - - Downloading local python for platform: {0} to {1} - Baixando o Python local para a plataforma: {0} a {1} - - - Downloading python package - Baixando o pacote Python - Encountered an error when getting Python user path: {0} Foi encontrado um erro ao obter o caminho do usuário do Python: {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} Foi encontrado um erro ao tentar recuperar a lista de pacotes instalados: {0} - - Error while creating python installation directory - Erro ao criar o diretório de instalação do Python - - - Error while downloading python setup - Erro ao baixar a configuração do Python - - - Error while unpacking python bundle - Erro ao descompactar o pacote Python - Installing Notebook dependencies Instalando as dependências do Notebook @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information Instalando as dependências do Notebook. Confira a exibição Tarefas para obter mais informações - - No - Não - Notebook dependencies installation is complete A instalação das dependências do Notebook está concluída @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress A instalação de dependências do Notebook está em andamento - - Python download is complete - O download do Python está concluído - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - O Python {0} agora está disponível no Azure Data Studio. A versão atual do Python (3.6.6) estará sem suporte em dezembro de 2021. Deseja atualizar para o Python {0} agora? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - O Python {0} será instalado e substituirá o Python 3.6.6. Alguns pacotes podem não ser mais compatíveis com a nova versão ou talvez precisem ser reinstalados. Um bloco de anotações será criado para ajudá-lo a reinstalar todos os pacotes pip. Deseja continuar com a atualização agora? - - - Unpacking python package - Descompactando o pacote Python - - - Yes - Sim - diff --git a/resources/xlf/pt-br/Microsoft.sql-migration.pt-BR.xlf b/resources/xlf/pt-br/Microsoft.sql-migration.pt-BR.xlf index 62768f95bd75..b901e46ee1b3 100644 --- a/resources/xlf/pt-br/Microsoft.sql-migration.pt-BR.xlf +++ b/resources/xlf/pt-br/Microsoft.sql-migration.pt-BR.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. Um grupo de recursos é um contêiner que armazena recursos relacionados para uma solução do Azure. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + Um único modelo do ARM tem uma limitação de implantação de no máximo 50 bancos de dados SQL do Azure. O modelo para os primeiros 50 bancos de dados é exibido abaixo. Para exibir todos os modelos, salve o arquivo JSON de modelo em um armazenamento local ou Armazenamento de Blobs do Azure. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). Uma fonte de bancos de dados SQL Server em execução no local ou no SQL Server na Máquina Virtual do Azure ou em qualquer máquina virtual em execução na nuvem (privada, pública). @@ -138,6 +142,10 @@ All fields are required. Todos os campos são obrigatórios. + + All nodes should be on the same version to be configured + Todos os nós devem estar na mesma versão para serem configurados + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. Todas as tabelas de destino estão vazias. Nenhuma tabela está disponível para seleção para migração de dados. Mas eles estão disponíveis para migração de esquema se não existirem no destino. @@ -279,8 +287,8 @@ Crescente - Assess extended event sessions - Avaliar sessões de eventos estendidos + Assess Ad-hoc or dynamic SQL + Avaliar SQL ad hoc ou dinâmico Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node Para melhorar o desempenho e a alta disponibilidade, você pode registrar nós adicionais. Confira abaixo as instruções de registro. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + O Serviço de Migração de Banco de Dados do Azure ''{0}'' está conectado ao runtime de integração auto-hospedada em execução nos nós a seguir + Azure Database Migration Service "{0}" details:` Detalhes do Serviço de Migração de Banco de Dados do Azure "{0}": ` @@ -398,6 +410,10 @@ See below for registration instructions. Confira abaixo as instruções de registro. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + O Serviço de Migração de Banco de Dados do Azure aproveita o Runtime de Integração auto-hospedada do Azure Data Factory para carregar backups do compartilhamento de arquivo de rede local para o Azure. Com base nas seleções na página anterior, você precisará configurar uma página de Runtime de integração auto-hospedada. + 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). O Serviço de Migração de Banco de Dados do Azure aproveita o runtime de integração auto-hospedada do Azure Data Factory para lidar com a conectividade entre a origem e o destino e carregar backups de um compartilhamento de arquivos de rede local para o Azure (se aplicável). @@ -530,6 +546,10 @@ Confira abaixo as instruções de registro. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Região do Azure para seu destino SQL do Azure. Somente as regiões que contêm um destino qualificado para migração serão mostradas. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + Região do Azure para sua Conta de Armazenamento. Somente as regiões que contêm uma conta de armazenamento serão mostradas. + Azure storage Armazenamento do Azure @@ -574,6 +594,10 @@ Confira abaixo as instruções de registro. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. Com base nos resultados da avaliação, todos os {0} de seus bancos de dados em um estado online podem ser migrados para o SQL do Azure. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + Abaixo está o script ARM para o SKU de destino recomendado. Você pode salvar o script como modelo. + Below is the target storage configuration required to meet your storage performance needs. Abaixo está a configuração de armazenamento de destino necessária para atender suas necessidades de desempenho de armazenamento. @@ -786,6 +810,10 @@ Confira abaixo as instruções de registro. Close Fechar + + Close + Fechar + Collect performance data now Coletar dados de desempenho agora @@ -854,6 +882,18 @@ Confira abaixo as instruções de registro. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Configuração salva. A coleta de dados de desempenho permanecerá em execução em segundo plano. Você pode parar a coleta quando quiser. + + Configure Integration Runtime + Configurar o Integration Runtime + + + Configure manually + Configurar manualmente + + + Configure using PowerShell script + Configurar usando o script do PowerShell + Connect Conectar @@ -1198,6 +1238,10 @@ Confira abaixo as instruções de registro. Details copied Detalhes copiados + + Details for {0} are mandatory and missing. + Os detalhes para {0} são obrigatórios e estão ausentes. + Detected files Arquivos detectados @@ -1354,6 +1398,10 @@ Confira abaixo as instruções de registro. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Insira as credenciais para a Instância do SQL Server de origem. Essas credenciais serão usadas ao migrar bancos de dados para o SQL do Azure. + + Enter the details below to select the Azure Storage account and save the script as template + Insira os detalhes abaixo para selecionar a conta de Armazenamento do Azure e salvar o script como modelo + Enter the information below to add a new Azure Database Migration Service. Insira as informações abaixo para adicionar um novo Serviço de Migração de Banco de Dados do Azure. @@ -1434,6 +1482,14 @@ Atualmente, migrando as funções de servidor, estabelecendo mapeamentos de serv Establishing user mappings failed Ocorreu um erro ao estabelecer os mapeamentos de usuários + + Execute script + Executar script + + + Execution started and monitor the PowerShell window opened. + A execução foi iniciada e o monitor da janela do PowerShell foi aberto. + Explore documentation Explorar a documentação @@ -1490,6 +1546,14 @@ Atualmente, migrando as funções de servidor, estabelecendo mapeamentos de serv Failed to provision a Database Migration Service. Wait a few minutes and then try again. Falha ao provisional um Serviço de Migração de Banco de Dados. Aguarde alguns minutos e tente novamente. + + Failed to save ARM Template + Falha ao salvar o Modelo ARM + + + Failed to upload ARM Template + Falha ao carregar o Modelo ARM + Feedback Comentários @@ -1575,8 +1639,8 @@ Atualmente, migrando as funções de servidor, estabelecendo mapeamentos de serv Para servidores de destino que executam o SQL Server 2014 ou inferior, você deve armazenar seus backups de banco de dados em um contêiner do Azure Storage Blob em vez de carregá-los usando a opção de compartilhamento de rede. Além disso, você deve armazenar os arquivos de backup como blobs de páginas, pois os blobs de blocos têm suporte apenas para destinos que executam o SQL Server 2016 ou posterior. Saiba mais: {0} - 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} - Para os bancos de dados selecionados, opcionalmente, forneça arquivos de sessão de evento estendido para avaliar consultas ad hoc ou SQL dinâmicas ou quaisquer instruções DML iniciadas pela camada de dados do aplicativo. {0} + 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. + Para os bancos de dados selecionados, opcionalmente, forneça arquivos de sessão de evento prorrogado para avaliar consultas de SQL ad hoc ou dinâmicas ou quaisquer instruções DML iniciadas por meio da camada de dados do aplicativo. Full backup file(s) @@ -1590,6 +1654,10 @@ Atualmente, migrando as funções de servidor, estabelecendo mapeamentos de serv General purpose Uso geral + + Generate Template + Gerar Modelo + Generating script Gerando script @@ -1654,10 +1722,26 @@ Atualmente, migrando as funções de servidor, estabelecendo mapeamentos de serv I have already migrated my certificates and private keys to the target. Já migrei meus certificados e chaves privadas para o destino. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + Quero configurar o runtime de integração auto-hospedada em outro computador Windows que não seja meu computador local. + IO latency requirement Requisitos de latência de E/S + + IP address + Endereço IP + + + IR configuration type + Tipo de configuração de IR + + + IR version + Versão do IR + If results were expected, verify the connection to the SQL Server instance. Para atingir os resultados esperados, verifique a conexão com a Instância do SQL Server. @@ -1694,6 +1778,10 @@ Atualmente, migrando as funções de servidor, estabelecendo mapeamentos de serv Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Importe esse arquivo de dados de uma pasta existente, se você já o tiver coletado usando o Assistente de Migração de Dados. + + Important + Importante + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. No Serviço de Migração de Banco de Dados do Azure, você pode migrar seus bancos de dados offline ou enquanto estiverem online. Em uma migração offline, o tempo de inatividade do aplicativo começa quando a migração é iniciada. Para limitar o tempo de inatividade ao tempo que leva para mudar para o novo ambiente após a migração, use uma migração online. @@ -1926,6 +2014,14 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Managed instance restore state Estado de restauração da instância gerenciada + + Manual IR configuration collapsed + Configuração de IR manual recolhida + + + Manual IR configuration expanded + Configuração de IR manual expandida + Map selected source databases to target databases for migration Mapeie os bancos de dados de origem selecionados para os bancos de dados de destino @@ -2250,6 +2346,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Next Próximo + + Next-gen General Purpose + Dados de próxima geração Uso Geral + No Não @@ -2318,6 +2418,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos No managed instances found. Nenhuma instância gerenciada encontrada. + + No node found + Nenhum nó encontrado + No pending backups. Click refresh to check current status. Nenhum backup pendente. Clique em Atualizar para verificar o status atual. @@ -2354,6 +2458,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos No virtual machines found. Nenhuma máquina virtual encontrada. + + Node name + Nome do nó + None Nenhum @@ -2390,6 +2498,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Not started Não iniciado + + Note: Refer Self-hosted IR recommendations + Observação: consulte as recomendações de IR auto-hospedado + Number of stripes Número de faixas @@ -2426,6 +2538,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Offline migration Migração offline + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + Depois de executado no PowerShell, o script exclusivo mostrado abaixo será baixado, instalará o runtime de integração auto-hospedada e o registrará com o Serviço de Migração de Banco de Dados do Azure. Você precisará ter o PowerShell instalado no computador de destino. + Online On-line @@ -2522,6 +2638,18 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Port Porta + + PowerShell script saved + Script do PowerShell salvo + + + Powershell script collapsed + Script do PowerShell recolhido + + + Powershell script expanded + Script do PowerShell expandido + Prefetch objects Pré-buscar objetos @@ -2542,6 +2670,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Preparing Preparando + + Prerequisite: Need PowerShell with execute as admin privileges. + Pré-requisito: é necessário ter o PowerShell com privilégios de execução como administrador. + Previous (Disabled) Anterior (Desabilitado) @@ -2698,6 +2830,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Resource group Grupo de recursos + + Resource group + Grupo de recursos + Resource group created Grupo de recursos criado @@ -2902,6 +3038,14 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos SQL tempdb Tempdb do SQL + + Save + Salvar + + + Save Template + Salvar Modelo + Save and close Salvar e fechar @@ -2914,6 +3058,14 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Save recommendation report Salvar relatório de recomendação + + Save script + Salvar script + + + Save to Azure blob container + Salvar no contêiner de blobs do Azure + Saved session Sessão salva @@ -3010,6 +3162,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Select Selecionar + + Select Azure Storage Account + Selecione a Conta de Armazenamento do Azure + Select Database Migration Service Selecionar o Serviço de Migração de Banco de Dados @@ -3030,6 +3186,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Select a Database Migration Service to monitor migrations. Selecione um Serviço de Migração de Banco de Dados para monitorar as migrações. + + Select a Storage Account + Selecionar uma Conta de Armazenamento + Select a blob container value first. Selecione um valor de contêiner blob primeiro. @@ -3418,7 +3578,11 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Storage Armazenamento - + + Storage Account + Conta de Armazenamento + + Storage account Conta de armazenamento @@ -3446,6 +3610,10 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Subscription name for your Azure SQL target Nome da assinatura para o destino do SQL do Azure + + Subscription name for your Storage Account + Nome da assinatura da sua Conta de Armazenamento + Succeeded Com êxito @@ -3630,6 +3798,14 @@ Clique em "Executar validação" para verificar se os requisitos foram atendidos Target version Versão alvo + + Template saved successfully + Modelo salvo com êxito + + + Template uploaded successfully + Modelo carregado com êxito + Test connection Testar conexão @@ -3926,10 +4102,22 @@ No entanto, é permitido prosseguir a migração do esquema e o Serviço de Migr User account Conta de usuário + + User account + Conta de usuário + User name Nome do usuário + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + Usando Repositório de Dados de Consultas (essa opção está disponível para o Microsoft SQL Server 2016 e posterior) + + + Using extended event session + Usando a sessão de evento estendido + Validating and migrating logins are in progress A validação e a migração de logons estão em andamento @@ -4090,6 +4278,10 @@ Isto pode levar algum tempo. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. Ao carregar backups de banco de dados no contêiner de blobs, verifique se os arquivos de backup de bancos de dados diferentes estão armazenados em pastas separadas. Há suporte apenas para a raiz do contêiner e das pastas no máximo um nível de profundidade. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + Quando você clicar em "executar script", o script do PowerShell abaixo fará o download automático do software de runtime de integração auto-hospedado, o instalará e o registrará no Serviço de Migração de Banco de Dados do Azure. Para verificar o status da conexão do IR, volte à tela anterior e atualize-a. + Where do you want to save collected data? Onde você deseja salvar os dados coletados? @@ -4138,6 +4330,14 @@ Isto pode levar algum tempo. Your Azure SQL target resource port number : 0 - 65535 Seu número de porta de recurso de destino do SQL do Azure : 0 - 65535 + + Your Blob Container name + Nome do SEU Contêiner de Blob + + + Your Storage Account name + Nome da Sua Conta de Armazenamento + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). Os detalhes do local de backup do seu banco de dados, seja um compartilhamento de arquivos de rede ou um contêiner de Armazenamento de Blobs do Azure (não necessário para destinos de Banco de Dados SQL do Azure). diff --git a/resources/xlf/ru/Microsoft.mssql.ru.xlf b/resources/xlf/ru/Microsoft.mssql.ru.xlf index c33b5e2b9d7b..2ac21a654073 100644 --- a/resources/xlf/ru/Microsoft.mssql.ru.xlf +++ b/resources/xlf/ru/Microsoft.mssql.ru.xlf @@ -845,7 +845,7 @@ Note: A self-signed certificate offers only limited protection and is not a reco Files Файлы - + Files Файлы @@ -1205,6 +1205,10 @@ Note: A self-signed certificate offers only limited protection and is not a reco Optimize Ad Hoc Workloads Оптимизировать нерегламентированные рабочие нагрузки + + Options + Параметры + Original File Name Исходное имя файла diff --git a/resources/xlf/ru/Microsoft.notebook.ru.xlf b/resources/xlf/ru/Microsoft.notebook.ru.xlf index d09216361b41..4e6d12b2d164 100644 --- a/resources/xlf/ru/Microsoft.notebook.ru.xlf +++ b/resources/xlf/ru/Microsoft.notebook.ru.xlf @@ -384,14 +384,6 @@ Browse Обзор - - Installation Type - Тип установки - - - New Python installation - Новая установка Python - No supported Python versions found. Поддерживаемые версии Python не найдены. @@ -401,12 +393,8 @@ Для ядер записных книжек требуется настроить среду выполнения Python и установить зависимости. - Python Install Location - Расположение установки Python - - - Python runtime configured! - Среда выполнения Python настроена. + Python Location + Расположение Python Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. Для ядра "{0}" требуется настроить среду выполнения Python и установить зависимости. - - Use existing Python installation - Использовать существующую установку Python + + {0} (Current Python Instance) + {0} (текущий экземпляр Python) {0} (Custom) {0} (пользовательский) - - {0} (Default) - {0} (по умолчанию) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - Сеансы активных записных книжек Python будут завершены, чтобы обновить их. Хотите продолжить? - Another Python installation is currently in progress. Waiting for it to complete. Сейчас выполняется другая установка Python. Дождитесь ее завершения. - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - Не удается перезаписать существующую установку Python во время работы Python. Прежде чем продолжить, закройте все активные записные книжки. - - - Don't Ask Again - Больше не спрашивать - - - Downloading local python for platform: {0} to {1} - Скачивание локального Python для платформы: {0} в {1} - - - Downloading python package - Идет скачивание пакета Python - Encountered an error when getting Python user path: {0} Обнаружена ошибка при получении пути пользователя Python: {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} Произошла ошибка при попытке получить список установленных пакетов: {0} - - Error while creating python installation directory - Ошибка при создании каталога установки Python - - - Error while downloading python setup - Ошибка при скачивании программы установки Python - - - Error while unpacking python bundle - Ошибка при распаковке пакета Python - Installing Notebook dependencies Идет установка зависимостей Notebook @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information Идет установка зависимостей Notebook, дополнительные сведения см. в представлении задач - - No - Нет - Notebook dependencies installation is complete Установка зависимостей Notebook завершена @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress Выполняется установка зависимостей Notebook - - Python download is complete - Скачивание Python завершено - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - {0} Python доступна в Azure Data Studio. Текущая версия Python (3.6.6) не поддерживается в декабре 2021. Вы хотите обновить {0} Python сейчас? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - Будет установлен {0} Python, который заменит 3.6.6 Python. Некоторые пакеты могут быть несовместимы с новой версией или требуют переустановки. Будет создана Записная книжка, которая поможет вам переустановить все пакеты PIP. Вы хотите продолжить обновление сейчас? - - - Unpacking python package - Распаковка пакета Python - - - Yes - Да - diff --git a/resources/xlf/ru/Microsoft.sql-migration.ru.xlf b/resources/xlf/ru/Microsoft.sql-migration.ru.xlf index b9604a10b2fc..e5eff366fe1c 100644 --- a/resources/xlf/ru/Microsoft.sql-migration.ru.xlf +++ b/resources/xlf/ru/Microsoft.sql-migration.ru.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. Группа ресурсов — это контейнер, содержащий связанные ресурсы для решения Azure. + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + Для одного шаблона ARM применяется ограничение развертывания, составляющее максимум 50 баз данных SQL Azure. Шаблон для первых 50 баз данных отображается ниже. Чтобы просмотреть все шаблоны, сохраните файл JSON шаблона в локальном хранилище или хранилище BLOB-объектов Azure. + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). Исходные базы данных SQL Server, работающие в локальной среде, на SQL Server в виртуальной машине Azure или в любой виртуальной машине, работающей в облаке (частном, общедоступном). @@ -138,6 +142,10 @@ All fields are required. Нужно заполнить все поля. + + All nodes should be on the same version to be configured + Для настройки все узлы должны иметь одинаковую версию + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. Все исходные таблицы пусты. Нет доступных таблиц для выбора с целью переноса данных. Но они доступны для миграции схемы, если они не существуют в целевом объекте. @@ -279,8 +287,8 @@ По возрастанию - Assess extended event sessions - Оценка расширенных сеансов событий + Assess Ad-hoc or dynamic SQL + Оценка специального или динамического SQL Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node Для улучшения производительности и обеспечения высокой доступности можно зарегистрировать дополнительные узлы. Инструкции по регистрации см. ниже. + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure Database Migration Service "{0}" подключена к локальной среде выполнения интеграции, запущенной на следующем узле или узлах + Azure Database Migration Service "{0}" details:` Сведения Azure Database Migration Service "{0}":` @@ -398,6 +410,10 @@ See below for registration instructions. Инструкции по регистрации см. ниже. + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure Database Migration Service использует локальную среду выполнения интеграции Фабрики данных Azure для отправки резервных копий из общей папки локальной сети в Azure. В зависимости от выбранных на предыдущей странице элементов потребуется настроить локальную среду выполнения интеграции. + 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). Azure Database Migration Service использует локальную среду выполнения интеграции Фабрики данных Azure для управления подключением между источником и назначением и для загрузки резервных копий из локальной сетевой папки в Azure (если применимо). @@ -530,6 +546,10 @@ See below for registration instructions. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Регион Azure для целевого Azure SQL. Будут показаны только регионы, в которых есть целевые объекты, подходящие для миграции. + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + Регион Azure для учетной записи хранения. Будут показаны только регионы, содержащие учетную запись хранения. + Azure storage Служба хранилища Azure @@ -574,6 +594,10 @@ See below for registration instructions. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. Исходя из результатов оценки, все {0} из ваших баз данных в подключенном состоянии можно перенести в Azure SQL. + + Below is the ARM script for the recommended target SKU. You can save the script as template. + Ниже приведен сценарий ARM для рекомендуемого целевого SKU. Сценарий можно сохранить в качестве шаблона. + Below is the target storage configuration required to meet your storage performance needs. Ниже приведена целевая конфигурация хранилища, необходимая для выполнения ваших требований к производительности хранилища. @@ -786,6 +810,10 @@ See below for registration instructions. Close Закрыть + + Close + Закрыть + Collect performance data now Собрать данные производительности @@ -854,6 +882,18 @@ See below for registration instructions. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. Конфигурация сохранена. Сбор данных производительности будет выполняться в фоновом режиме. Вы можете остановить сбор, когда за хотите. + + Configure Integration Runtime + Настройка среды выполнения интеграции + + + Configure manually + Настроить вручную + + + Configure using PowerShell script + Настроить с помощью сценария PowerShell + Connect Подключиться @@ -1198,6 +1238,10 @@ See below for registration instructions. Details copied Сведения скопированы + + Details for {0} are mandatory and missing. + Сведения для {0} являются обязательными и отсутствуют. + Detected files Обнаруженные файлы @@ -1354,6 +1398,10 @@ See below for registration instructions. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. Введите учетные данные для источника экземпляра SQL Server. Эти учетные данные будут использоваться при миграции баз данных в Azure SQL. + + Enter the details below to select the Azure Storage account and save the script as template + Введите сведения ниже, чтобы выбрать учетную запись службы хранения Azure и сохранить сценарий в качестве шаблона + Enter the information below to add a new Azure Database Migration Service. Чтобы добавить новую службу Azure Database Migration Service, введите сведения ниже. @@ -1434,6 +1482,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Establishing user mappings failed Сбой установки сопоставлений пользователей + + Execute script + Выполнить сценарий + + + Execution started and monitor the PowerShell window opened. + Выполнение запущено, окно мониторинга PowerShell открыто. + Explore documentation Обзор документации @@ -1490,6 +1546,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Failed to provision a Database Migration Service. Wait a few minutes and then try again. Не удалось подготовить Database Migration Service. Подождите несколько минут и повторите попытку. + + Failed to save ARM Template + Не удалось сохранить шаблон ARM + + + Failed to upload ARM Template + Не удалось отправить шаблон ARM + Feedback Отзывы @@ -1575,8 +1639,8 @@ Currently, migrating server roles, establishing server mappings and setting perm Для целевых серверов с SQL Server 2014 или более поздней версии необходимо хранить резервные копии баз данных в контейнере Azure Storage Blob, а не отправлять их с помощью сетевой папки. Кроме того, файлы резервных копий должны храниться как страничные BLOB-объекты, так как блочные BLOB-объекты поддерживаются только для целевых объектов с SQL Server 2016 или более поздней версии. Дополнительные сведения: {0} - 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} - Для выбранных баз данных при необходимости предоставьте файлы расширенных сеансов событий для оценки специализированных или динамических SQL-запросов или любых инструкций DML, инициированных с помощью уровня данных приложения. {0} + 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. + Для выбранных баз данных при необходимости предоставьте файлы расширенных сеансов событий для оценки специализированных или динамических SQL-запросов или любых инструкций DML, инициированных с помощью уровня данных приложения. Full backup file(s) @@ -1590,6 +1654,10 @@ Currently, migrating server roles, establishing server mappings and setting perm General purpose Общее назначение + + Generate Template + Генерировать шаблон + Generating script Создается скрипт @@ -1654,10 +1722,26 @@ Currently, migrating server roles, establishing server mappings and setting perm I have already migrated my certificates and private keys to the target. Мои сертификаты и закрытые ключи уже перенесены в целевой объект. + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + Я хочу настроить локальную среду выполнения интеграции на другом компьютере с Windows, который не является моим локальным компьютером. + IO latency requirement Требование задержки ввода-вывода + + IP address + IP-адрес + + + IR configuration type + Тип конфигурации IR + + + IR version + Версия IR + If results were expected, verify the connection to the SQL Server instance. Если ожидались результаты, проверьте подключение к экземпляру SQL Server. @@ -1694,6 +1778,10 @@ Currently, migrating server roles, establishing server mappings and setting perm Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. Импортируйте этот файл данных из существующей папки, если вы уже собрали его с помощью Помощника по миграции данных. + + Important + Важно + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. В Azure Database Migration Service вы можете перенести базы данных в автономном режиме или при их подключении к сети. При автономной миграции время простоя приложения начинается при запуске миграции. Чтобы ограничить время простоя временем, необходимым для перехода в новую среду после миграции, используйте миграцию по сети. @@ -1926,6 +2014,14 @@ Click "Run validation" to check that requirements are met. Managed instance restore state Состояние восстановления управляемого экземпляра + + Manual IR configuration collapsed + Конфигурация IR вручную свернута + + + Manual IR configuration expanded + Конфигурация IR вручную развернута + Map selected source databases to target databases for migration Сопоставление выбранных баз данных-источников с целевыми базами данных для миграции @@ -2250,6 +2346,10 @@ Click "Run validation" to check that requirements are met. Next Далее + + Next-gen General Purpose + Следующее поколение общего назначения + No Нет @@ -2318,6 +2418,10 @@ Click "Run validation" to check that requirements are met. No managed instances found. Управляемые экземпляры не найдены. + + No node found + Узел не найден + No pending backups. Click refresh to check current status. Ожидающие резервные копии отсутствуют. Нажмите кнопку Обновить, чтобы проверить текущее состояние. @@ -2354,6 +2458,10 @@ Click "Run validation" to check that requirements are met. No virtual machines found. Виртуальные машины не найдены + + Node name + Имя узла + None Нет @@ -2390,6 +2498,10 @@ Click "Run validation" to check that requirements are met. Not started Не запущено + + Note: Refer Self-hosted IR recommendations + Примечание. См. рекомендации для локальной среды выполнения интеграции + Number of stripes Число полос @@ -2426,6 +2538,10 @@ Click "Run validation" to check that requirements are met. Offline migration Автономная миграция + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + После выполнения в PowerShell уникальный сценарий, показанный ниже, загрузит и установит локальную среду выполнения интеграции и зарегистрирует ее в Azure Database Migration Service. На целевом компьютере необходимо установить PowerShell. + Online В Интернете @@ -2522,6 +2638,18 @@ Click "Run validation" to check that requirements are met. Port Порт + + PowerShell script saved + Сценарий PowerShell сохранен + + + Powershell script collapsed + Сценарий PowerShell свернут + + + Powershell script expanded + Сценарий PowerShell развернут + Prefetch objects Упреждающая выборка объектов @@ -2542,6 +2670,10 @@ Click "Run validation" to check that requirements are met. Preparing Подготовка + + Prerequisite: Need PowerShell with execute as admin privileges. + Необходимое условие: требуется PowerShell с правами администратора на выполнение. + Previous (Disabled) Назад (отключено) @@ -2698,6 +2830,10 @@ Click "Run validation" to check that requirements are met. Resource group Группа ресурсов + + Resource group + Группа ресурсов + Resource group created Создана группа ресурсов @@ -2902,6 +3038,14 @@ Click "Run validation" to check that requirements are met. SQL tempdb SQL tempdb + + Save + Сохранить + + + Save Template + Сохранить шаблон + Save and close Сохранить и закрыть @@ -2914,6 +3058,14 @@ Click "Run validation" to check that requirements are met. Save recommendation report Сохранить отчет о рекомендациях + + Save script + Сохранить сценарий + + + Save to Azure blob container + Сохранить в контейнере BLOB-объектов Azure + Saved session Сохраненный сеанс @@ -3010,6 +3162,10 @@ Click "Run validation" to check that requirements are met. Select Выбрать + + Select Azure Storage Account + Выберите учетную запись хранения Azure + Select Database Migration Service Выбрать службу миграции баз данных @@ -3030,6 +3186,10 @@ Click "Run validation" to check that requirements are met. Select a Database Migration Service to monitor migrations. Выберите службу Database Migration Service для отслеживания миграций. + + Select a Storage Account + Выбрать учетную запись хранения + Select a blob container value first. Сначала выберите значение контейнера больших двоичных объектов. @@ -3418,7 +3578,11 @@ Click "Run validation" to check that requirements are met. Storage Хранилище - + + Storage Account + Учетная запись хранения + + Storage account Учетная запись хранения @@ -3446,6 +3610,10 @@ Click "Run validation" to check that requirements are met. Subscription name for your Azure SQL target Имя подписки для целевого объекта Azure SQL + + Subscription name for your Storage Account + Имя подписки для учетной записи хранения + Succeeded Выполнено @@ -3630,6 +3798,14 @@ Click "Run validation" to check that requirements are met. Target version Целевая версия + + Template saved successfully + Шаблон сохранен + + + Template uploaded successfully + Шаблон успешно отправлен + Test connection Проверить подключение @@ -3926,10 +4102,22 @@ However, it is allowed to proceed the schema migration and Azure Database Migrat User account Учетная запись пользователя + + User account + Учетная запись пользователя + User name Имя пользователя + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + Использование хранилища данных запросов (этот параметр доступен для Microsoft SQL Server 2016 и более поздних версий) + + + Using extended event session + Использование расширенного сеанса событий + Validating and migrating logins are in progress Выполняется проверка и миграция учетных данных @@ -4090,6 +4278,10 @@ This may take some time. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. При отправке резервных копий баз данных в контейнер BLOB-объектов убедитесь, что файлы резервных копий из разных баз данных хранятся в отдельных папках. Поддерживается только корень контейнера и папок глубиной не более одного уровня. + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + При нажатии кнопки "Выполнить сценарий" расположенный ниже сценарий PowerShell автоматически скачает программное обеспечение локальной среды выполнения интеграции, а также установит и зарегистрирует его в Azure Database Migration Service. Чтобы проверить состояние подключения IR, вернитесь на предыдущий экран и обновите страницу. + Where do you want to save collected data? Где вы хотите сохранить собранные данные? @@ -4138,6 +4330,14 @@ This may take some time. Your Azure SQL target resource port number : 0 - 65535 Номер вашего целевого ресурса порта Azure SQL: 0–65535 + + Your Blob Container name + Имя контейнера BLOB-объектов + + + Your Storage Account name + Имя учетной записи хранения + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). Сведения о расположении резервной копии базы данных: сетевой общей папке или контейнере Хранилища BLOB-объектов Azure (не требуется для целевых Баз данных SQL Azure). diff --git a/resources/xlf/zh-hans/Microsoft.mssql.zh-Hans.xlf b/resources/xlf/zh-hans/Microsoft.mssql.zh-Hans.xlf index e03f56abd585..ae50f065410e 100644 --- a/resources/xlf/zh-hans/Microsoft.mssql.zh-Hans.xlf +++ b/resources/xlf/zh-hans/Microsoft.mssql.zh-Hans.xlf @@ -845,7 +845,7 @@ Note: A self-signed certificate offers only limited protection and is not a reco Files 文件 - + Files 文件 @@ -1205,6 +1205,10 @@ Note: A self-signed certificate offers only limited protection and is not a reco Optimize Ad Hoc Workloads 优化临时工作负载 + + Options + 选项 + Original File Name 原始文件名 diff --git a/resources/xlf/zh-hans/Microsoft.notebook.zh-Hans.xlf b/resources/xlf/zh-hans/Microsoft.notebook.zh-Hans.xlf index 748607849c39..3b7ada98ff23 100644 --- a/resources/xlf/zh-hans/Microsoft.notebook.zh-Hans.xlf +++ b/resources/xlf/zh-hans/Microsoft.notebook.zh-Hans.xlf @@ -384,14 +384,6 @@ Browse 浏览 - - Installation Type - 安装类型 - - - New Python installation - 新 Python 安装 - No supported Python versions found. 找不到支持的 Python 版本。 @@ -401,12 +393,8 @@ 笔记本内核要求配置 Python 运行时并安装依赖项。 - Python Install Location - Python 安装位置 - - - Python runtime configured! - Python 运行时已配置! + Python Location + Python 位置 Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. "{0}" 内核要求配置 Python 运行时并安装依赖项。 - - Use existing Python installation - 使用现有 Python 安装 + + {0} (Current Python Instance) + {0} (当前 Python 实例) {0} (Custom) {0} (自定义) - - {0} (Default) - {0} (默认) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - 将关闭活动 Python 笔记本会话以进行更新。是否要立即继续? - Another Python installation is currently in progress. Waiting for it to complete. 另一个 Python 安装正在进行中。请等待它完成。 - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - 在 Python 运行时无法覆盖现有 Python 安装。请关闭所有活动笔记本，再继续操作。 - - - Don't Ask Again - 不再询问 - - - Downloading local python for platform: {0} to {1} - 正在将平台 {0} 的本地 python 下载到 {1} - - - Downloading python package - 正在下载 python 包 - Encountered an error when getting Python user path: {0} 获取 Python 用户路径时遇到错误: {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} 尝试检索已安装的包列表时遇到错误: {0} - - Error while creating python installation directory - 创建 python 安装目录时出错 - - - Error while downloading python setup - 下载 python 安装程序时出错 - - - Error while unpacking python bundle - 解压 Python 捆绑包时出错 - Installing Notebook dependencies 正在安装笔记本依赖项 @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information 正在安装笔记本依赖项；有关详细信息，请参阅“任务”视图 - - No - 否 - Notebook dependencies installation is complete 笔记本依赖项安装完毕 @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress 正在安装笔记本依赖项 - - Python download is complete - Python 下载完毕 - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Python {0} 现已在 Azure Data Studio 中提供。当前 Python 版本 (3.6.6) 将于 2021 年 12 月不再受支持。是否要立即更新到 Python {0}? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - 将安装 Python {0} ，并将替换 Python 3.6.6。某些包可能不再与新版本兼容，或者可能需要重新安装。将创建一个笔记本来帮助你重新安装所有 pip 包。是否要立即继续更新? - - - Unpacking python package - 正在解压 python 包 - - - Yes - 是 - diff --git a/resources/xlf/zh-hans/Microsoft.sql-migration.zh-Hans.xlf b/resources/xlf/zh-hans/Microsoft.sql-migration.zh-Hans.xlf index 7ee0d0ddd5f4..02b9df0a4206 100644 --- a/resources/xlf/zh-hans/Microsoft.sql-migration.zh-Hans.xlf +++ b/resources/xlf/zh-hans/Microsoft.sql-migration.zh-Hans.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. 资源组是保管 Azure 解决方案的相关资源的容器。 + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + 单个 ARM 模板的部署限制为最多 50 个 Azure SQL 数据库。前 50 个数据库的模板如下所示。要查看所有模板，请将模板 JSON 文件保存在本地存储或 Azure Blob 存储中。 + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). 在本地或 Azure 虚拟机中的 SQL Server 或云(私有、公共)中运行的任何虚拟机上的源 SQL Server 数据库。 @@ -138,6 +142,10 @@ All fields are required. 所有字段均为必填。 + + All nodes should be on the same version to be configured + 所有节点都应在同一版本上进行配置 + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. 所有源表均为空。没有表可供选择以用于数据迁移。但是，如果它们在目标上不存在，则可用于架构迁移。 @@ -279,8 +287,8 @@ 升序 - Assess extended event sessions - 评估扩展事件会话 + Assess Ad-hoc or dynamic SQL + 评估临时或动态 SQL Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node 为了提高性能和高可用性，你可以注册其他节点。请参阅下面的注册说明。 + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure 数据库迁移服务“{0}”已连接到在以下节点上运行的自承载集成运行时 + Azure Database Migration Service "{0}" details:` Azure 数据库迁移服务“{0}”详细信息: @@ -398,6 +410,10 @@ See below for registration instructions. 请参阅下面的注册说明。 + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure 数据库迁移服务利用 Azure 数据工厂的自承载集成运行时将备份从本地网络文件共享上传到 Azure。根据上一页上的选择，需要设置自承载集成运行时。 + 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). Azure 数据库迁移服务利用 Azure 数据工厂的自承载集成运行时处理源和目标之间的连接，并将备份从本地网络文件共享上传到 Azure (适用时)。 @@ -530,6 +546,10 @@ See below for registration instructions. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. Azure SQL 目标的 Azure 区域。将仅显示包含符合迁移条件的目标的区域。 + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + 存储帐户的 Azure 区域。将仅显示包含存储帐户的区域。 + Azure storage Azure 存储 @@ -574,6 +594,10 @@ See below for registration instructions. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. 根据评估结果，你的联机状态下的所有 {0} 个数据库都可以迁移到 Azure SQL。 + + Below is the ARM script for the recommended target SKU. You can save the script as template. + 下面是建议的目标 SKU 的 ARM 脚本。可以将脚本另存为模板。 + Below is the target storage configuration required to meet your storage performance needs. 下面是满足存储性能需求所需的目标存储配置。 @@ -786,6 +810,10 @@ See below for registration instructions. Close 关闭 + + Close + 关闭 + Collect performance data now 立即收集性能数据 @@ -854,6 +882,18 @@ See below for registration instructions. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. 已保存配置。性能数据收集将保持在后台运行。你可以在需要时停止收集。 + + Configure Integration Runtime + 配置集成运行时 + + + Configure manually + 手动配置 + + + Configure using PowerShell script + 使用 PowerShell 脚本进行配置 + Connect 连接 @@ -1198,6 +1238,10 @@ See below for registration instructions. Details copied 已复制详细信息 + + Details for {0} are mandatory and missing. + 必须提供 {0} 详细信息，但缺少此信息。 + Detected files 检测到的文件 @@ -1354,6 +1398,10 @@ See below for registration instructions. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. 输入源 SQL Server 实例的凭据。将数据库迁移到 Azure SQL 时将使用这些凭据。 + + Enter the details below to select the Azure Storage account and save the script as template + 输入下面的详细信息以选择 Azure 存储帐户并将脚本另存为模板 + Enter the information below to add a new Azure Database Migration Service. 在下面输入信息以添加新的 Azure 数据库迁移服务。 @@ -1434,6 +1482,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Establishing user mappings failed 建立用户映射失败 + + Execute script + 执行脚本 + + + Execution started and monitor the PowerShell window opened. + 已开始执行并监视打开的 PowerShell 窗口。 + Explore documentation 浏览文档 @@ -1490,6 +1546,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Failed to provision a Database Migration Service. Wait a few minutes and then try again. 未能预配数据库迁移服务。请等待几分钟，然后重试。 + + Failed to save ARM Template + 未能保存 ARM 模板 + + + Failed to upload ARM Template + 未能上传 ARM 模板 + Feedback 反馈 @@ -1575,8 +1639,8 @@ Currently, migrating server roles, establishing server mappings and setting perm 对于运行 SQL Server 2014 或更低版本的目标服务器，必须将数据库备份存储在 Azure 存储 Blob 容器中，而不是使用网络共享选项上传它们。此外，必须将备份文件存储为页 Blob，因为运行 SQL Server 2016 或更高版本的目标仅支持块 blob。要了解详细信息，请访问: {0} - 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} - 对于所选数据库，可以选择提供扩展事件会话文件以评估临时或动态 SQL 查询或通过应用程序数据层启动的任何 DML 语句。{0} + 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. + 对于所选数据库，可选择提供扩展事件会话文件以评估临时或动态 SQL 查询或通过应用程序数据层启动的任何 DML 语句。 Full backup file(s) @@ -1590,6 +1654,10 @@ Currently, migrating server roles, establishing server mappings and setting perm General purpose 常规用途 + + Generate Template + 生成模板 + Generating script 正在生成脚本 @@ -1654,10 +1722,26 @@ Currently, migrating server roles, establishing server mappings and setting perm I have already migrated my certificates and private keys to the target. 我已将证书和私钥迁移到目标。 + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + 我想在另一台 Windows 计算机上设置自承载集成运行时，该计算机不是我的本地计算机。 + IO latency requirement IO 延迟要求 + + IP address + IP 地址 + + + IR configuration type + IR 配置类型 + + + IR version + IR 版本 + If results were expected, verify the connection to the SQL Server instance. 如果结果在预期内，请验证与 SQL Server 实例的连接。 @@ -1694,6 +1778,10 @@ Currently, migrating server roles, establishing server mappings and setting perm Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. 如果已使用“数据迁移助手”收集此数据文件，请从现有文件夹导入此数据文件。 + + Important + 重要说明 + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. 在 Azure 数据库迁移服务中，可以在脱机或联机时迁移数据库。脱机迁移期间，应用程序停机时间在迁移开始时开始。如果要在迁移后将故障时间限制为要直接转换到新环境的时间，请使用联机迁移。 @@ -1926,6 +2014,14 @@ Click "Run validation" to check that requirements are met. Managed instance restore state 托管实例还原状态 + + Manual IR configuration collapsed + 手动 IR 配置已折叠 + + + Manual IR configuration expanded + 手动 IR 配置已展开 + Map selected source databases to target databases for migration 将所选源数据库映射到目标数据库以进行迁移 @@ -2250,6 +2346,10 @@ Click "Run validation" to check that requirements are met. Next 下一步 + + Next-gen General Purpose + 下一代常规用途 + No 否 @@ -2318,6 +2418,10 @@ Click "Run validation" to check that requirements are met. No managed instances found. 找不到托管实例。 + + No node found + 未找到节点 + No pending backups. Click refresh to check current status. 没有挂起的备份。请单击“刷新”以检查当前状态。 @@ -2354,6 +2458,10 @@ Click "Run validation" to check that requirements are met. No virtual machines found. 找不到任何虚拟机。 + + Node name + 节点名称 + None 无 @@ -2390,6 +2498,10 @@ Click "Run validation" to check that requirements are met. Not started 未启动 + + Note: Refer Self-hosted IR recommendations + 注意: 请参阅自承载 IR 建议 + Number of stripes 条带数 @@ -2426,6 +2538,10 @@ Click "Run validation" to check that requirements are met. Offline migration 脱机迁移 + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + 在 PowerShell 中执行后，下面显示的唯一脚本将下载并安装自承载集成运行时，并向 Azure 数据库迁移服务注册它。需要在目标计算机上安装 PowerShell。 + Online 联机 @@ -2522,6 +2638,18 @@ Click "Run validation" to check that requirements are met. Port 端口 + + PowerShell script saved + PowerShell 脚本已保存 + + + Powershell script collapsed + PowerShell 脚本已折叠 + + + Powershell script expanded + PowerShell 脚本已展开 + Prefetch objects 预提取对象 @@ -2542,6 +2670,10 @@ Click "Run validation" to check that requirements are met. Preparing 正在准备 + + Prerequisite: Need PowerShell with execute as admin privileges. + 先决条件: 需要 PowerShell 具有以管理员身份执行的权限。 + Previous (Disabled) 上一个(已禁用) @@ -2698,6 +2830,10 @@ Click "Run validation" to check that requirements are met. Resource group 资源组 + + Resource group + 资源组 + Resource group created 已创建资源组 @@ -2902,6 +3038,14 @@ Click "Run validation" to check that requirements are met. SQL tempdb SQL tempdb + + Save + 保存 + + + Save Template + 保存模板 + Save and close 保存并关闭 @@ -2914,6 +3058,14 @@ Click "Run validation" to check that requirements are met. Save recommendation report 保存建议报告 + + Save script + 保存脚本 + + + Save to Azure blob container + 保存到 Azure Blob 容器 + Saved session 已保存的会话 @@ -3010,6 +3162,10 @@ Click "Run validation" to check that requirements are met. Select 选择 + + Select Azure Storage Account + 选择 Azure 存储帐户 + Select Database Migration Service 选择数据库迁移服务 @@ -3030,6 +3186,10 @@ Click "Run validation" to check that requirements are met. Select a Database Migration Service to monitor migrations. 选择一项数据库迁移服务来监视迁移。 + + Select a Storage Account + 选择存储帐户 + Select a blob container value first. 首先选择一个 Blob 容器值。 @@ -3418,7 +3578,11 @@ Click "Run validation" to check that requirements are met. Storage 存储 - + + Storage Account + 存储帐户 + + Storage account 存储帐户 @@ -3446,6 +3610,10 @@ Click "Run validation" to check that requirements are met. Subscription name for your Azure SQL target Azure SQL 目标的订阅名称 + + Subscription name for your Storage Account + 存储帐户的订阅名称 + Succeeded 成功 @@ -3630,6 +3798,14 @@ Click "Run validation" to check that requirements are met. Target version 目标版本 + + Template saved successfully + 已成功保存模板 + + + Template uploaded successfully + 已成功上传模板 + Test connection 测试连接 @@ -3926,10 +4102,22 @@ However, it is allowed to proceed the schema migration and Azure Database Migrat User account 用户帐户 + + User account + 用户帐户 + User name 用户名 + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + 使用查询数据存储(此选项适用于 Microsoft SQL Server 2016 及更高版本) + + + Using extended event session + 使用扩展事件会话 + Validating and migrating logins are in progress 正在验证和迁移登录 @@ -4090,6 +4278,10 @@ This may take some time. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. 将数据库备份上传到 blob 容器时，请确保不同数据库中的备份文件存储在单独的文件夹中。仅支持容器的根目录和最高级别的深层文件夹。 + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + 单击“执行脚本”后，下面的 PowerShell 脚本将自动下载自承载集成运行时软件、安装并将其注册到 Azure 数据库迁移服务。若要检查 IR 的连接状态，请返回到上一个屏幕并刷新。 + Where do you want to save collected data? 要将收集的数据保存到何处? @@ -4138,6 +4330,14 @@ This may take some time. Your Azure SQL target resource port number : 0 - 65535 你的 Azure SQL 目标资源端口号: 0 - 65535 + + Your Blob Container name + Blob 容器名称 + + + Your Storage Account name + 存储帐户名称 + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). 你的数据库备份位置详细信息，可以是网络文件共享或 Azure Blob 存储容器(非 Azure SQL 数据库目标所需)。 diff --git a/resources/xlf/zh-hant/Microsoft.cms.zh-Hant.xlf b/resources/xlf/zh-hant/Microsoft.cms.zh-Hant.xlf index 510dd30af390..331be00376fa 100644 --- a/resources/xlf/zh-hant/Microsoft.cms.zh-Hant.xlf +++ b/resources/xlf/zh-hant/Microsoft.cms.zh-Hant.xlf @@ -480,7 +480,7 @@ Strict (supported for SQL Server 2022 and Azure SQL) - Strict (supported for SQL Server 2022 and Azure SQL) + 嚴格 (支援 SQL Server 2022 和 Azure SQL) Support for managing SQL Server Central Management Servers diff --git a/resources/xlf/zh-hant/Microsoft.mssql.zh-Hant.xlf b/resources/xlf/zh-hant/Microsoft.mssql.zh-Hant.xlf index 49f6346011c4..db910775bbf7 100644 --- a/resources/xlf/zh-hant/Microsoft.mssql.zh-Hant.xlf +++ b/resources/xlf/zh-hant/Microsoft.mssql.zh-Hant.xlf @@ -845,7 +845,7 @@ Note: A self-signed certificate offers only limited protection and is not a reco Files 檔案 - + Files 檔案 @@ -1205,6 +1205,10 @@ Note: A self-signed certificate offers only limited protection and is not a reco Optimize Ad Hoc Workloads 針對臨機工作負載進行最佳化 + + Options + 選項 + Original File Name 原始檔案名稱 @@ -2668,7 +2672,7 @@ Note: A self-signed certificate offers only limited protection and is not a reco Strict (supported for SQL Server 2022 and Azure SQL) - Strict (supported for SQL Server 2022 and Azure SQL) + 嚴格 (支援 SQL Server 2022 和 Azure SQL) The SQL Server language record name diff --git a/resources/xlf/zh-hant/Microsoft.notebook.zh-Hant.xlf b/resources/xlf/zh-hant/Microsoft.notebook.zh-Hant.xlf index fd0b32534f48..75c20765e5da 100644 --- a/resources/xlf/zh-hant/Microsoft.notebook.zh-Hant.xlf +++ b/resources/xlf/zh-hant/Microsoft.notebook.zh-Hant.xlf @@ -384,14 +384,6 @@ Browse 瀏覽 - - Installation Type - 安裝類型 - - - New Python installation - 新增 Python 安裝 - No supported Python versions found. 找不到支援的 Python 版本。 @@ -401,12 +393,8 @@ Notebook 核心需要設定 Python 執行階段並安裝相依性。 - Python Install Location - Python 安裝位置 - - - Python runtime configured! - 已設定 Python 執行階段! + Python Location + Python 位置 Select @@ -416,18 +404,14 @@ The '{0}' kernel requires a Python runtime to be configured and dependencies to be installed. '{0}' 核心需要設定 Python 執行階段並安裝相依性。 - - Use existing Python installation - 使用現有的 Python 安裝 + + {0} (Current Python Instance) + {0} (目前的 Python 執行個體) {0} (Custom) {0} (自訂) - - {0} (Default) - {0} (預設) - {0} (Python {1}) {0} (Python {1}) @@ -676,30 +660,10 @@ - - Active Python notebook sessions will be shutdown in order to update. Would you like to proceed now? - 為了進行更新，將關閉使用中的 Python 筆記本工作階段。您要立即繼續嗎? - Another Python installation is currently in progress. Waiting for it to complete. 目前在進行另一個 Python 安裝。請等它完成。 - - Cannot overwrite an existing Python installation while python is running. Please close any active notebooks before proceeding. - 當 Python 正在執行時，無法覆寫現有的 Python 安裝。請先關閉所有使用中的筆記本再繼續。 - - - Don't Ask Again - 不要再詢問 - - - Downloading local python for platform: {0} to {1} - 正在將平台的本機 python: {0} 下載至 {1} - - - Downloading python package - 正在下載 python 套件 - Encountered an error when getting Python user path: {0} 取得 Python 使用者路徑時發生錯誤: {0} @@ -708,18 +672,6 @@ Encountered an error when trying to retrieve list of installed packages: {0} 嘗試擷取已安裝套件的清單時發生錯誤: {0} - - Error while creating python installation directory - 建立 python 安裝目錄時發生錯誤 - - - Error while downloading python setup - 下載 python 設定時發生錯誤 - - - Error while unpacking python bundle - 將 python 套件組合解壓縮時發生錯誤 - Installing Notebook dependencies 正在安裝 Notebook 相依性 @@ -732,10 +684,6 @@ Installing Notebook dependencies, see Tasks view for more information 正在安裝 Notebook 相依性，請參閱 [工作] 檢視以取得詳細資訊 - - No - 否 - Notebook dependencies installation is complete Notebook 相依性安裝完成 @@ -744,26 +692,6 @@ Notebook dependencies installation is in progress 正在安裝 Notebook 相依性 - - Python download is complete - Python 下載完成 - - - Python {0} is now available in Azure Data Studio. The current Python version (3.6.6) will be out of support in December 2021. Would you like to update to Python {0} now? - Azure Data Studio 現已提供 Python {0}。目前的 Python 版本 (3.6.6) 將在 2021 年 12 月時取消支援。您要立即更新為 Python {0} 嗎? - - - Python {0} will be installed and will replace Python 3.6.6. Some packages may no longer be compatible with the new version or may need to be reinstalled. A notebook will be created to help you reinstall all pip packages. Would you like to continue with the update now? - 將安裝 Python {0} 並取代 Python 3.6.6。某些套件可能不再與新版本相容，或可能需要重新安裝。將建立筆記本以協助您重新安裝所有 pip 套件。您要立即繼續更新嗎? - - - Unpacking python package - 正在解壓縮 python 套件 - - - Yes - 是 - diff --git a/resources/xlf/zh-hant/Microsoft.sql-migration.zh-Hant.xlf b/resources/xlf/zh-hant/Microsoft.sql-migration.zh-Hant.xlf index b4b14dd11175..6ee93f5fdc39 100644 --- a/resources/xlf/zh-hant/Microsoft.sql-migration.zh-Hant.xlf +++ b/resources/xlf/zh-hant/Microsoft.sql-migration.zh-Hant.xlf @@ -78,6 +78,10 @@ A resource group is a container that holds related resources for an Azure solution. 資源群組是能夠存放 Azure 解決方案相關資源的容器。 + + A single ARM template has a deployment limitation of a maximum 50 Azure SQL Databases. The template for the first 50 databases is displayed below. To view all templates, save the template JSON file in a local storage or Azure Blob storage. + 單一 ARM 範本的部署限制上限為 50 Azure SQL 資料庫。前 50 個資料庫的範本顯示如下。若要檢視所有範本，請將範本 JSON 檔案儲存在本機儲存體或 Azure Blob 儲存體中。 + A source SQL Server database(s) running on on-premises, or on SQL Server on Azure Virtual Machine or any virtual machine running in the cloud (private, public). 在內部部署或 Azure 虛擬機器上的 SQL Server 上執行的來源 SQL Server 資料庫，或雲端中執行的任何虛擬機器 (私人、公用)。 @@ -138,6 +142,10 @@ All fields are required. 所有欄位都是必要欄位。 + + All nodes should be on the same version to be configured + 所有節點都應位於相同的版本，才能設定 + All of source tables are empty. No table is available to select for data migration. But they are available for schema migration if they do not exist on target. 所有來源資料表都是空白。沒有資料表可供選取以進行資料移轉。但若它們不存在於目標上，則它們可供結構描述移轉使用。 @@ -279,8 +287,8 @@ 遞增 - Assess extended event sessions - 評估擴充事件工作階段 + Assess Ad-hoc or dynamic SQL + 評估臨機操作或動態 SQL Assessed databases: {0} @@ -382,6 +390,10 @@ For improved performance and high availability, you can register additional node 為了提升效能和高可用性，您可以註冊其他節點。請參閱下方的註冊指示。 + + Azure Database Migration Service '{0}' is connected to self-hosted integration runtime running on the following node(s) + Azure 資料庫移轉服務 '{0}' 已連線到在下列節點上執行的自我裝載整合執行階段 + Azure Database Migration Service "{0}" details:` Azure 資料庫移轉服務 "{0}" 詳細資料: @@ -398,6 +410,10 @@ See below for registration instructions. 請參閱下方的註冊指示。 + + Azure Database Migration Service leverages Azure Data Factory's Self-hosted Integration Runtime to upload backups from on-premise network file share to Azure. Based on the selections on the previous page you will need to setup an Self-hosted Integration Runtime. + Azure 資料庫移轉服務利用 Azure Data Factory 的自我裝載整合執行階段，將備份從內部部署網路檔案共用上傳到 Azure。根據上一頁的選取項目，您必須設定自我裝載整合執行階段。 + 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). Azure 資料庫移轉服務利用 Azure Data Factory 的自我裝載整合執行階段，處理來源與目標之間的連線，並將內部部署網路檔案共用的備份上傳到 Azure (若適用)。 @@ -530,6 +546,10 @@ See below for registration instructions. Azure region for your Azure SQL target. Only regions that contain a target eligible for migration will be shown. 您的 Azure SQL 目標的 Azure 區域。只會顯示包含符合移轉目標的區域。 + + Azure region for your Storage Account. Only regions that contain a storage account will be shown. + 儲存體帳戶的 Azure 地區。只會顯示包含儲存體帳戶的區域。 + Azure storage Azure 儲存體 @@ -574,6 +594,10 @@ See below for registration instructions. Based on the assessment results, all {0} of your databases in an online state can be migrated to Azure SQL. 根據評定結果，您所有在線上狀態的 {0} 個資料庫都可以移轉到 Azure SQL。 + + Below is the ARM script for the recommended target SKU. You can save the script as template. + 以下是建議的目標 SKU 的 ARM 指令碼。您可以將指令碼儲存為範本。 + Below is the target storage configuration required to meet your storage performance needs. 以下是滿足儲存體效能需求所需的目標儲存體設定。 @@ -786,6 +810,10 @@ See below for registration instructions. Close 關閉 + + Close + 關閉 + Collect performance data now 立即收集效能資料 @@ -854,6 +882,18 @@ See below for registration instructions. Configuration saved. Performance data collection will remain running in the background. You can stop the collection when you want to. 已儲存設定。效能資料收集仍會在背景執行。您可以在想要時停止集合。 + + Configure Integration Runtime + 設定整合執行階段 + + + Configure manually + 手動設定 + + + Configure using PowerShell script + 使用 PowerShell 指令碼設定 + Connect 連線 @@ -1198,6 +1238,10 @@ See below for registration instructions. Details copied 已複製詳細資料 + + Details for {0} are mandatory and missing. + {0} 的詳細資料為必要但現缺少。 + Detected files 偵測到的檔案 @@ -1354,6 +1398,10 @@ See below for registration instructions. Enter the credentials for the source SQL Server instance. These credentials will be used while migrating databases to Azure SQL. 輸入來源 SQL Server 執行個體的認證。將資料庫移轉到 Azure SQL 時，將會使用此認證。 + + Enter the details below to select the Azure Storage account and save the script as template + 在下方輸入詳細資料以選取 Azure 儲存體帳戶，並將指令碼儲存為範本 + Enter the information below to add a new Azure Database Migration Service. 請在下方輸入資訊，以新增 Azure 資料庫移轉服務。 @@ -1434,6 +1482,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Establishing user mappings failed 建立使用者對應失敗 + + Execute script + 執行指令碼 + + + Execution started and monitor the PowerShell window opened. + 已開始執行並監視開啟的 PowerShell 視窗。 + Explore documentation 探索文件 @@ -1490,6 +1546,14 @@ Currently, migrating server roles, establishing server mappings and setting perm Failed to provision a Database Migration Service. Wait a few minutes and then try again. 無法佈建資料庫移轉服務。請稍待幾分鐘後再試一次。 + + Failed to save ARM Template + 無法儲存 ARM 範本 + + + Failed to upload ARM Template + 無法上傳 ARM 範本 + Feedback 意見反應 @@ -1575,8 +1639,8 @@ Currently, migrating server roles, establishing server mappings and setting perm 對於執行 SQL Server 2014 或更低版本的目標伺服器，您必須將資料庫備份儲存在 Azure 儲存體 Blob 容器中，而非使用網路共用選項將其上傳。此外，您必須將備份檔案儲存為分頁 Blob，因為只有執行 SQL Server 2016 或更新版本的目標才支援區塊 Blob。深入了解: {0} - 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} - 對於選取的資料庫，請選擇性地提供擴充事件工作階段檔案來評估臨機操作或動態 SQL 查詢，或透過應用程式資料圖層起始的任何 DML 陳述式。{0} + 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. + 對於選取的資料庫，請選擇性地提供擴充事件工作階段檔案來評估臨機操作或動態 SQL 查詢，或透過應用程式資料圖層起始的任何 DML 陳述式。 Full backup file(s) @@ -1590,6 +1654,10 @@ Currently, migrating server roles, establishing server mappings and setting perm General purpose 一般目的 + + Generate Template + 產生範本 + Generating script 產生指令碼 @@ -1654,10 +1722,26 @@ Currently, migrating server roles, establishing server mappings and setting perm I have already migrated my certificates and private keys to the target. 我已經將憑證和私密金鑰移轉到目標。 + + I want to setup self-hosted integration runtime on another Windows machine that is not my local machine. + 我想要在另一部不是我的本機電腦的 Windows 電腦上設定自我裝載整合執行階段。 + IO latency requirement IO 延遲需求 + + IP address + IP 位址 + + + IR configuration type + 整合執行階段設定類型 + + + IR version + 整合執行階段版本 + If results were expected, verify the connection to the SQL Server instance. 如果預期結果，請驗證 SQL Server 執行個體的連線。 @@ -1694,6 +1778,10 @@ Currently, migrating server roles, establishing server mappings and setting perm Import this data file from an existing folder, if you have already collected it using Data Migration Assistant. 從現有資料夾匯入此資料檔案 (如果您已使用 Data Migration Assistant 收集)。 + + Important + 重要 + In Azure Database Migration Service, you can migrate your databases offline or while they are online. In an offline migration, application downtime starts when the migration starts. To limit downtime to the time it takes you to cut over to the new environment after the migration, use an online migration. 在 Azure 資料移轉服務中，您可以離線或在連線時移轉您的資料庫。在離線移轉中，應用程式停機時間會在移轉開始時開始。若要將停機時間限制為移轉後移轉至新環境所需的時間，請使用線上移轉。 @@ -1926,6 +2014,14 @@ Click "Run validation" to check that requirements are met. Managed instance restore state 受控執行個體還原狀態 + + Manual IR configuration collapsed + 手動整合執行階段設定已摺疊 + + + Manual IR configuration expanded + 手動整合執行階段設定已展開 + Map selected source databases to target databases for migration 將選取的來源資料庫對應到目標資料庫以進行移轉 @@ -2250,6 +2346,10 @@ Click "Run validation" to check that requirements are met. Next 下一步 + + Next-gen General Purpose + 新一代一般用途 + No 否 @@ -2318,6 +2418,10 @@ Click "Run validation" to check that requirements are met. No managed instances found. 找不到任何受控執行個體。 + + No node found + 找不到節點 + No pending backups. Click refresh to check current status. 沒有擱置的備份。按一下 [重新整理] 以檢查目前的狀態。 @@ -2354,6 +2458,10 @@ Click "Run validation" to check that requirements are met. No virtual machines found. 找不到任何虛擬機器。 + + Node name + 節點名稱 + None 無 @@ -2390,6 +2498,10 @@ Click "Run validation" to check that requirements are met. Not started 未啟動 + + Note: Refer Self-hosted IR recommendations + 注意: 請參閱自我裝載整合執行階段建議 + Number of stripes 條紋數 @@ -2426,6 +2538,10 @@ Click "Run validation" to check that requirements are met. Offline migration 離線移轉 + + Once executed in powershell, the unique script shown below will download, and install the self-hosted integration runtime and register it with the Azure Database Migration Service. You will need to have PowerShell installed on the target machine. + 在 Powershell 中執行之後，下方顯示的唯一指令碼將會下載，並安裝自我裝載整合執行階段，然後向 Azure 資料移轉服務註冊。您必須在目標電腦上安裝 PowerShell。 + Online 上線 @@ -2522,6 +2638,18 @@ Click "Run validation" to check that requirements are met. Port 連接埠 + + PowerShell script saved + Powershell 指令碼已儲存 + + + Powershell script collapsed + Powershell 指令碼已摺疊 + + + Powershell script expanded + Powershell 指令碼已展開 + Prefetch objects 預先擷取物件 @@ -2542,6 +2670,10 @@ Click "Run validation" to check that requirements are met. Preparing 正在準備 + + Prerequisite: Need PowerShell with execute as admin privileges. + 必要條件: 需要具有執行身分系統管理員權限的 PowerShell。 + Previous (Disabled) 上一個 (已停用) @@ -2698,6 +2830,10 @@ Click "Run validation" to check that requirements are met. Resource group 資源群組 + + Resource group + 資源群組 + Resource group created 已建立資源群組 @@ -2902,6 +3038,14 @@ Click "Run validation" to check that requirements are met. SQL tempdb SQL tempdb + + Save + 儲存 + + + Save Template + 儲存範本 + Save and close 儲存後關閉 @@ -2914,6 +3058,14 @@ Click "Run validation" to check that requirements are met. Save recommendation report 儲存建議報告 + + Save script + 儲存指令碼 + + + Save to Azure blob container + 儲存至 Azure Blob 容器 + Saved session 已儲存的工作階段 @@ -3010,6 +3162,10 @@ Click "Run validation" to check that requirements are met. Select 選取 + + Select Azure Storage Account + 選取 Azure 儲存體帳戶 + Select Database Migration Service 選取資料庫移轉服務 @@ -3030,6 +3186,10 @@ Click "Run validation" to check that requirements are met. Select a Database Migration Service to monitor migrations. 選取要監視移轉的資料庫移轉服務。 + + Select a Storage Account + 選取儲存體帳戶 + Select a blob container value first. 請先選取 BLOb 容器值。 @@ -3418,7 +3578,11 @@ Click "Run validation" to check that requirements are met. Storage 儲存體 - + + Storage Account + 儲存體帳戶 + + Storage account 儲存體帳戶 @@ -3446,6 +3610,10 @@ Click "Run validation" to check that requirements are met. Subscription name for your Azure SQL target Azure SQL 目標的訂用帳戶名稱 + + Subscription name for your Storage Account + 您儲存體帳戶的訂用帳戶名稱 + Succeeded 已成功 @@ -3630,6 +3798,14 @@ Click "Run validation" to check that requirements are met. Target version 目標版本 + + Template saved successfully + 已成功儲存範本 + + + Template uploaded successfully + 已成功上傳範本 + Test connection 測試連接 @@ -3926,10 +4102,22 @@ However, it is allowed to proceed the schema migration and Azure Database Migrat User account 使用者帳戶 + + User account + 使用者帳戶 + User name 使用者名稱 + + Using Query Data Store (this option is available for Microsoft SQL Server 2016 and later) + 使用查詢資料存放區 (此選項適用於 Microsoft SQL Server 2016 及更新版本) + + + Using extended event session + 使用擴充事件工作階段 + Validating and migrating logins are in progress 正在驗證及移轉登入 @@ -4090,6 +4278,10 @@ This may take some time. When uploading database backups to your blob container, ensure that backup files from different databases are stored in separate folders. Only the root of the container and folders at most one level deep are supported. 將資料庫備份上傳到 Blob 容器時，請確定來自不同資料庫的備份檔案儲存在不同的資料夾中。只支援容器與資料夾最多一層深的根目錄。 + + When you click 'execute script', the PowerShell script below will automatically download self-hosted integration runtime software, install, and register it with your Azure Database Migration Service. To check the connection status of the IR, go back to the previous screen and refresh. + 當您按下 [執行指令碼] 時，下方的 PowerShell 指令碼會自動下載自我裝載整合執行階段軟體、安裝，並與您的 Azure 資料移轉服務註冊。若要檢查整合執行階段的連線狀態，請返回上一個畫面並重新整理。 + Where do you want to save collected data? 您要將收集的資料儲存在哪裡? @@ -4138,6 +4330,14 @@ This may take some time. Your Azure SQL target resource port number : 0 - 65535 您的 Azure SQL 目標資源連接埠號碼: 0 - 65535 + + Your Blob Container name + 您的 Blob 容器名稱 + + + Your Storage Account name + 您的儲存體帳戶名稱 + Your database backup location details, either a network file share or an Azure Blob Storage container (not required for Azure SQL Database targets). 您的資料庫備份位置詳細資料，網路檔案共用或 Azure Blob 儲存體容器 (Azure SQL Database 目標不需要)。