update SQL connection string placeholders

Author: huypub

articles/aks/howto-deploy-java-wls-app.md

@@ -554,7 +554,7 @@ In the previous steps, you created the auxiliary image including models and WDT.
 
    | Variable               | Description                                | Example                                                                                       |
    |------------------------|--------------------------------------------|-----------------------------------------------------------------------------------------------|
-   | `DB_CONNECTION_STRING` | The connection string of SQL server.       | `jdbc:sqlserver://sqlserverforwlsaks.database.windows.net:1433;database=wlsaksquickstart0125` |
+   | `DB_CONNECTION_STRING` | The connection string of SQL server.       | `jdbc:sqlserver://server-name.database.windows.net:1433;database=wlsaksquickstart0125` |
    | `DB_USER`              | The username to sign in to the SQL server. | `welogic@sqlserverforwlsaks`                                                                  |
    | `DB_PASSWORD`          | The password to sign in to the sQL server. | `Secret123456`                                                                                |
 
@@ -577,7 +577,7 @@ In the previous steps, you created the auxiliary image including models and WDT.
    In the following commands, be sure to set the variables `DB_CONNECTION_STRING`, `DB_USER`, and `DB_PASSWORD` correctly by replacing the placeholder examples with the values described in the previous steps. Be sure to enclose the value of the `DB_` variables in single quotes to prevent the shell from interfering with the values.
 
    ```bash
-   export DB_CONNECTION_STRING='<example-jdbc:sqlserver://sqlserverforwlsaks.database.windows.net:1433;database=wlsaksquickstart0125>'
+   export DB_CONNECTION_STRING='<example-jdbc:sqlserver://server-name.database.windows.net:1433;database=wlsaksquickstart0125>'
    export DB_USER='<example-welogic@sqlserverforwlsaks>'
    export DB_PASSWORD='<example-Secret123456>'
    export WLS_DOMAIN_NS=sample-domain1-ns

articles/hdinsight-aks/trino/trino-add-catalogs.md

@@ -79,7 +79,7 @@ This article demonstrates how you can add a new catalog to your cluster using AR
                         },
                         {
                             "fileName": "trinotestdb1.properties",
-                            "content":"connector.name=sqlserver\nconnection-url=jdbc:sqlserver://mysqlserver1.database.windows.net:1433;database=db1;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;\nconnection-user=${SECRET_REF:trinotest-admin-user}\nconnection-password=${SECRET_REF:trinotest-admin-pwd}\n"
+                            "content":"connector.name=sqlserver\nconnection-url=jdbc:sqlserver://server-name.database.windows.net:1433;database=db1;encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;\nconnection-user=${SECRET_REF:trinotest-admin-user}\nconnection-password=${SECRET_REF:trinotest-admin-pwd}\n"
                         },
                     ]
                 }

articles/hdinsight-aks/trino/trino-connect-to-metastore.md

@@ -41,7 +41,7 @@ Configure external Hive metastore database in `config.properties` file:
 {
     "fileName": "config.properties",
     "values": {
-        "hive.metastore.hdi.metastoreDbConnectionURL": "jdbc:sqlserver://mysqlserver1.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30",
+        "hive.metastore.hdi.metastoreDbConnectionURL": "jdbc:sqlserver://server-name.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30",
         "hive.metastore.hdi.metastoreDbConnectionUserName": "trinoadmin",
         "hive.metastore.hdi.metastoreDbConnectionPasswordSecret": "hms-db-pwd",
         "hive.metastore.hdi.metastoreWarehouseDir": "abfs://[email protected]/hive/warehouse"
@@ -50,7 +50,7 @@ Configure external Hive metastore database in `config.properties` file:
 ```
 | Property| Description| Example|
 |---|---|---|
-|hive.metastore.hdi.metastoreDbConnectionURL|JDBC connection string to database.|jdbc:sqlserver://mysqlserver1.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30|
+|hive.metastore.hdi.metastoreDbConnectionURL|JDBC connection string to database.|jdbc:sqlserver://server-name.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30|
 |hive.metastore.hdi.metastoreDbConnectionUserName|SQL user name to connect to database.|trinoadmin|
 |hive.metastore.hdi.metastoreDbConnectionPasswordSecret|Secret referenceName configured in secretsProfile with password.|hms-db-pwd|
 |hive.metastore.hdi.metastoreWarehouseDir|ABFS URI to location in storage where data is stored.|`abfs://[email protected]/hive/warehouse`|
@@ -127,7 +127,7 @@ To configure external Hive metastore to an existing Trino cluster, add the requi
                                         {
                                             "fileName": "config.properties",
                                             "values": {
-                                                "hive.metastore.hdi.metastoreDbConnectionURL": "jdbc:sqlserver://mysqlserver1.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30",
+                                                "hive.metastore.hdi.metastoreDbConnectionURL": "jdbc:sqlserver://server-name.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30",
                                                 "hive.metastore.hdi.metastoreDbConnectionUserName": "trinoadmin",
                                                 "hive.metastore.hdi.metastoreDbConnectionPasswordSecret": "hms-db-pwd",
                                                 "hive.metastore.hdi.metastoreWarehouseDir": "abfs://[email protected]/hive/warehouse"
@@ -181,7 +181,7 @@ Alternatively external Hive metastore database parameters can be specified in `t
 |---|---|---|
 |trinoProfile.catalogOptions.hive|List of Hive or iceberg or delta catalogs with parameters of external Hive metastore database, require parameters for each. To use external metastore database, catalog must be present in this list.
 |trinoProfile.catalogOptions.hive[*].catalogName|Name of Trino catalog configured in `serviceConfigsProfiles`, which configured to use external Hive metastore database.|hive1|
-|trinoProfile.catalogOptions.hive[*].metastoreDbConnectionURL|JDBC connection string to database.|jdbc:sqlserver://mysqlserver1.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30|
+|trinoProfile.catalogOptions.hive[*].metastoreDbConnectionURL|JDBC connection string to database.|jdbc:sqlserver://server-name.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30|
 |trinoProfile.catalogOptions.hive[*].metastoreDbConnectionUserName|SQL user name to connect to database.|trinoadmin|
 |trinoProfile.catalogOptions.hive[*].metastoreDbConnectionPasswordSecret|Secret referenceName configured in secretsProfile with password.|hms-db-pwd|
 |trinoProfile.catalogOptions.hive[*].metastoreWarehouseDir|ABFS URI to location in storage where data is stored.|`abfs://[email protected]/hive/warehouse`|
@@ -236,7 +236,7 @@ Alternatively external Hive metastore database parameters can be specified in `t
                             "hive": [
                                 {
                                     "catalogName": "hive1",
-                                    "metastoreDbConnectionURL": "jdbc:sqlserver://mysqlserver1.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30",
+                                    "metastoreDbConnectionURL": "jdbc:sqlserver://server-name.database.windows.net;database=myhmsdb1;encrypt=true;trustServerCertificate=true;create=false;loginTimeout=30",
                                     "metastoreDbConnectionUserName": "trinoadmin",
                                     "metastoreDbConnectionPasswordSecret": "hms-db-pwd",
                                     "metastoreWarehouseDir": "abfs://[email protected]/hive/warehouse"

articles/private-link/tutorial-inspect-traffic-azure-firewall.md

@@ -130,7 +130,7 @@ In this section, you enable the firewall logs and send them to the log analytics
     | Resource group | Select **test-rg**. |
     | **Database details** |  |
     | Database name | Enter **sql-db**. |
-    | Server | Select **Create new**. </br> Enter **sql-server-1** in **Server name** (Server names must be unique, replace **sql-server-1** with a unique value). </br> Select **(US) East US 2** in **Location**. </br> Select **Use SQL authentication**. </br> Enter a server admin sign-in and password. </br> Select **OK**. |
+    | Server | Select **Create new**. </br> Enter **server-name** in **Server name** (Server names must be unique, replace **server-name** with a unique value). </br> Select **(US) East US 2** in **Location**. </br> Select **Use SQL authentication**. </br> Enter a server admin sign-in and password. </br> Select **OK**. |
     | Want to use SQL elastic pool? | Select **No**. |
     | Workload environment | Leave the default of **Production**. |
     | **Backup storage redundancy** |  |
@@ -322,7 +322,7 @@ The route sends traffic from **vnet-1** to the address space of virtual network
 
 ## Configure an application rule in Azure Firewall
 
-Create an application rule to allow communication from **vnet-1** to the private endpoint of the Azure SQL server **sql-server-1.database.windows.net**. Replace **sql-server-1** with the name of your Azure SQL server.
+Create an application rule to allow communication from **vnet-1** to the private endpoint of the Azure SQL server **server-name.database.windows.net**. Replace **server-name** with the name of your Azure SQL server.
 
 1. In the search box at the top of the portal, enter **Firewall**. Select **Firewall Policies** in the search results.
 
@@ -348,7 +348,7 @@ Create an application rule to allow communication from **vnet-1** to the private
     | Source | Enter **10.0.0.0/16** |
     | Protocol | Enter **mssql:1433** |
     | Destination type | Select **FQDN**. |
-    | Destination | Enter **sql-server-1.database.windows.net**. |
+    | Destination | Enter **server-name.database.windows.net**. |
 
 1. Select **Add**.
 
@@ -367,7 +367,7 @@ Create an application rule to allow communication from **vnet-1** to the private
 1. To verify name resolution of the private endpoint, enter the following command in the terminal window:
 
     ```bash
-    nslookup sql-server-1.database.windows.net
+    nslookup server-name.database.windows.net
     ```
 
     You receive a message similar to the following example. The IP address returned is the private IP address of the private endpoint.
@@ -390,10 +390,10 @@ Create an application rule to allow communication from **vnet-1** to the private
 
     * Replace **\<admin-password>** with the admin password you entered during SQL server creation.
 
-    * Replace **sql-server-1** with the name of your SQL server.
+    * Replace **server-name** with the name of your SQL server.
 
     ```bash
-    sqlcmd -S sql-server-1.database.windows.net -U '<server-admin>' -P '<admin-password>'
+    sqlcmd -S server-name.database.windows.net -U '<server-admin>' -P '<admin-password>'
     ```
 
 1. A SQL command prompt is displayed on successful sign in. Enter **exit** to exit the **sqlcmd** tool.
@@ -408,7 +408,7 @@ Create an application rule to allow communication from **vnet-1** to the private
 
 1. In the example **Queries** in the search box, enter **Application rule**. In the returned results in **Network**, select the **Run** button for **Application rule log data**.
 
-1. In the log query output, verify **sql-server-1.database.windows.net** is listed under **FQDN** and **SQLPrivateEndpoint** is listed under **Rule**.
+1. In the log query output, verify **server-name.database.windows.net** is listed under **FQDN** and **SQLPrivateEndpoint** is listed under **Rule**.
 
 [!INCLUDE [portal-clean-up.md](../../includes/portal-clean-up.md)]
 

articles/private-link/tutorial-private-endpoint-sql-portal.md

@@ -123,7 +123,7 @@ In this section, you use the virtual machine you created in the previous steps t
 1. To verify name resolution of the private endpoint, enter the following command in the terminal window:
 
     ```bash
-    nslookup sql-server-1.database.windows.net
+    nslookup server-name.database.windows.net
     ```
 
     You receive a message similar to the following example. The IP address returned is the private IP address of the private endpoint.
@@ -149,7 +149,7 @@ In this section, you use the virtual machine you created in the previous steps t
     * Replace **sql-server-1** with the name of your SQL server.
 
     ```bash
-    sqlcmd -S sql-server-1.database.windows.net -U '<server-admin>' -P '<admin-password>'
+    sqlcmd -S server-name.database.windows.net -U '<server-admin>' -P '<admin-password>'
     ```
 
 1. A SQL command prompt is displayed on successful sign in. Enter **exit** to exit the **sqlcmd** tool.