[BULK] INCLUDE file maintenance: remove ssKilimanjaro

Author: rwestMSFT

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[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)].
+[!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[sql2008r2](../../../includes/sql2008r2-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|
 |------------------------------------------------------------------------------------|-----------------|

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpcontrol-ole-db.md

@@ -41,7 +41,7 @@ HRESULT BCPControl(
 |BCP_OPTION_BATCH|The number of rows per batch. The default is 0, which indicates all rows in a table when data is being extracted, or all rows in the user data file when data is being copied to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]. A value less than 1 resets BCP_OPTION_BATCH to the default.|  
 |BCP_OPTION_DELAYREADFMT|A Boolean, if set to true, will cause [IBCPSession::BCPReadFmt](../../oledb/ole-db-interfaces/ibcpsession-bcpreadfmt-ole-db.md) to read at execution. If false (the default), IBCPSession::BCPReadFmt will immediately read the format file. A sequence error will occur if **BCP_OPTION_DELAYREADFMT** is true and you call IBCPSession::BCPColumns or IBCPSession::BCPColFmt.<br /><br /> A sequence error will also occur if you call `IBCPSession::BCPControl(BCPDELAYREADFMT, (void *)FALSE))` after calling `IBCPSession::BCPControl(BCPDELAYREADFMT, (void *)TRUE)` and IBCPSession::BCPWriteFmt.<br /><br /> For more information, see [Metadata Discovery](../../oledb/features/metadata-discovery.md).|  
 |BCP_OPTION_FILECP|The *iValue* argument contains the number of the code page for the data file. You can specify the number of the code page, such as 1252 or 850, or one of the following values:<br /><br /> BCP_FILECP_ACP: data in the file is in the Microsoft Windows� code page of the client.<br /><br /> BCP_FILECP_OEMCP: data in the file is in the OEM code page of the client (default).<br /><br /> BCP_FILECP_RAW: data in the file is in the code page of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].|  
-|BCP_OPTION_FILEFMT|The version number of the data file format. This can be 80 ([!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)]), 90 ([!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]), 100 ([!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)] or [!INCLUDE[ssKilimanjaro](../../../includes/sskilimanjaro-md.md)]), or 110 ([!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)]). 110 is the default. This is useful for exporting and importing data in formats that were supported by earlier version of the server.  For example, to import data obtained from a text column in a [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] server into a **varchar(max)** column in a [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] or later server, you should specify 80. Similarly, if you specify 80 while exporting data from a **varchar(max)** column, it will be saved just like text columns are saved in the [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] format, and can be imported into a text column of a [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] server.|  
+|BCP_OPTION_FILEFMT|The version number of the data file format. This can be 80 ([!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)]), 90 ([!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]), 100 ([!INCLUDE[sql2008-md](../../../includes/sql2008-md.md)] or [!INCLUDE[sql2008r2](../../../includes/sql2008r2-md.md)]), or 110 ([!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)]). 110 is the default. This is useful for exporting and importing data in formats that were supported by earlier version of the server.  For example, to import data obtained from a text column in a [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] server into a **varchar(max)** column in a [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] or later server, you should specify 80. Similarly, if you specify 80 while exporting data from a **varchar(max)** column, it will be saved just like text columns are saved in the [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] format, and can be imported into a text column of a [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] server.|  
 |BCP_OPTION_FIRST|The first row of data of the file or table to copy. The default is 1; a value less than 1 resets this option to its default.|  
 |BCP_OPTION_FIRSTEX|For BCP out operations, specifies the first row of the database table to copy into the data file.<br /><br /> For BCP in operations, specifies the first row of the data file to copy into the database table.<br /><br /> The *iValue* parameter is expected to be the address of a signed 64-bit integer that contains the value. The maximum value that can be passed to BCPFIRSTEX 2^63-1.|  
 |BCP_OPTION_FMTXML|Used to specify that the format file generated should be in an XML format. It's off by default and the format files are saved as text files. The XML format file provides greater flexibility but with some added constraints. For example, you can't specify the prefix and terminator for a field simultaneously, which is possible in older format files.<br /><br /> Note: Before OLE DB Driver [18.6.0](../release-notes-for-oledb-driver-for-sql-server.md#1860), XML format files were only supported when [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] tools was installed along with the OLE DB Driver for SQL Server.|  

docs/database-engine/availability-groups/windows/remote-blob-store-rbs-and-always-on-availability-groups-sql-server.md

@@ -33,7 +33,7 @@ ms.custom: seodec18
 
 ##  <a name="RelatedContent"></a> Related Content  
 
--   [Maintaining Remote BLOB Store](https://msdn.microsoft.com/library/gg316773\(SQL.105\).aspx) (in [!INCLUDE[ssKilimanjaro](../../../includes/sskilimanjaro-md.md)] Books Online)  
+-   [Maintaining Remote BLOB Store](https://msdn.microsoft.com/library/gg316773\(SQL.105\).aspx) (in [!INCLUDE[sql2008r2](../../../includes/sql2008r2-md.md)] Books Online)  
 
 -   [Running RBS Maintainer](/archive/blogs/sqlrbs/running-rbs-maintainer) (blog)  
 

docs/database-engine/availability-groups/windows/service-broker-with-always-on-availability-groups-sql-server.md

@@ -67,7 +67,7 @@ helpviewer_keywords:
     > [!NOTE]  
     >  By default, each user database, including **msdb**, contains the route **AutoCreatedLocal**. This route matches any service name and broker instance and specifies that the message should be delivered within the current instance. **AutoCreatedLocal** has lower priority than routes that explicitly specify a specific service that communicates with a remote instance.  
   
-     For information about creating routes, see [Service Broker Routing Examples](https://msdn.microsoft.com/library/ms166090\(SQL.105\).aspx) (in the [!INCLUDE[ssKilimanjaro](../../../includes/sskilimanjaro-md.md)] version of Books Online) and [CREATE ROUTE (Transact-SQL)](../../../t-sql/statements/create-route-transact-sql.md).  
+     For information about creating routes, see [Service Broker Routing Examples](https://msdn.microsoft.com/library/ms166090\(SQL.105\).aspx) (in the [!INCLUDE[sql2008r2](../../../includes/sql2008r2-md.md)] version of Books Online) and [CREATE ROUTE (Transact-SQL)](../../../t-sql/statements/create-route-transact-sql.md).  
   
 ##  <a name="SendRemoteMessages"></a> Requirements for Sending Messages to a Remote Service in an Availability Group  
   

docs/database-engine/configure-windows/connect-to-the-database-engine-using-extended-protection.md

@@ -17,7 +17,7 @@ helpviewer_keywords:
 ---
 # Connect to the Database Engine Using Extended Protection
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports **Extended Protection** beginning with [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)]. **Extended Protection for Authentication** is a feature of the network components implemented by the operating system. **Extended Protection** is supported in Windows 7 and Windows Server 2008 R2. **Extended Protection** is included in service packs for older [!INCLUDE[msCoName](../../includes/msconame-md.md)] operating systems. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is more secure when connections are made using **Extended Protection**.  
+  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports **Extended Protection** beginning with [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)]. **Extended Protection for Authentication** is a feature of the network components implemented by the operating system. **Extended Protection** is supported in Windows 7 and Windows Server 2008 R2. **Extended Protection** is included in service packs for older [!INCLUDE[msCoName](../../includes/msconame-md.md)] operating systems. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is more secure when connections are made using **Extended Protection**.  
 
 > [!IMPORTANT]  
 > Windows does not enable **Extended Protection** by default. For information about how to enable **Extended Protection** in Windows, see [Extended Protection for Authentication](/dotnet/framework/wcf/feature-details/extended-protection-for-authentication-overview).
@@ -73,7 +73,7 @@ helpviewer_keywords:
 ## Enabling Extended Protection for the Database Engine  
  To use **Extended Protection**, both the server and the client must have an operating system on that supports **Extended Protection**, and **Extended Protection** must be enabled on the operating system. For more information about how to enable **Extended Protection** for the operating system, see [Extended Protection for Authentication](/dotnet/framework/wcf/feature-details/extended-protection-for-authentication-overview).  
 
- [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports **Extended Protection** beginning with [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)]. **Extended Protection** for some earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] will be made available in future updates. After enabling **Extended Protection** on the server computer, use the following steps to enable **Extended Protection**:  
+ [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports **Extended Protection** beginning with [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)]. **Extended Protection** for some earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] will be made available in future updates. After enabling **Extended Protection** on the server computer, use the following steps to enable **Extended Protection**:  
 
 1.  On the **Start** menu, choose **All Programs**, point to **Microsoft SQL Server** and then click **SQL Server Configuration Manager**.  
 

docs/database-engine/database-mirroring/database-mirroring-witness.md

@@ -41,7 +41,7 @@ helpviewer_keywords:
  A single-server instance can also function at the same time as a witness in some sessions and a partner in other sessions. However, in practice, a server instance typically functions as either a witness or a partner. This is because the partners require sophisticated computers that have enough hardware to support a production database, whereas the witness can run on any available Windows system that supports [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)].  
 
 ##  <a name="SwHwRecommendations"></a> Software and Hardware Recommendations  
- We strongly recommend that the witness reside on a separate computer from the partners. Database mirroring partners are supported only by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Standard edition and by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Enterprise edition. Witnesses, in contrast, are also supported by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Workgroup and by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Express. Except during an upgrade from an earlier version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], the server instances in a mirroring session must all be running the same version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For example, a [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] witness is supported when you are upgrading from a [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] mirroring configuration but cannot be added to an existing or new [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)] or later mirroring configuration.  
+ We strongly recommend that the witness reside on a separate computer from the partners. Database mirroring partners are supported only by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Standard edition and by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Enterprise edition. Witnesses, in contrast, are also supported by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Workgroup and by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Express. Except during an upgrade from an earlier version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], the server instances in a mirroring session must all be running the same version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For example, a [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] witness is supported when you are upgrading from a [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] mirroring configuration but cannot be added to an existing or new [!INCLUDE[sql2008r2](../../includes/sql2008r2-md.md)] or later mirroring configuration.  
 
  A witness can run on any reliable computer system that supports any of these editions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. However, we recommend that every server instance that is used as a witness correspond to the minimum configuration that is required for the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Standard version that you are running. For more information about these requirements, see [Hardware and Software Requirements for Installing SQL Server 2016](../../sql-server/install/hardware-and-software-requirements-for-installing-sql-server.md).  
 

docs/database-engine/deprecated-database-engine-features-in-sql-server-2016.md

@@ -46,7 +46,7 @@ The following [!INCLUDE[ssDEnoversion](../includes/ssdenoversion-md.md)] feature
 |Category|Deprecated feature|Replacement|Feature name|Feature ID|
 |--------------|------------------------|-----------------|------------------|----------------|
 |Backup and Restore|RESTORE { DATABASE &#124; LOG } WITH [MEDIA]PASSWORD continues to be deprecated. BACKUP { DATABASE &#124; LOG } WITH PASSWORD and BACKUP { DATABASE &#124; LOG } WITH MEDIAPASSWORD are discontinued.|None|BACKUP DATABASE or LOG WITH PASSWORD<br /><br /> BACKUP DATABASE or LOG WITH MEDIAPASSWORD|104<br /><br /> 103|
-|Compatibility levels|Upgrade from version 100 ([!INCLUDE[sql2008-md](../includes/sql2008-md.md)] and [!INCLUDE[ssKilimanjaro](../includes/sskilimanjaro-md.md)]).|When a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] version goes out of [support](/lifecycle/products/?products=sql-server), the associated database compatibility level will be marked deprecated. However, we will continue to support applications certified on any supported Database Compatibility Level as long as possible, to make the upgrades easier. For more information about compatibility levels, see [ALTER DATABASE Compatibility Level &#40;Transact-SQL&#41;](../t-sql/statements/alter-database-transact-sql-compatibility-level.md).|Database compatibility level 100|108|
+|Compatibility levels|Upgrade from version 100 ([!INCLUDE[sql2008-md](../includes/sql2008-md.md)] and [!INCLUDE[sql2008r2](../includes/sql2008r2-md.md)]).|When a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] version goes out of [support](/lifecycle/products/?products=sql-server), the associated database compatibility level will be marked deprecated. However, we will continue to support applications certified on any supported Database Compatibility Level as long as possible, to make the upgrades easier. For more information about compatibility levels, see [ALTER DATABASE Compatibility Level &#40;Transact-SQL&#41;](../t-sql/statements/alter-database-transact-sql-compatibility-level.md).|Database compatibility level 100|108|
 |Database objects|Ability to return result sets from triggers|None|Returning results from trigger|12|
 |Encryption|Encryption using RC4 or RC4_128 is deprecated and is scheduled to be removed in the next version. Decrypting RC4 and RC4_128 is not deprecated.|Use another encryption algorithm such as AES.|Deprecated encryption algorithm|253|
 |Hash algorithms|Using the MD2, MD4, MD5, SHA, and SHA1 is deprecated.|Use SHA2_256 or SHA2_512 instead. Older algorithms will continue working, but they will raise a deprecation event.|Deprecated hash algorithm|None|

docs/database-engine/deprecated-database-engine-features-in-sql-server-2017.md

@@ -54,7 +54,7 @@ The following [!INCLUDE[ssDEnoversion](../includes/ssdenoversion-md.md)] feature
 
 | Deprecated feature | Replacement | Feature name | Feature ID |
 |--------------------|-------------|--------------|------------|
-Upgrade from version 100 ([!INCLUDE[sql2008-md](../includes/sql2008-md.md)] and [!INCLUDE[ssKilimanjaro](../includes/ssKilimanjaro-md.md)]). | When a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] version goes out of [support](/lifecycle/products/?products=sql-server), the associated Database Compatibility Levels are marked deprecated. However, we continue to support applications certified on any supported database compatibility level as long as possible, to make the upgrades easier. For more information about compatibility levels, see [ALTER DATABASE Compatibility Level (Transact-SQL)](../t-sql/statements/alter-database-transact-sql-compatibility-level.md). | Database compatibility level 100 | 108 |
+Upgrade from version 100 ([!INCLUDE[sql2008-md](../includes/sql2008-md.md)] and [!INCLUDE[sql2008r2](../includes/sql2008r2-md.md)]). | When a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] version goes out of [support](/lifecycle/products/?products=sql-server), the associated Database Compatibility Levels are marked deprecated. However, we continue to support applications certified on any supported database compatibility level as long as possible, to make the upgrades easier. For more information about compatibility levels, see [ALTER DATABASE Compatibility Level (Transact-SQL)](../t-sql/statements/alter-database-transact-sql-compatibility-level.md). | Database compatibility level 100 | 108 |
 
 ### Database objects