Skip to content

Commit a0fc044

Browse files
WilliamDAssafMSFTWilliamDAssafMSFT
committed
20230724 refactor ssazure_md.md into ssazure-sqldb.md
1 parent f74cacb commit a0fc044

29 files changed

Lines changed: 116 additions & 116 deletions

‎docs/connect/jdbc/connecting-to-an-azure-sql-database.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: conceptual
1212

1313
[!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
1414

15-
This article discusses issues when you use the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] to connect to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)]. For more information to connect to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], see:
15+
This article discusses issues when you use the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] to connect to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]. For more information to connect to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], see:
1616

1717
- [Azure SQL Database](/azure/sql-database/sql-database-technical-overview)
1818

@@ -22,16 +22,16 @@ This article discusses issues when you use the [!INCLUDE[jdbcNoVersion](../../in
2222

2323
## Details
2424

25-
To connect to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], you should connect to the master database to call **SQLServerDatabaseMetaData.getCatalogs**.
26-
[!INCLUDE[ssAzure](../../includes/ssazure_md.md)] doesn't support returning the entire set of catalogs from a user database. **SQLServerDatabaseMetaData.getCatalogs** use the sys.databases view to get the catalogs. Refer to the discussion of permissions in [sys.databases (Transact-SQL)](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) to understand **SQLServerDatabaseMetaData.getCatalogs** behavior on an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)].
25+
To connect to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], you should connect to the master database to call **SQLServerDatabaseMetaData.getCatalogs**.
26+
[!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] doesn't support returning the entire set of catalogs from a user database. **SQLServerDatabaseMetaData.getCatalogs** use the sys.databases view to get the catalogs. Refer to the discussion of permissions in [sys.databases (Transact-SQL)](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) to understand **SQLServerDatabaseMetaData.getCatalogs** behavior on an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)].
2727

2828
## Login timeout
2929

3030
When connecting to Azure SQL databases, the recommended default `loginTimeout` is 30 seconds. If you're connecting to a serverless instance, it's recommended to use an even longer `loginTimeout` of 60 seconds or more. If the serverless instance has been idle, it can take some time to wake up on an initial connection. For more information on how to set the `loginTimeout`, see [Setting the connection properties](setting-the-connection-properties.md).
3131

3232
## Connections dropped
3333

34-
When you connect to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], idle connections may be terminated by a network component (such as a firewall) after a period of inactivity. There are two types of idle connections, in this context:
34+
When you connect to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], idle connections may be terminated by a network component (such as a firewall) after a period of inactivity. There are two types of idle connections, in this context:
3535

3636
- Idle at the TCP layer, where connections can be dropped by any number of network devices.
3737

@@ -82,11 +82,11 @@ shutdown /r /t 1
8282

8383
## Append the server name to the userId in the connection string
8484

85-
Prior to the 4.0 version of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], to connect to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], you were required to append the server name to the UserId in the connection string. For example, user@servername. Beginning in version 4.0 of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], it's no longer necessary to append @servername to the UserId in the connection string.
85+
Prior to the 4.0 version of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], to connect to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], you were required to append the server name to the UserId in the connection string. For example, user@servername. Beginning in version 4.0 of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], it's no longer necessary to append @servername to the UserId in the connection string.
8686

8787
## Using encryption requires setting hostNameInCertificate
8888

89-
Prior to the 7.2 version of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], to connect to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], you should specify **hostNameInCertificate** if you specify **encrypt=true** (If the server name in the connection string is *shortName*.*domainName*, set the **hostNameInCertificate** property to \*.*domainName*.). This property is optional as of version 7.2 of the driver.
89+
Prior to the 7.2 version of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], to connect to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], you should specify **hostNameInCertificate** if you specify **encrypt=true** (If the server name in the connection string is *shortName*.*domainName*, set the **hostNameInCertificate** property to \*.*domainName*.). This property is optional as of version 7.2 of the driver.
9090

9191
For example:
9292

‎docs/connect/jdbc/system-requirements-for-the-jdbc-driver.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: conceptual
1212

1313
[!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
1414

15-
To use the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] to access data from a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], you must have the following components installed on your computer:
15+
To use the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] to access data from a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], you must have the following components installed on your computer:
1616

1717
- [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] ([download](download-microsoft-jdbc-driver-for-sql-server.md))
1818
- Java Runtime Environment

‎docs/connect/odbc/connection-resiliency.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: conceptual
1212

1313
[!INCLUDE[Driver_ODBC_Download](../../includes/driver_odbc_download.md)]
1414

15-
To ensure that applications remain connected to an [!INCLUDE[ssAzure](../../includes/ssazure_md.md)], the ODBC driver can restore idle connections.
15+
To ensure that applications remain connected to an [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], the ODBC driver can restore idle connections.
1616

1717
> [!IMPORTANT]
1818
> The connection resiliency feature is supported on Microsoft Azure SQL Database and SQL Server 2014 (and later) server versions.

0 commit comments

Comments
 (0)