Tableau Desktop can initiate multiple, parallel connections automatically when communicating with a data source. You can specify any and all of the following:
These settings are managed by an xml file named connection-configs.xml which you create and save in the Tableau Desktop folder. The default locations are:
<?xml version='1.0' encoding='utf-8' ?>
<connection-list>
<connection class='sqlserver' dbname='SalesDB' server='SQLserver10'>
<limit max='10'>
</limit>
</connection>
<connection class='mysql' dbname='Inventory' server='MySQL_Public'>
<limit max='10'>
</limit>
</connection>
<connection class='teradata' schema='TravelData' server='TeradataProduction2'>
<limit max='12'>
</limit>
</connection>
<connection class='sqlserver'>
<limit max='4'>
</limit>
</connection>
<connection class='mysql'>
<limit max='6'>
</limit>
</connection>
<connection class='teradata'>
<limit max='10'>
</limit>
</connection>
<connection>
<limit max='8'>
</limit>
</connection>
</connection-list>
A <connection> tag with no information about data source type, server, or database defines the maximum number of queries for all connections not covered by any other, more specific, connection specification. For example:
<connection>
<limit max='8'>
</limit>
</connection>
This value overrides the default parallel query limit, which is 16 for all data sources types except Amazon Redshift (for which the default is 8).
Set Additional Limits
Connection settings in connection-configs.xml can work at different levels of specificity. When establishing a connection, Tableau parses the file from top to bottom, so if there is more than one entry that would apply to a given connection, the entry nearest the top of the file is used.
For this reason, it is also appropriate to order connection specifications from most specific to least specific.
Additional (non-global) limits are set in a <connection-list> section at the top of the connection-configs.xml file.
The parameters you can use in a <connection> tag are:
| Parameter | String |
| class | The data source type. See the “Class Strings” table, below, for the strings to use for all data source types. |
| server | The server computer. |
| dbname | The database name. |
| schema | This setting can be useful with Teradata data sources. |
You can specify parameters in any order and any combination—for example, you could specify a server and a dbname without specifying a class.
Use the following strings to identify data source types in connection-configs.xml.
| Data Source | String |
| Actian Vectorwise | "vectorwise" |
| Amazon EMR | "awshadoophive" |
| Amazon Redshift | “redshift” |
| Aster Database | "asterncluster" |
| Cloudera Hadoop | "hadoophive" |
| Extracts created from cube data sources | Not configurable. |
| DataStax Enterprise | "datastax" |
| EXASolution | "exasolution" |
| Firebird | "firebird" |
| Generic ODBC | "genericodbc" |
| Google Analytics | "google-analytics" |
| Google BigQuery | "bigquery" |
| Hortonworks Hadooop Hive | "hortonworkshadoophive" |
| HP Vertica | “vertica” |
| IBM BigInsights | “bigsql” |
| IBM DB2 | "db2" |
| JavaScript Connector | "jsconnector" |
| MapR Hadoop Hive | "maprhadoophive" |
| MarkLogic | "marklogic" |
| Microsoft Access | "msaccess” |
| Microsoft Analysis Services | "msolap" |
| Microsoft Excel | Not configurable. |
| Microsoft PowerPivot | "powerpivot" |
| Microsoft SQL Server | "sqlserver" |
| MySQL | "mysql" |
| IBM Netezza | "netezza" |
| OData | “odata” |
| Oracle | "oracle" |
| Oracle Essbase | “essbase” |
| ParAccel | "paraccel" |
| Pivotal Greenplum | "greenplum" |
| PostgreSQL | "postgres" |
| Progress OpenEdge | "progressopenedge" |
| SAP HANA | "saphana" |
| SAP Netweaver Business Warehouse | "sapbw" |
| SAP Sybase ASE | "sybasease" |
| SAP Sybase IQ | "sybaseiq" |
| Salesforce | "salesforce" |
| Spark SQL | "spark" |
| Splunk | "splunk" |
| Statistical File | Not configurable. |
| Tableau Data Extract | "dataengine" |
| Teradata | “teradata” |
| Text file | “csv” |
001453728

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.