[BULK] INCLUDE file maintenance: replace sskatmai-md.md

Author: rwestMSFT

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

@@ -29,7 +29,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[sql2008-md](../../includes/sql2008-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/international-features-of-the-jdbc-driver.md

@@ -47,7 +47,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[sql2008-md](../../includes/sql2008-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/reference/getcolumns-method-sqlserverdatabasemetadata.md

@@ -95,7 +95,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[sql2008-md](../../../includes/sql2008-md.md)] and later versions|  
 |-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|  
 |user-defined type larger than 8 kB|LONGVARBINARY (-4)|VARBINARY (-3)|  
 |geography|LONGVARBINARY (-4)|VARBINARY (-3)|  

docs/connect/jdbc/sparse-columns.md

@@ -15,7 +15,7 @@ ms.topic: conceptual
 
 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 server running [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] and later versions. 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

@@ -13,7 +13,7 @@ ms.topic: conceptual
 
 [!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[sql2008-md](../../includes/sql2008-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".
 

docs/connect/oledb/applications/updating-an-application-from-sql-server-2005-native-client.md

@@ -20,7 +20,7 @@ This article discusses the breaking changes in OLE DB Driver for SQL Server sinc
 
 When you upgrade from Microsoft Data Access Components (MDAC) to OLE DB Driver for SQL Server, you might also see some behavior differences. For more information, see [Updating an Application to OLE DB Driver for SQL Server from MDAC](updating-an-application-to-oledb-driver-for-sql-server-from-mdac.md).
 
-[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 9.0 shipped with [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]. [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 10.0 shipped with [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)].  [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 10.5 shipped with [!INCLUDE[ssKilimanjaro](../../../includes/sskilimanjaro-md.md)]. [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 11.0 shipped with [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)] and [!INCLUDE[ssSQL14](../../../includes/sssql14-md.md)].
+[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 9.0 shipped with [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]. [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 10.0 shipped with [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)].  [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 10.5 shipped with [!INCLUDE[ssKilimanjaro](../../../includes/sskilimanjaro-md.md)]. [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 11.0 shipped with [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)] and [!INCLUDE[ssSQL14](../../../includes/sssql14-md.md)].
 
 |Changed behavior in OLE DB Driver for SQL Server compared to [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] Native Client|Description|
 |------------------------------------------------------------------------------------|-----------------|
@@ -34,7 +34,7 @@ When you upgrade from Microsoft Data Access Components (MDAC) to OLE DB Driver f
 |IBCPSession::BCColFmt conversion changes.|In OLE DB Driver for SQL Server, when you use IBCPSession::BCOColFmt to convert SQLDATETIME or SQLDATETIME to a string type, a fractional value is exported. For example, when converting type SQLDATETIME to type SQLNVARCHARMAX, versions prior to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 10.0 returned<br /> 1989-02-01 00:00:00.<br />OLE DB Driver for SQL Server returns <br />1989-02-01 00:00:00.0000000.|
 |Custom applications that use the BCP API can now see a warning.|The BCP API will generate a warning message if data length is greater than the specified length for a field for all types. Previously, this warning was only given for character types, but will not be issued for all types.|
 |Inserting an empty string into a **sql_variant** bound as a date/time type generates an error.|In [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client 9.0, inserting an empty string into a **sql_variant** bound as a date/time type did not generate an error. OLE DB Driver for SQL Server correctly generates an error in this situation.|
-|[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] might return different results when a trigger runs.|Changes introduced in [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)] might cause an application to have different results returned from a statement that caused a trigger to run when **NOCOUNT OFF** was in effect. In this situation, your application might generate an error. To resolve this error, set **NOCOUNT ON** in the trigger.|
+|[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] might return different results when a trigger runs.|Changes introduced in [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)] might cause an application to have different results returned from a statement that caused a trigger to run when **NOCOUNT OFF** was in effect. In this situation, your application might generate an error. To resolve this error, set **NOCOUNT ON** in the trigger.|
 
 ## See also
 

docs/connect/oledb/features/date-and-time-improvements.md

@@ -13,7 +13,7 @@ ms.topic: "reference"
 
 [!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
 
-  This topic describes the OLE DB Driver for SQL Server support for the date and time data types that were added in [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)].
+  This topic describes the OLE DB Driver for SQL Server support for the date and time data types that were added in [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)].
 
  For more information about date/time improvements, see [Date and Time Improvements (OLE DB)](../../oledb/ole-db-date-time/date-and-time-improvements-ole-db.md).
 
@@ -22,7 +22,7 @@ ms.topic: "reference"
  The following sections describe various ways of using the new date and time types.  
 
 ### Use Date as a Distinct Data Type  
- Beginning with [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)], enhanced support for date/time types makes it more efficient to use the DBTYPE_DBDATE OLE DB type.  
+ Beginning with [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)], enhanced support for date/time types makes it more efficient to use the DBTYPE_DBDATE OLE DB type.  
 
 ### Use Time as a Distinct Data Type  
  OLE DB already has a data type that just contains the time, DBTYPE_DBTIME, which has a precision of 1 second.
@@ -39,7 +39,7 @@ ms.topic: "reference"
  Some applications require datetime values with timezone information. This is supported by the new DBTYPE_DBTIMESTAMPOFFSET type.
 
 ### Use Date/Time/Datetime/Datetimeoffset Data with Client-Side Conversions Consistent with Existing Conversions  
- The conversions are extended in a consistent manner to include conversions between all date and time types introduced in [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)].  
+ The conversions are extended in a consistent manner to include conversions between all date and time types introduced in [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)].  
 
 ## See Also  
  [OLE DB Driver for SQL Server Features](../../oledb/features/oledb-driver-for-sql-server-features.md)  

docs/connect/oledb/features/filestream-support.md

@@ -16,7 +16,7 @@ helpviewer_keywords:
 
 [!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
 
-Beginning with [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)], OLE DB Driver for SQL Server supports the enhanced FILESTREAM feature. For samples, see [Filestream and OLE DB](../../oledb/ole-db-how-to/filestream/filestream-and-ole-db.md).  
+Beginning with [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)], OLE DB Driver for SQL Server supports the enhanced FILESTREAM feature. For samples, see [Filestream and OLE DB](../../oledb/ole-db-how-to/filestream/filestream-and-ole-db.md).  
 
 FILESTREAM provides a way to store and access large binary values, either through [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] or by direct access to the Windows file system. A large binary value is a value larger than 2 gigabytes (GB). For more information about enhanced FILESTREAM support, see [FILESTREAM (SQL Server)](../../../relational-databases/blob/filestream-sql-server.md).  
 

docs/connect/oledb/features/large-clr-user-defined-types.md

@@ -15,7 +15,7 @@ helpviewer_keywords:
 
 [!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
 
-  In SQL Server 2005, user-defined types (UDTs) in the common language runtime (CLR) were restricted to 8,000 bytes in size. This restriction has been lifted in [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)] and later versions. CLR UDTs are now treated in a similar way to large object (LOB) types. That is, UDTs less than or equal to 8,000 bytes behave the same way as in SQL Server 2005, but larger UDTs are supported and report their size as "unlimited".  
+  In SQL Server 2005, user-defined types (UDTs) in the common language runtime (CLR) were restricted to 8,000 bytes in size. This restriction has been lifted in [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)] and later versions. CLR UDTs are now treated in a similar way to large object (LOB) types. That is, UDTs less than or equal to 8,000 bytes behave the same way as in SQL Server 2005, but larger UDTs are supported and report their size as "unlimited".  
 
  For more information, see [Large CLR User-Defined Types (OLE DB)](../../oledb/ole-db/large-clr-user-defined-types-ole-db.md).  
 

docs/connect/oledb/features/service-principal-name-spn-support-in-client-connections.md

@@ -18,7 +18,7 @@ helpviewer_keywords:
 
 [!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
 
-Beginning with [!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)], support for service principal names (SPNs) has been extended to enable mutual authentication across all protocols. In previous versions of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], SPNs were only supported for Kerberos over TCP when the default SPN for the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance was registered with Active Directory.
+Beginning with [!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)], support for service principal names (SPNs) has been extended to enable mutual authentication across all protocols. In previous versions of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], SPNs were only supported for Kerberos over TCP when the default SPN for the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance was registered with Active Directory.
 
 SPNs are used by the authentication protocol to determine the account in which a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance runs. If the instance account is known, Kerberos authentication can be used to provide mutual authentication by the client and server. If the instance account isn't known, NTLM authentication, which only provides authentication of the client by the server, is used. Currently, OLE DB Driver for SQL Server does the authentication lookup, deriving the SPN from the instance name and network connection properties. [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instances will attempt to register SPNs on startup, or they can be registered manually. However, registration will fail if there are insufficient access rights for the account that attempts to register the SPNs.