diff --git a/resources/xlf/en/arc.xlf b/resources/xlf/en/arc.xlf index a9ffb8bbe5..c7e6559e2f 100644 --- a/resources/xlf/en/arc.xlf +++ b/resources/xlf/en/arc.xlf @@ -67,14 +67,17 @@ without downtime and by + + Compute Configuration + Condition - Configuration + Node Configuration - Configuration (per node) + Configuration Configure retention policy @@ -101,10 +104,10 @@ Could not connect to SQL managed instance - Azure Arc Instance {0}. {1} - Connect to PostgreSQL Hyperscale - Azure Arc ({0}) + Connect to PostgreSQL server - Azure Arc ({0}) - Could not connect to PostgreSQL Hyperscale - Azure Arc Instance {0}. {1} + Could not connect to PostgreSQL server - Azure Arc Instance {0}. {1} A connection to the server is required to show and set database engine settings, which will require the PostgreSQL Extension to be installed. @@ -158,24 +161,9 @@ Coordinator - - Coordinator Node CPU limit - - - Coordinator Node CPU request - Coordinator endpoint - - Coordinator Node Memory limit (in GB) - - - Coordinator Node Memory request (in GB) - - - Coordinator Node - You can configure the number of CPU cores and storage size that will apply to the coordinator node. Adjust the number of CPU cores and memory settings for your server group. To reset the requests and/or limits, pass in empty value. @@ -428,10 +416,10 @@ Latest point in time - Learn more about database engine settings for Azure Arc-enabled PostgreSQL Hyperscale + Learn more about database engine settings for Azure Arc-enabled PostgreSQL - Learn more about Azure PostgreSQL Hyperscale client interfaces + Learn more about Azure PostgreSQL client interfaces Learn More. @@ -524,7 +512,7 @@ No worker server parameters found... - There aren’t any known issues affecting this PostgreSQL Hyperscale instance. + There aren’t any known issues affecting this PostgreSQL instance. The current version is the latest version. No upgrades available. @@ -614,7 +602,7 @@ A connection is required to show and set database engine settings. - PostgreSQL Hyperscale - Azure Arc + PostgreSQL server - Azure Arc Point in time restore @@ -650,7 +638,7 @@ Select a pod in the dropdown below for detailed health information - PostgreSQL Hyperscale server group by + PostgreSQL by Admin username @@ -662,7 +650,7 @@ You can scale your Azure Arc-enabled - PostgreSQL Hyperscale - Azure Arc Dashboard - {0} + PostgreSQL server - Azure Arc Dashboard (Preview) - {0} microsoft.azuredatastudio-postgresql @@ -799,12 +787,12 @@ Select from available client connection strings below. + + Server + Server Endpoint - - Server group nodes - Server group type @@ -937,18 +925,6 @@ Worker - - Worker Nodes CPU limit - - - Worker Nodes CPU request - - - Worker Nodes Memory limit (in GB) - - - Worker Nodes Memory request (in GB) - Worker node count @@ -1022,28 +998,36 @@ I accept {0} and {1}. - - Azure Arc-enabled PostgreSQL Hyperscale terms and conditions + + Azure Marketplace Terms - - Azure Arc enabled Managed Instance provides SQL Server access and feature compatibility that can be deployed on the infrastructure of your choice. {0}. + + Learn more + + + Privacy policy + + + Terms of use + + + PostgreSQL Server - Azure Arc is one of the database engines available as part of Azure Arc-enabled data services and it can be deployed on the infrastructure of your choice. {0}. By clicking 'Script to notebook' or 'Deploy', I (a) agree to the legal terms and privacy statement(s) associated with the Marketplace offering(s) listed below; (b) authorize Microsoft to bill my current payment method for the fees associated with the offering(s), with the same billing frequency as my Azure subscription; and (c) agree that Microsoft may share my contact, usage and transactional information with the provider(s) of the offering(s) for support, billing and other transactional activities. Microsoft does not provide rights for third-party offerings. For additional details see {1}, {2}, and {3}. - - Azure Marketplace Terms + + Learn more about PostgreSQL Server - Azure Arc - - Learn more + + PostgreSQL Server - Azure Arc terms and conditions + + + Azure Arc-enabled Managed Instance provides SQL Server access and feature compatibility that can be deployed on the infrastructure of your choice. {0}. + + By clicking 'Script to notebook' or 'Deploy', I (a) agree to the legal terms and privacy statement(s) associated with the Marketplace offering(s) listed below; (b) authorize Microsoft to bill my current payment method for the fees associated with the offering(s), with the same billing frequency as my Azure subscription; and (c) agree that Microsoft may share my contact, usage and transactional information with the provider(s) of the offering(s) for support, billing and other transactional activities. Microsoft does not provide rights for third-party offerings. For additional details see {1}, {2}, and {3}. - Learn more about Azure Arc enabled Managed Instance - - - Privacy policy - - - Terms of use + Learn more about Azure Arc-enabled Managed Instance Azure SQL managed instance - Azure Arc terms and conditions @@ -1312,101 +1296,68 @@ Password - + The maximum number of CPU cores for the Postgres instance that can be used on the coordinator node. Fractional cores are supported. - + CPU limit - + The minimum number of CPU cores that must be available on the coordinator node to schedule the service. Fractional cores are supported. - + CPU request - - The memory limit of the Postgres instance on the coordinator node in GB. - - - Memory limit (GB) - - - The memory request of the Postgres instance on the coordinator node in GB. - - - Memory request (GB) - - + Engine Version - + A comma-separated list of the Postgres extensions that should be loaded on startup. Please refer to the postgres documentation for supported values. - + Extensions - - Server group name + + The memory limit of the Postgres instance on the coordinator node in GB. - - Server group name must consist of lower case alphanumeric characters or '-', start with a letter, end with an alphanumeric character, and be 11 characters or fewer in length. + + Memory limit (GB) - + + The memory request of the Postgres instance on the coordinator node in GB. + + + Memory request (GB) + + + Server name + + + Server name must consist of lower case alphanumeric characters or '-', start with a letter, end with an alphanumeric character, and be 11 characters or fewer in length. + + Port - + The size of the storage volume to be used for backups in GB. - + Volume Size GB (Backups) - + The size of the storage volume to be used for data in GB. - + Volume Size GB (Data) - + The size of the storage volume to be used for logs in GB. - + Volume Size GB (Logs) - - The maximum number of CPU cores for the Postgres instance that can be used per node. Fractional cores are supported. - - - CPU limit (cores per node) - - - The minimum number of CPU cores that must be available per node to schedule the service. Fractional cores are supported. - - - CPU request (cores per node) - - - The number of worker nodes to provision in a sharded cluster, or zero (the default) for single-node Postgres. - - - Number of workers - - - The memory limit of the Postgres instance per node in GB. - - - Memory limit (GB per node) - - - The memory request of the Postgres instance per node in GB. - - - Memory request (GB per node) - - - Coordinator Node Compute Configuration - - - Worker Nodes Compute Configuration + + Compute Configuration General settings @@ -1424,10 +1375,10 @@ The storage class to be used for logs persistent volumes - Provide Azure enabled PostgreSQL Hyperscale server group parameters + Provide PostgreSQL server parameters - Deploy an Azure Arc-enabled PostgreSQL Hyperscale server group + Deploy a PostgreSQL Server - Azure Arc (Preview) SQL Connection information @@ -1716,10 +1667,10 @@ Requested memory must be less than or equal to memory limit - Deploy PostgreSQL Hyperscale server groups into an Azure Arc environment + Deploy a PostgreSQL server into an Azure Arc environment - PostgreSQL Hyperscale server groups - Azure Arc + PostgreSQL Server - Azure Arc (Preview) Managed SQL Instance service for app developers in a customer-managed environment diff --git a/resources/xlf/en/sql-migration.xlf b/resources/xlf/en/sql-migration.xlf index 4e98cb55f9..eb310b9873 100644 --- a/resources/xlf/en/sql-migration.xlf +++ b/resources/xlf/en/sql-migration.xlf @@ -441,9 +441,6 @@ This may take some time. Database backup - - Ensure that the Azure Storage account does not use a private endpoint. - Migration status @@ -1302,9 +1299,6 @@ This may take some time. I already have the performance data - - Generating Azure recommendations using provided performance data... - Select a folder on your local drive where previously collected performance data was saved @@ -1327,7 +1321,7 @@ This may take some time. Check back periodically for updated recommendations by pressing the 'Refresh recommendation' button. - Azure recommendation collects and analyzes performance data and then recommends an appropriate sized database in Azure for your workload. + Azure recommendation collects and analyzes performance data and then recommends an appropriate sized target in Azure for your workload. Data collection still in progress. Refining existing recommendations... @@ -1401,6 +1395,12 @@ This may take some time. Edit recommendation parameters + + Enable elastic recommendation + + + Elastic recommendation uses an alternate recommendation model which utilizes personalized price-performance profiling against existing on-cloud customers. + Enable preview features @@ -1914,7 +1914,7 @@ This may take some time. No recommendation available - No SKU recommendations were generated, as there were no SKUs which could satisfy the performance characteristics of your source. Try selecting a different target platform, adjusting recommendation parameters, or selecting a different set of databases to assess. + No SKU recommendations were generated, as there were no SKUs which could satisfy the performance characteristics of your source. Try selecting a different target platform, adjusting recommendation parameters, selecting a different set of databases to assess, or changing the recommendation model. Connection was successful but did not find any target databases.