Skip to content

Commit a29ee57

Browse files
megvanhuygenmegvanhuygen
authored
Merge pull request #96972 from Minewiskan/aas-datasource
Aas datasource
2 parents 8e2c48b + 1883cf5 commit a29ee57

File tree

4 files changed

+78
-73
lines changed

4 files changed

+78
-73
lines changed

‎articles/analysis-services/analysis-services-datasource.md

Lines changed: 78 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -4,97 +4,102 @@ description: Describes data sources and connectors supported for tabular 1200 an
44
author: minewiskan
55
ms.service: azure-analysis-services
66
ms.topic: conceptual
7-
ms.date: 11/14/2019
7+
ms.date: 12/02/2019
88
ms.author: owend
99
ms.reviewer: minewiskan
1010

1111
---
1212
# Data sources supported in Azure Analysis Services
1313

14-
Data sources and connectors shown in Get Data or Import Wizard in Visual Studio are shown for both Azure Analysis Services and SQL Server Analysis Services. However, not all data sources and connectors shown are supported in Azure Analysis Services. The types of data sources you can connect to depend on many factors such as model compatibility level, available data connectors, authentication type, providers, and On-premises data gateway support.
14+
Data sources and connectors shown in Get Data or Table Import Wizard in Visual Studio with Analysis Services projects are shown for both Azure Analysis Services and SQL Server Analysis Services. However, not all data sources and connectors shown are supported in Azure Analysis Services. The types of data sources you can connect to depend on many factors such as model compatibility level, available data connectors, authentication type, and On-premises data gateway support. The following tables describe supported data sources for Azure Analysis Services.
1515

1616
## Azure data sources
1717

18-
|Data source |In-memory |DirectQuery |
19-
|---------|---------|---------|
20-
|Azure SQL Database<sup>[2](#azsqlmanaged)</sup> | Yes | Yes |
21-
|Azure SQL Data Warehouse | Yes | Yes |
22-
|Azure Blob Storage<sup>[1](#tab1400a)</sup> | Yes | No |
23-
|Azure Table Storage<sup>[1](#tab1400a)</sup> | Yes | No |
24-
|Azure Cosmos DB<sup>[1](#tab1400a)</sup> | Yes | No |
25-
|Azure Data Lake Store (Gen1)<sup>[1](#tab1400a)</sup>, <sup>[4](#gen2)</sup> | Yes | No |
26-
|Azure HDInsight HDFS<sup>[1](#tab1400a)</sup> | Yes | No |
27-
|Azure HDInsight Spark<sup>[1](#tab1400a)</sup>, <sup>[3](#databricks)</sup> | Yes | No |
18+
|Data source |In-memory |DirectQuery |Notes |
19+
|---------|---------|---------|---------|
20+
|Azure SQL Database | Yes | Yes |<sup>[2](#azprovider)</sup>, <sup>[3](#azsqlmanaged)</sup>|
21+
|Azure SQL Data Warehouse | Yes | Yes |<sup>[2](#azprovider)</sup>|
22+
|Azure Blob Storage | Yes | No | <sup>[1](#tab1400a)</sup> |
23+
|Azure Table Storage | Yes | No | <sup>[1](#tab1400a)</sup>|
24+
|Azure Cosmos DB | Yes | No |<sup>[1](#tab1400a)</sup> |
25+
|Azure Data Lake Store Gen1 | Yes | No |<sup>[1](#tab1400a)</sup> |
26+
|Azure Data Lake Store Gen2 | Yes | No |<sup>[1](#tab1400a)</sup>, <sup>[5](#gen2)</sup>|
27+
|Azure HDInsight HDFS | Yes | No |<sup>[1](#tab1400a)</sup> |
28+
|Azure HDInsight Spark | Yes | No |<sup>[1](#tab1400a)</sup>, <sup>[4](#databricks)</sup>|
2829
||||
2930

30-
<a name="tab1400a">1</a> - Tabular 1400 and higher models only.
31-
<a name="azsqlmanaged">2</a> - Azure SQL Database Managed Instance is supported. Because managed instance runs within Azure VNet with a private IP address, public endpoint must be enabled on the instance. If not enabled, an on-premises Data Gateway is required.
32-
<a name="databricks">3</a> - Azure Databricks using the Spark connector is currently not supported.
33-
<a name="gen2">4</a> - ADLS Gen2 connector is currently not supported, however, Blob Storage connector can be used with an ADLS Gen2 data source.
31+
**Notes:**
32+
<a name="tab1400a">1</a> - Tabular 1400 and higher models only.
33+
<a name="azprovider">2</a> - When specified as a *provider* data source in tabular 1200 and higher models, both in-memory and DirectQuery models require Microsoft OLE DB Driver for SQL Server MSOLEDBSQL (recommended), SQL Server Native Client 11.0, or .NET Framework Data Provider for SQL Server.
34+
<a name="azsqlmanaged">3</a> - Azure SQL Database Managed Instance is supported. Because managed instance runs within Azure VNet with a private IP address, public endpoint must be enabled on the instance. If not enabled, an [On-premises data gateway](analysis-services-gateway.md) is required.
35+
<a name="databricks">4</a> - Azure Databricks using the Spark connector is currently not supported.
36+
<a name="gen2">5</a> - ADLS Gen2 connector is currently not supported, however, Azure Blob Storage connector can be used with an ADLS Gen2 data source.
3437

38+
## Other data sources
3539

36-
**Provider**
37-
In-memory and DirectQuery models connecting to Azure data sources use .NET Framework Data Provider for SQL Server.
40+
|Data source | In-memory | DirectQuery |Notes |
41+
| --- | --- | --- | --- |
42+
|Access Database | Yes | No | |
43+
|Active Directory | Yes | No | <sup>[6](#tab1400b)</sup> |
44+
|Analysis Services | Yes | No | |
45+
|Analytics Platform System | Yes | No | |
46+
|CSV file |Yes | No | |
47+
|Dynamics 365 | Yes | No | <sup>[6](#tab1400b)</sup> |
48+
|Excel workbook | Yes | No | |
49+
|Exchange | Yes | No | <sup>[6](#tab1400b)</sup> |
50+
|Folder |Yes | No | <sup>[6](#tab1400b)</sup> |
51+
|IBM Informix |Yes | No | |
52+
|JSON document | Yes | No | <sup>[6](#tab1400b)</sup> |
53+
|Lines from binary | Yes | No | <sup>[6](#tab1400b)</sup> |
54+
|MySQL Database | Yes | No | |
55+
|OData Feed | Yes | No | <sup>[6](#tab1400b)</sup> |
56+
|ODBC query | Yes | No | |
57+
|OLE DB | Yes | No | |
58+
|Oracle | Yes |Yes | <sup>[9](#oracle)</sup> |
59+
|PostgreSQL Database | Yes | No | <sup>[6](#tab1400b)</sup> |
60+
|Salesforce Objects| Yes | No | <sup>[6](#tab1400b)</sup> |
61+
|Salesforce Reports |Yes | No | <sup>[6](#tab1400b)</sup> |
62+
|SAP HANA | Yes | No | |
63+
|SAP Business Warehouse | Yes | No | <sup>[6](#tab1400b)</sup> |
64+
|SharePoint List | Yes | No | <sup>[6](#tab1400b)</sup>, <sup>[11](#filesSP)</sup> |
65+
|SQL Server |Yes | Yes | <sup>[7](#sqlim)</sup>, <sup>[8](#instgw)</sup> |
66+
|SQL Server Data Warehouse |Yes | Yes | <sup>[7](#sqlim)</sup>, <sup>[8](#instgw)</sup> |
67+
|Sybase Database | Yes | No | |
68+
|Teradata | Yes | Yes | <sup>[10](#teradata)</sup> |
69+
|TXT file |Yes | No | |
70+
|XML table | Yes | No | <sup>[6](#tab1400b)</sup> |
71+
| | | |
3872

39-
## Other data sources
73+
**Notes:**
74+
<a name="tab1400b">6</a> - Tabular 1400 and higher models only.
75+
<a name="sqlim">7</a> - When specified as a *provider* data source in tabular 1200 and higher models, specify Microsoft OLE DB Driver for SQL Server MSOLEDBSQL (recommended), SQL Server Native Client 11.0, or .NET Framework Data Provider for SQL Server.
76+
<a name="instgw">8</a> - If specifying MSOLEDBSQL as the data provider, it may be necessary to download and install the [Microsoft OLE DB Driver for SQL Server](https://docs.microsoft.com/sql/connect/oledb/oledb-driver-for-sql-server) on the same computer as the On-premises data gateway.
77+
<a name="oracle">9</a> - For tabular 1200 models, or as a *provider* data source in tabular 1400+ models, specify Oracle Data Provider for .NET.
78+
<a name="teradata">10</a> - For tabular 1200 models, or as a *provider* data source in tabular 1400+ models, specify Teradata Data Provider for .NET.
79+
<a name="filesSP">11</a> - Files in on-premises SharePoint are not supported.
4080

41-
Connecting to on-premises data sources from an Azure Analysis Services server require an On-premises gateway. When using a gateway, 64-bit providers are required.
81+
Connecting to on-premises data sources from an Azure Analysis Services server require an [On-premises gateway](analysis-services-gateway.md). When using a gateway, 64-bit providers are required.
4282

43-
### In-memory and DirectQuery
83+
## Understanding providers
4484

45-
|Data source | In-memory provider | DirectQuery provider |
46-
| --- | --- | --- |
47-
| SQL Server |Microsoft OLE DB Driver for SQL Server MSOLEDBSQL (recommended), SQL Server Native Client 11.0, .NET Framework Data Provider for SQL Server | .NET Framework Data Provider for SQL Server |
48-
| SQL Server Data Warehouse |Microsoft OLE DB Driver for SQL Server MSOLEDBSQL (recommended), SQL Server Native Client 11.0, .NET Framework Data Provider for SQL Server | .NET Framework Data Provider for SQL Server |
49-
| Oracle | OLE DB Provider for Oracle, Oracle Data Provider for .NET |Oracle Data Provider for .NET |
50-
| Teradata |OLE DB Provider for Teradata, Teradata Data Provider for .NET |Teradata Data Provider for .NET |
51-
| | | |
85+
When creating tabular 1400 and higher model projects in Visual Studio, by default you do not specify a data provider when connecting to a data source by using **Get Data**. Tabular 1400 and higher models use [Power Query](/power-query/power-query-what-is-power-query.md) connectors to manage connections, data queries, and mashups between the data source and Analysis Services. These are sometimes referred to as *structured* data source connections in that connection property settings are set for you. You can, however, enable legacy data sources. When enabled, you can use **Table Import Wizard** to connect to certain data sources traditionally supported in tabular 1200 and lower models as *legacy*, or *provider* data sources. When specified as a provider data source, you can specify a particular data provider and other advanced connection properties. For example, you can connect to an on-premises SQL Server Data Warehouse or even an Azure SQL Database as a legacy data source. You can then select the OLE DB Driver for SQL Server MSOLEDBSQL data provider. In this case, selecting an OLE DB data provider may provide improved performance over the Power Query connector.
86+
87+
When using the Table Import Wizard in Visual Studio, connections to any data source require a data provider. A default data provider is selected for you. You can change the data provider if needed. The type of provider you choose can depend on performance, whether or not the model is using in-memory storage or DirectQuery, and which Analysis Services platform you deploy your model to.
88+
89+
### Specify provider data sources in tabular 1400 and higher model projects
90+
91+
To enable provider data sources, in Visual Studio, click **Tools** > **Options** > **Analysis Services Tabular** > **Data Import**, select **Enable legacy data sources**.
92+
93+
![Enable legacy data sources](media/analysis-services-datasource/aas-enable-legacy-datasources.png)
94+
95+
With legacy data sources enabled, in **Tabular Model Explorer**, right-click **Data Sources** > **Import From Data Source (Legacy)**.
96+
97+
![Legacy data sources in Tabular Model Explorer](media/analysis-services-datasource/aas-import-legacy-datasources.png)
98+
99+
Just like with tabular 1200 model projects, use **Table Import Wizard** to connect to a data source. On the connect page, click **Advanced**. Specify data provider and other connection settings in **Set Advanced Properties**.
100+
101+
![Legacy data sources Advanced properties](media/analysis-services-datasource/aas-import-legacy-advanced.png)
52102

53-
### In-memory only
54-
55-
|Data source |
56-
|---------|
57-
|Access Database |
58-
|Active Directory<sup>[1](#tab1400b)</sup> |
59-
|Analysis Services |
60-
|Analytics Platform System |
61-
|CSV file |
62-
|Dynamics CRM<sup>[1](#tab1400b)</sup> |
63-
|Excel workbook |
64-
|Exchange<sup>[1](#tab1400b)</sup> |
65-
|Folder<sup>[1](#tab1400b)</sup> |
66-
|IBM Informix<sup>[1](#tab1400b)</sup> (Beta) |
67-
|JSON document<sup>[1](#tab1400b)</sup> |
68-
|Lines from binary<sup>[1](#tab1400b)</sup> |
69-
|MySQL Database |
70-
|OData Feed<sup>[1](#tab1400b)</sup> |
71-
|ODBC query |
72-
|OLE DB |
73-
|PostgreSQL Database<sup>[1](#tab1400b)</sup> |
74-
|Salesforce Objects<sup>[1](#tab1400b)</sup> |
75-
|Salesforce Reports<sup>[1](#tab1400b)</sup> |
76-
|SAP HANA<sup>[1](#tab1400b)</sup> |
77-
|SAP Business Warehouse<sup>[1](#tab1400b)</sup> |
78-
|SharePoint List<sup>[1](#tab1400b)</sup>, <sup>[2](#filesSP)</sup> |
79-
|Sybase Database |
80-
|TXT file |
81-
|XML table<sup>[1](#tab1400b)</sup> |
82-
||
83-
84-
<a name="tab1400b">1</a> - Tabular 1400 and higher models only.
85-
<a name="filesSP">2</a> - Files in on-premises SharePoint are not supported.
86-
87-
## Specifying a different provider
88-
89-
Data models in Azure Analysis Services may require different data providers when connecting to certain data sources. In some cases, tabular models connecting to data sources using native providers such as SQL Server Native Client (SQLNCLI11) may return an error. If using native providers other than MSOLEDBSQL, you may see error message: **The provider 'SQLNCLI11.1' is not registered**. Or, if you have a DirectQuery model connecting to on-premises data sources and you use native providers, you may see error message: **Error creating OLE DB row set. Incorrect syntax near 'LIMIT'**.
90-
91-
When migrating an on-premises SQL Server Analysis Services tabular model to Azure Analysis Services, it may be necessary to change the provider.
92-
93-
**To specify a provider**
94-
95-
1. In Visual Studio > **Tabular Model Explorer** > **Data Sources**, right-click a data source connection, and then click **Edit Data Source**.
96-
2. In **Edit Connection**, click **Advanced** to open the Advance properties window.
97-
3. In **Set Advanced Properties** > **Providers**, then select the appropriate provider.
98103

99104
## Impersonation
100105
In some cases, it may be necessary to specify a different impersonation account. Impersonation account can be specified in Visual Studio or SSMS.

‎articles/analysis-services/media/analysis-services-datasource/aas-enable-legacy-datasources.png

27.9 KB
Loading

‎articles/analysis-services/media/analysis-services-datasource/aas-import-legacy-advanced.png

30.4 KB
Loading

‎articles/analysis-services/media/analysis-services-datasource/aas-import-legacy-datasources.png

27.8 KB
Loading

0 commit comments

Comments
 (0)