Merge branch 'main' into release-dallas

Author: v-alje

azure-sql/migration-guides/managed-instance/sql-server-to-managed-instance-guide.md

@@ -6,8 +6,8 @@ ms.subservice: migration-guide
 ms.custom: 
 ms.devlang: 
 ms.topic: how-to
-author: mokabiru
-ms.author: mokabiru
+author: croblesm
+ms.author: roblescarlos
 ms.reviewer: mathoma, danil, randolphwest
 ms.date: 04/11/2022
 ---
@@ -20,8 +20,7 @@ This guide helps you migrate your SQL Server instance to Azure SQL Managed Insta
 You can migrate SQL Server running on-premises or on: 
 
 - SQL Server on Virtual Machines  
-- Amazon Web Services (AWS) EC2 
-- Amazon Relational Database Service (AWS RDS) 
+- Amazon Web Services (AWS) EC2
 - Compute Engine (Google Cloud Platform - GCP)  
 - Cloud SQL for SQL Server (Google Cloud Platform – GCP) 
 

docs/connect/jdbc/configuring-how-java-sql-time-values-are-sent-to-the-server.md

@@ -33,7 +33,7 @@ You can configure how the java.sql.Time value is sent by using the **sendTimeAsD
 
 You can programmatically modify the value of the **sendTimeAsDatetime** connection property with [SQLServerDataSource.setSendTimeAsDatetime](reference/setsendtimeasdatetime-method-sqlserverdatasource.md).
 
-Versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] earlier than [!INCLUDE[ssKatmai](../../includes/sskatmai_md.md)] don't support the **time** data type, so applications using java.sql.Time typically store java.sql.Time values either as **datetime** or **smalldatetime** [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data types.
+Versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] earlier than [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] don't support the **time** data type, so applications using java.sql.Time typically store java.sql.Time values either as **datetime** or **smalldatetime** [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data types.
 
 If you want to use the **datetime** and **smalldatetime**[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data types when working with java.sql.Time values, you should set the **sendTimeAsDatetime** connection property to **true**. If you want to use the **time** [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data type when working with java.sql.Time values, you should set the **sendTimeAsDatetime** connection property to **false**.
 

docs/connect/jdbc/feature-dependencies-of-microsoft-jdbc-driver-for-sql-server.md

@@ -22,7 +22,7 @@ This article lists libraries that the Microsoft JDBC Driver for SQL Server depen
 
 - `com.azure:azure-security-keyvault-keys`: Microsoft Azure Client Library For KeyVault Keys for JDBC driver version 9.2 and above or `com.microsoft.azure:azure-keyvault`: Microsoft Azure SDK For Key Vault for JDBC driver version 8.4 and below for Always Encrypted Azure Key Vault feature. (optional)
 - `com.azure:azure-identity`: Microsoft Azure Client Library For Identity for JDBC driver version 9.2 and above or `com.microsoft.azure:adal4j`: Microsoft Azure Active Directory Authentication Library for JDBC driver version 8.4 and below for Azure Active Directory Authentication features and Azure Key Vault feature. (optional)
-- `com.microsoft.azure:msal4j`: Microsoft Authentication Library (MSAL) For Java
+- `com.microsoft.azure:msal4j`: Microsoft Authentication Library (MSAL) For Java. (optional)
 - `org.antlr:antlr4-runtime`: ANTLR 4 Runtime for useFmtOnly feature. (optional)
 - `org.osgi:org.osgi.core`: OSGi Core library for OSGi Framework support.
 - `org.osgi:org.osgi.compendium`: OSGi Compendium library for OSGi Framework support.

docs/connect/jdbc/international-features-of-the-jdbc-driver.md

@@ -51,7 +51,7 @@ For date, time, and currencies, all formatting with localized data is done at th
 
 ## Collation support
 
-The JDBC Driver 3.0 supports all the collations supported by [!INCLUDE[ssVersion2000](../../includes/ssversion2000-md.md)], [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)], and the new collations or new versions of Windows collation names introduced in [!INCLUDE[ssKatmai](../../includes/sskatmai_md.md)].
+The JDBC Driver 3.0 supports all the collations supported by [!INCLUDE[ssVersion2000](../../includes/ssversion2000-md.md)], [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)], and the new collations or new versions of Windows collation names introduced in [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)].
 
 For more information on the collations, see [Collation and Unicode Support](/previous-versions/sql/sql-server-2008-r2/ms143503(v=sql.105)) and [Windows Collation Name (Transact-SQL)](../../t-sql/statements/windows-collation-name-transact-sql.md).
 

docs/connect/jdbc/jdbc-driver-support-for-high-availability-disaster-recovery.md

@@ -17,7 +17,7 @@ ms.author: v-davidengel
 
 [!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
 
-  This article discusses [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] support for high-availability, disaster recovery: [!INCLUDE[ssHADR](../../includes/sshadr_md.md)]. For more information about [!INCLUDE[ssHADR](../../includes/sshadr_md.md)], see [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] Books Online.
+  This article discusses [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] support for high-availability, disaster recovery: [!INCLUDE[ssHADR](../../includes/sshadr-md.md)]. For more information about [!INCLUDE[ssHADR](../../includes/sshadr-md.md)], see [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] Books Online.
 
  Beginning in version 4.0 of the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], you can specify the availability group listener of a (high-availability, disaster-recovery) availability group (AG) in the connection property. If a [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] application is connected to an Always On database that fails over, the original connection is broken, and the application must open a new connection to continue work after the failover. The following [connection properties](setting-the-connection-properties.md) were added in [!INCLUDE[jdbc_40](../../includes/jdbc_40_md.md)]:
 

docs/connect/jdbc/reference/getcolumns-method-sqlserverdatabasemetadata.md

@@ -101,7 +101,7 @@ public java.sql.ResultSet getColumns(java.lang.String catalog,
 
  The DATA_TYPE column has the following changes:  
 
-|[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Data Type|Return Type in JDBC Driver 2.0 (or, if connected to [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]) and Associated Numeric Constant|Return Type in JDBC Driver 3.0 when connected to [!INCLUDE[ssKatmai](../../../includes/sskatmai_md.md)] or later|  
+|[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Data Type|Return Type in JDBC Driver 2.0 (or, if connected to [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]) and Associated Numeric Constant|Return Type in JDBC Driver 3.0 when connected to [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)] or later|  
 |-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|  
 |user-defined type larger than 8 kB|LONGVARBINARY (-4)|VARBINARY (-3)|  
 |geography|LONGVARBINARY (-4)|VARBINARY (-3)|  

docs/connect/jdbc/release-notes-for-the-jdbc-driver.md

@@ -905,7 +905,7 @@ The driver supports JDK version 7.0 in addition to JDK 6.0 and 5.0.
 
 ## Itanium not supported for JDBC Driver applications
 
-Microsoft JDBC Driver for SQL Server applications aren't supported to run on an Itanium computer.
+Microsoft JDBC Driver for SQL Server isn't supported on Itanium computers.
 
 ## See also
 

docs/connect/jdbc/setting-the-connection-properties.md

@@ -98,7 +98,7 @@ The following table lists all the currently available connection string properti
 | sendTemporalDataTypesAsStringForBulkCopy<br/><br/>boolean<br/>["true" &#124; "false"]<br/><br/>true | (Version 8.4+) This connection property, when set to "false", sends **DATE**, **DATETIME**, **DATIMETIME2**, **DATETIMEOFFSET**, **SMALLDATETIME**, and **TIME** datatypes as their respective types instead of sending them as String.<br/><br/>With this connection property set to "false", the driver will only accept the default string literal format of each temporal datatype, for example:<br/><br/>DATE: `YYYY-MM-DD`<br/>DATETIME: `YYYY-MM-DD hh:mm:ss[.nnn]`<br/>DATETIME2: `YYYY-MM-DD hh:mm:ss[.nnnnnnn]`<br/>DATETIMEOFFSET: `YYYY-MM-DD hh:mm:ss[.nnnnnnn] [{+/-}hh:mm]`<br/>SMALLDATETIME: `YYYY-MM-DD hh:mm:ss`<br/>TIME: `hh:mm:ss[.nnnnnnn]`<br/> |
 | sendTimeAsDatetime<br/><br/>boolean<br/>["true" &#124; "false"]<br/><br/>true | This property was added in SQL Server JDBC Driver 3.0.<br/><br/> Set to "true" to send java.sql.Time values to the server as [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] **datetime** values. <br/>Set to "false" to send java.sql.Time values to the server as [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] **time** values.<br/><br/> The default value for this property is currently "true" and might change in a future release.<br/><br/> For more information about how the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] configures java.sql.Time values before it sends them to the server, see [Configuring How java.sql.Time Values are Sent to the Server](configuring-how-java-sql-time-values-are-sent-to-the-server.md). |
 | serverCertificate,<br/>server<br/><br/>String<br/><br/>null | (Version 11.2.0+) The path to the server certificate file. Used for validation when using **encrypt** set to **strict**. The driver supports certificate files using the PEM file format. |
-| serverName,<br/>server<br/><br/>String<br/><br/>null | The computer running [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or an Azure SQL database.<br/><br/> You can also specify the Virtual Network Name of an [!INCLUDE[ssHADR](../../includes/sshadr_md.md)] availability group. For more information about disaster recovery, see [JDBC driver support for High Availability, disaster recovery](jdbc-driver-support-for-high-availability-disaster-recovery.md). |
+| serverName,<br/>server<br/><br/>String<br/><br/>null | The computer running [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or an Azure SQL database.<br/><br/> You can also specify the Virtual Network Name of an availability group. For more information about disaster recovery, see [JDBC driver support for High Availability, disaster recovery](jdbc-driver-support-for-high-availability-disaster-recovery.md). |
 | serverNameAsACE<br/><br/>boolean<br/>["true" &#124; "false"]<br/><br/>false | (Version 6.0+) Set to "true" to indicate that the driver should translate the Unicode server name to ASCII compatible encoding (Punycode) for the connection. If this setting is false, the driver uses the server name as provided to connect.<br/><br/> For more information about international features, see [International features of the JDBC driver](international-features-of-the-jdbc-driver.md). |
 | serverPreparedStatement...<br/>DiscardThreshold<br/><br/>Integer<br/><br/>10 | (Version 6.2+) This property can be used to control how many outstanding prepared statement discard actions (<code>sp_unprepare</code>) can be outstanding per connection before a call to clean up the outstanding handles on the server is executed. <br/><br/> If this property is set to &lt;= 1, unprepare actions are executed immediately on prepared statement close. If it's set to &gt;1, these calls are batched together to avoid overhead of calling sp_unprepare too often. |
 | serverSpn<br/><br/>String<br/><br/>null | (Version 4.2+) This optional property can be used to specify the Service Principal Name (SPN) for a Java Kerberos connection.  It's used with **authenticationScheme**.<br/><br/> To specify the SPN, it can be in the form of: "MSSQLSvc/fqdn:port@REALM" where fqdn is the fully qualified domain name, port is the port number, and REALM is the Kerberos realm of the SQL Server in upper-case letters.<br/><br/> Note: the @REALM is optional if the default realm of the client (as specified in the Kerberos configuration) is the same as the Kerberos realm for the SQL Server.<br/><br/> For more information about using **serverSpn** with Java Kerberos, see [Using Kerberos integrated authentication to connect to SQL Server](using-kerberos-integrated-authentication-to-connect-to-sql-server.md). |

docs/connect/jdbc/sparse-columns.md

@@ -19,7 +19,7 @@ ms.author: v-davidengel
 
 Sparse columns are ordinary columns that have an optimized storage for null values. Sparse columns reduce the space requirements for null values at the cost of more overhead to retrieve non-null values. Consider using sparse columns when the space saved is at least 20 percent to 40 percent.
 
-The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] JDBC Driver 3.0 supports sparse columns when you connect to a [!INCLUDE[ssKatmai](../../includes/sskatmai_md.md)] (or later) server. You can use [SQLServerDatabaseMetaData.getColumns](reference/getcolumns-method-sqlserverdatabasemetadata.md), [SQLServerDatabaseMetaData.getFunctionColumns](reference/getfunctioncolumns-method-sqlserverdatabasemetadata.md), or [SQLServerDatabaseMetaData.getProcedureColumns](reference/getprocedurecolumns-method-sqlserverdatabasemetadata.md) to determine which column is sparse and which column is the column set column.
+The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] JDBC Driver 3.0 supports sparse columns when you connect to a [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] (or later) server. You can use [SQLServerDatabaseMetaData.getColumns](reference/getcolumns-method-sqlserverdatabasemetadata.md), [SQLServerDatabaseMetaData.getFunctionColumns](reference/getfunctioncolumns-method-sqlserverdatabasemetadata.md), or [SQLServerDatabaseMetaData.getProcedureColumns](reference/getprocedurecolumns-method-sqlserverdatabasemetadata.md) to determine which column is sparse and which column is the column set column.
 
 The code file for this sample is named SparseColumns.java, and it can be found in the following location:
 

docs/connect/jdbc/user-defined-types.md

@@ -17,7 +17,7 @@ ms.author: v-davidengel
 
 [!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
 
-User-defined types (UDTs) were introduced in [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] to allow a developer to extend the server's scalar type system by storing common language runtime (CLR) objects in a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. UDTs can contain multiple elements and can have behaviors, unlike the traditional alias data types, that consist of a single [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] system data type. Previously, UDTs were restricted to a maximum size of 8 kilobytes. In [!INCLUDE[ssKatmai](../../includes/sskatmai_md.md)], support was added for UDTs larger than 64 kilobytes. Beginning in version 3.0, the JDBC Driver also supports UDTs larger than 64 kilobytes when you specify the UserDefined format.
+User-defined types (UDTs) were introduced in [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] to allow a developer to extend the server's scalar type system by storing common language runtime (CLR) objects in a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. UDTs can contain multiple elements and can have behaviors, unlike the traditional alias data types, that consist of a single [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] system data type. Previously, UDTs were restricted to a maximum size of 8 kilobytes. In [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], support was added for UDTs larger than 64 kilobytes. Beginning in version 3.0, the JDBC Driver also supports UDTs larger than 64 kilobytes when you specify the UserDefined format.
 
 There is no behavior change for UDTs that are less than or equal to 8,000 bytes, but larger UDTs are supported and report their size as "unlimited".