Merge pull request from MicrosoftDocs/master

v-alje · web-flow · commit 721ad1cbc10e · 2017-12-06T15:31:30.000-08:00
12/6 PM Publish
diff --git a/docs/analysis-services/instances/TOC.md b/docs/analysis-services/instances/TOC.md
@@ -15,7 +15,7 @@
 ## [Kerberos authentication](configure-analysis-services-for-kerberos-constrained-delegation.md)  
 ## [SPN registration](spn-registration-for-an-analysis-services-instance.md)  
 ## [HTTP Access](configure-http-access-to-analysis-services-on-iis-8-0.md)  
-## [Data providers](data-providers-used-for-analysis-services-connections.md)  
+## [Client libraries (data providers)](data-providers-used-for-analysis-services-connections.md)  
 ## [Disconnect users and sessions](disconnect-users-and-sessions-on-analysis-services-server.md)  
 # [Monitor an Analysis Services Instance](monitor-an-analysis-services-instance.md)  
 ## [SQL Server Profiler](use-sql-server-profiler-to-monitor-analysis-services.md)  
diff --git a/docs/analysis-services/instances/data-providers-used-for-analysis-services-connections.md b/docs/analysis-services/instances/data-providers-used-for-analysis-services-connections.md
@@ -1,7 +1,7 @@
 ---
 title: "Data providers used for Analysis Services connections | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/04/2017"
+ms.date: "12/06/2017"
 ms.prod: "sql-non-specified"
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -21,95 +21,21 @@ ms.author: "owend"
 manager: "kfile"
 ms.workload: "On Demand"
 ---
-# Data providers used for Analysis Services connections
-  Analysis Services provides three data providers for server and data access. All applications connecting to Analysis Services do so using one of these providers. Two of the providers, ADOMD.NET and Analysis Services Management Objects (AMO), are managed data providers. The Analysis Services OLE DB provider (MSOLAP DLL) is a native data provider.  
-  
- In organizations that run multiple versions of Analysis Services, you might need to install more recent versions of the data providers on user workstations connecting to Analysis Services data. Connections to newer versions of Analysis Services require data providers from the same major release. For example, to connect to [!INCLUDE[ssASCurrent](../../includes/ssascurrent-md.md)], each workstation must have a data provider from the same release. Although Excel installs the data providers it needs to connect, that provider can be out of date relative to the Analysis Services instances you are using.  
-  
- This topic contains the following sections:  
-  
- [How to determine server version](#bkmk_ServVers)  
-  
- [How to determine the version of the Analysis Services data providers](#bkmk_LibUpdate)  
-  
- [Where to get newer version data providers](#bkmk_downloadsite)  
-  
- [Analysis Services OLE DB Provider](#bkmk_OLE)  
-  
- [ADOMD.NET](#bkmk_ADOMD)  
-  
- [AMO](#blkmk_AMO)  
-  
-##  <a name="bkmk_ServVers"></a> How to determine server version  
- Knowing the version of the Analysis Services instance will help you determine whether you need to install newer versions of the data providers on workstations in your organization.  
-  
--   In SQL Server Management Studio, connect to the Analysis Services instance. You can view version info in **Server Properties** > **General** > **Version**.  
-  
- The major build number of the initial release of [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] is 13.0.1601.5.  
-  
-  
-##  <a name="bkmk_LibUpdate"></a> How to determine the version of the Analysis Services data providers  
- Data providers are installed with Analysis Services, as well as by client applications that routinely connect to Analysis Services databases, such as Excel.  
-  
- Office 2010 installs data providers from SQL Server 2008. Office 2013 installs data providers from SQL Server 2012, and so on. If you are using multiple versions of Office or SQL Server, and connections or feature availability are not what you expect, you might need to install a newer version of the data providers. You can run multiple major versions of each data provider side by side on the same computer.  
-  
-#### Find the file version of the OLEDB provider  
-  
-1.  Go to \Program Files\Microsoft Analysis Services\AS OLEDB\130.  
-  
-2.  Right-click **msolap130.dll** > **Properties** > **Details**.  
-  
- If you cannot find the file at this location, or if the folder path includes AS OLEDB\110 or AS OLEDB\90, you are using an older library and must now install a newer version (AS OLEDB\11) to connect to [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)].  
-  
-#### Find the file version of ADOMD.NET and AMO  
-  
-1.  Go to C:\Windows\Assembly  
-  
-2.  Right-click Microsoft.AnalysisServices.AdomdClient and click **Properties**. Click **Version**.  
-  
-     For AMO, right-click Microsoft.AnalysisServices.  
-  
-##  <a name="bkmk_downloadsite"></a> Where to get newer version data providers  
+
+# Client libraries (data providers) used for Analysis Services connections
+
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
+Analysis Services provides three client libraries, also known as **data providers**, for server and data access from tools and client applications. Tools like SSMS and SSDT, and applications like Power BI Desktop and Excel connect to Analysis Services by using these libraries. Two of the client libraries, ADOMD.NET and Analysis Services Management Objects (AMO), are managed client libraries. The Analysis Services OLE DB provider (MSOLAP DLL) is a native client library. 
+  
+##  <a name="bkmk_downloadsite"></a> Where to get newer versions  
  The version installed on the client computer should match the major version of the server providing the data. If the server installation is newer than the data providers installed on the workstations in your network, you might need to install newer libraries.  
+
+Client libraries included in earlier SQL Server Feature Packs correspond to that SQL version; however, they may not be the latest. Connecting to Azure Analysis Services may require later versions. All versions are backward compatible.
+
+To get the latest,  see [Client libraries for connecting to Azure Analysis Services](https://docs.microsoft.com/azure/analysis-services/analysis-services-data-providers). 
   
-#### Find the data providers on the download site  
-  
-1.  Go to the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=52676).  
-  
-2.  Click **Download**. ADOMD.NET, the OLE DB provider, and AMO are included in the list as an installable package. For example, SQL_AS_OLEDB.msi. Each library is available in 32-bit or 64-bit versions. Servers and newer workstations running a 64-bit operating system will require the 64-bit version.  
-  
-##  <a name="bkmk_OLE"></a> Analysis Services OLE DB Provider  
- Analysis Services OLE DB Provider is the native provider for Analysis Services database connections. MSOLAP is used indirectly by both ADOMD.NET and AMO, delegating connection requests to the data provider. You can also call the OLE DB provider directly from application code, which you might do if solution requirements preclude the use of a managed API.  
-  
- The Analysis Services OLE DB provider is installed automatically by SQL Server Setup, Excel, and other applications that are frequently used to access Analysis Services databases. You can also install it manually by downloading it from the download center. By default, the provider can be found in the \Program Files\Microsoft Analysis Services folder. The provider must be installed on any workstation used to access Analysis Services data.  
-  
- MSOLAP130.dll is the version of the Analysis Services OLE DB provider that ships in [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]. Other recent previous versions include MSOLAP110.dll (for SQL Server 2008 and 2008 R2) and MSOLAP90.dll (for SQL Server 2005).  
-  
- OLE DB providers are often specified in connection strings. An Analysis Services connection string uses a different nomenclature to refer to the OLE DB provider: MSOLAP.\<version>.dll  
-  
- MSOLAP.5.dll is the current Analysis Services OLE DB provider installed with Excel 2013. Previous versions, such as MSOLAP.4.dll or MSOLAP.3.dll, are often found on workstations running older versions of Excel. Some Analysis Services features, such as the [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] add-in, require specific versions of the OLE DB provider. See [Connection String Properties &#40;Analysis Services&#41;](../../analysis-services/instances/connection-string-properties-analysis-services.md) for more information.  
-  
-##  <a name="bkmk_ADOMD"></a> ADOMD.NET  
- ADOMD.NET is a managed data provider used for querying Analysis Services data. Excel uses ADOMD.NET when connecting to a specific Analysis Services cube. The connection string you see in Excel is for an ADOMD.NET connection.  
-  
- ADOMD.NET is installed by SQL Server Setup and used by SQL Server client applications to connect to Analysis Services. Office installs this library to support data connections from Excel. As with other data providers included in SQL Server, you can redistribute ADOMD.NET if you are using the library in custom code. You can also download and install it manually to get the newer version (see [How to determine the version of the Analysis Services data providers](#bkmk_LibUpdate) in this topic).  
-  
- To check file version information, look for ADOMD.NET in the global assembly cache, where it is listed as `Microsoft.AnalysisServices.AdomdClient`.  
-  
- When connecting to a database, the connection string properties for all three libraries are largely the same. Almost any connection string you define for ADOMD.NET (<xref:Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectionString%2A>) will also work for AMO and the Analysis Services OLE DB provider. See [Connection String Properties &#40;Analysis Services&#41;](../../analysis-services/instances/connection-string-properties-analysis-services.md) for more information.  
-  
- For more information about connecting programmatically, see [Establishing Connections in ADOMD.NET](../../analysis-services/multidimensional-models-adomd-net-client/connections-in-adomd-net.md).  
-  
-##  <a name="blkmk_AMO"></a> AMO  
- AMO is a managed data provider used for server administration and data definition. For example, SQL Server Management Studio uses AMO to connect to Analysis Services.  
-  
- AMO is installed by SQL Server Setup and used by SQL Server client applications to connect to Analysis Services. You can also download and install it manually when using AMO in custom code (see [How to determine the version of the Analysis Services data providers](#bkmk_LibUpdate) in this topic). AMO can be found in the global assembly cache, as `Microsoft.AnalysisServices`.  
-  
- A connection using AMO is typically minimal, consisting of “data source=\<servername>”. After a connection is established, you use the API to work with database collections and major objects. Both SSDT and SSMS use AMO to connect to an Analysis Services instance.  
-  
- For more information about connecting programmatically, see [Programming AMO Fundamental Objects](../../analysis-services/multidimensional-models/analysis-management-objects/programming-amo-fundamental-objects.md).  
-  
-## See Also  
+## See also  
  [Connect to Analysis Services](../../analysis-services/instances/connect-to-analysis-services.md)  
   
   
diff --git a/docs/analysis-services/multidimensional-models/supported-data-sources-ssas-multidimensional.md b/docs/analysis-services/multidimensional-models/supported-data-sources-ssas-multidimensional.md
@@ -40,7 +40,7 @@ ms.workload: "On Demand"
 |-|-|-|-|  
 |Source|Versions|File type|Providers*|  
 |Access databases|Microsoft Access  2010, 2013, 2016|.accdb or .mdb|Microsoft Jet 4.0 OLE DB provider|  
-|SQL Server relational databases*|Microsoft SQL Server 2008, 2008 R2, 2012, 2014, 2016, [!INCLUDE[ssSDSFull](../../includes/sssdsfull-md.md)] , Microsoft Analytics Platform System (APS)<br /><br /> <br /><br /> Note: For more information about [!INCLUDE[ssSDS](../../includes/sssds-md.md)] on [Azure.com](http://go.microsoft.com/fwlink/?LinkID=157856).<br /><br /> Note: Analytics Platform System (APS) was formerly known as SQL Server Parallel Datawarehouse (PDW). Originally, connecting to PDW from Analysis Services required a special data provider. This provider was replaced in SQL Server 2012. Starting in SQL Server 2012, the SQL Server native client is used for connections to PDW/APS. For more information about APS, see the web site [Microsoft Analytics Platform System](http://www.microsoft.com/en-us/server-cloud/products/analytics-platform-system/resources.aspx).|(not applicable)|OLE DB Provider for SQL Server<br /><br /> SQL Server Native Client OLE DB Provider<br /><br /> SQL Server Native 11.0 Client OLE DB Provider<br /><br /> .NET Framework Data Provider for SQL Client|  
+|SQL Server relational databases*|Microsoft SQL Server 2008, 2008 R2, 2012, 2014, 2016, [!INCLUDE[ssSDSFull](../../includes/sssdsfull-md.md)], Azure SQL Data Warehouse, Microsoft Analytics Platform System (APS)<br /><br /> <br /><br /> Note: For more information about [!INCLUDE[ssSDS](../../includes/sssds-md.md)] on [Azure.com](http://go.microsoft.com/fwlink/?LinkID=157856).<br /><br /> Note: Analytics Platform System (APS) was formerly known as SQL Server Parallel Data Warehouse (PDW). Originally, connecting to PDW from Analysis Services required a special data provider. This provider was replaced in SQL Server 2012. Starting in SQL Server 2012, the SQL Server native client is used for connections to PDW/APS. For more information about APS, see the web site [Microsoft Analytics Platform System](http://www.microsoft.com/en-us/server-cloud/products/analytics-platform-system/resources.aspx).|(not applicable)|OLE DB Provider for SQL Server<br /><br /> SQL Server Native Client OLE DB Provider<br /><br /> SQL Server Native 11.0 Client OLE DB Provider<br /><br /> .NET Framework Data Provider for SQL Client|  
 |Oracle relational databases|Oracle 9i, 10g, 11g, 12g|(not applicable)|Oracle OLE DB Provider<br /><br /> .NET Framework Data Provider for Oracle Client<br /><br /> .NET Framework Data Provider for SQL Server<br /><br /> OraOLEDB<br /><br /> MSDASQL|  
 |Teradata relational databases|Teradata V2R6, V12|(not applicable)|TDOLEDB OLE DB provider<br /><br /> .Net Data Provider for Teradata|  
 |Informix relational databases|V11.10|(not applicable)|Informix OLE DB provider|  
diff --git a/docs/database-engine/install-windows/configure-sql-server-on-a-server-core-installation.md b/docs/database-engine/install-windows/configure-sql-server-on-a-server-core-installation.md
@@ -112,7 +112,7 @@ These steps are meant to be performed on a PC running the client edition of Wind
   
 7. Select the **AlwaysOn High Availability** tab.  
   
-8. Verify that Windows failover cluster name field contains the name of the local failover cluster node. If this field is blank, this server instance currently does not support AlwaysOn Availability Groups. Either the local computer is not a cluster node, the WSFC cluster has been shut down, or this edition of [!INCLUDE[ssNoVersion](../../includes/ssNoVersion-md.md)] that does not support AlwaysOn Availability Groups.  
+8. Verify that Windows failover cluster name field contains the name of the local failover cluster node. If this field is blank, this server instance currently does not support AlwaysOn Availability Groups. Either the local computer is not a cluster node, the WSFC cluster has been shut down, or this edition of [!INCLUDE[ssNoVersion](../../includes/ssNoVersion-md.md)] does not support AlwaysOn Availability Groups.  
   
 9. Select the Enable AlwaysOn Availability Groups check box, and click OK.  
   
diff --git a/docs/integration-services/lift-shift/ssis-azure-connect-with-windows-auth.md b/docs/integration-services/lift-shift/ssis-azure-connect-with-windows-auth.md
@@ -76,6 +76,12 @@ To check whether you can connect to an on-premises SQL Server, do the following
 
 3.  From SSMS, check whether you can connect to the on-premises SQL Server that you want to use.
 
+### Prerequisites
+To connect to an on-premises SQL Server from a package running on Azure, you have to enable the following prerequisites:
+
+1.  Enable remote connections on the on-premises SQL Server.
+2.  Allow access through the Windows firewall. For more info, see [Configure the Windows Firewall to Allow SQL Server Access](https://docs.microsoft.com/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access).
+
 ## Connect to an on-premises file share
 To check whether you can connect to an on-premises file share, do the following things:
 
diff --git a/docs/linux/sql-server-linux-release-notes.md b/docs/linux/sql-server-linux-release-notes.md
@@ -143,7 +143,7 @@ The following features and services are not available on Linux at this time. The
 
 ### Known issues
 
-The following sections describe known issues with the Genera Availability (GA) release of SQL Server 2017 on Linux.
+The following sections describe known issues with the General Availability (GA) release of SQL Server 2017 on Linux.
 
 #### General
 
diff --git a/docs/relational-databases/backup-restore/back-up-to-a-mirrored-media-set-transact-sql.md b/docs/relational-databases/backup-restore/back-up-to-a-mirrored-media-set-transact-sql.md
@@ -21,7 +21,7 @@ ms.workload: "Inactive"
 ---
 # Back Up to a Mirrored Media Set (Transact-SQL)
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
-  This topic describes how to use the [!INCLUDE[tsql](../../includes/tsql-md.md)][BACKUP](../../t-sql/statements/backup-transact-sql.md) statement to specify a mirrored media set when backing up a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. In your BACKUP statement, specify the first mirror in the TO clause. Then, specify each mirror in its own MIRROR TO clause. The TO and MIRROR TO clauses must specify the same number and type of backup devices.  
+  This topic describes how to use the [!INCLUDE[tsql](../../includes/tsql-md.md)] [BACKUP](../../t-sql/statements/backup-transact-sql.md) statement to specify a mirrored media set when backing up a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. In your BACKUP statement, specify the first mirror in the TO clause. Then, specify each mirror in its own MIRROR TO clause. The TO and MIRROR TO clauses must specify the same number and type of backup devices.  
   
 ## Example  
  The following example creates the mirrored media set illustrated in the previous illustration and backs up the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] database to both mirrors.  
diff --git a/docs/t-sql/language-elements/save-transaction-transact-sql.md b/docs/t-sql/language-elements/save-transaction-transact-sql.md
@@ -51,7 +51,7 @@ SAVE { TRAN | TRANSACTION } { savepoint_name | @savepoint_variable }
   
 ## Arguments  
  *savepoint_name*  
- Is the name assigned to the savepoint. Savepoint names must conform to the rules for identifiers, but are limited to 32 characters. *transaction_name* is always case sensitive, even when the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is not case sensitive.  
+ Is the name assigned to the savepoint. Savepoint names must conform to the rules for identifiers, but are limited to 32 characters. *savepoint_name* is always case sensitive, even when the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is not case sensitive.  
   
  @*savepoint_variable*  
  Is the name of a user-defined variable containing a valid savepoint name. The variable must be declared with a **char**, **varchar**, **nchar**, or **nvarchar** data type. More than 32 characters can be passed to the variable, but only the first 32 characters will be used.  
diff --git a/docs/t-sql/queries/select-having-transact-sql.md b/docs/t-sql/queries/select-having-transact-sql.md
@@ -1,7 +1,7 @@
 ---
 title: "HAVING (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "08/09/2017"
+ms.date: "11/28/2017"
 ms.prod: "sql-non-specified"
 ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw"
 ms.service: ""
@@ -32,7 +32,7 @@ ms.workload: "Active"
 # SELECT - HAVING (Transact-SQL)
 [!INCLUDE[tsql-appliesto-ss2008-all-md](../../includes/tsql-appliesto-ss2008-all-md.md)]
 
-  Specifies a search condition for a group or an aggregate. HAVING can be used only with the SELECT statement. HAVING is typically used in a GROUP BY clause. When GROUP BY is not used, HAVING behaves like a WHERE clause.  
+  Specifies a search condition for a group or an aggregate. HAVING can be used only with the SELECT statement. HAVING is typically used with a GROUP BY clause. When GROUP BY is not used, there is an implicit single, aggregated group.   
   
  ![Topic link icon](../../database-engine/configure-windows/media/topic-link.gif "Topic link icon") [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
   
@@ -44,7 +44,7 @@ ms.workload: "Active"
   
 ## Arguments  
 \<search_condition>
- Specifies the search condition for the group or the aggregate to meet.  
+ Specifies one or more predicates for groups and/or aggregates to meet. For more information about search conditions and predicates, see [Search Condition &#40;Transact-SQL&#41;](../../t-sql/queries/search-condition-transact-sql.md).  
   
  The **text**, **image**, and **ntext** data types cannot be used in a HAVING clause.  
   
diff --git a/docs/t-sql/statements/alter-partition-scheme-transact-sql.md b/docs/t-sql/statements/alter-partition-scheme-transact-sql.md
diff --git a/docs/t-sql/statements/create-partition-scheme-transact-sql.md b/docs/t-sql/statements/create-partition-scheme-transact-sql.md
