Connection String Parameters for Quandl
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider.
|The API key obtained when you register a Quandl account.
|Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider .
|The connection string for the cache database. This property is always used in conjunction with CacheProvider . Setting both properties will override the value set for CacheLocation for caching data.
|Specifies the path to the cache when caching to a file.
|This property determines whether or not to cache the table metadata to a file store.
|The name of the provider to be used to cache data.
|The tolerance for stale data in the cache specified in seconds when using AutoCache .
|The maximum lifetime of a connection in seconds. Once the time has elapsed, the connection object is disposed.
|The code identifying the database.
|A password used to authenticate to a proxy-based firewall.
|The TCP port for a proxy-based firewall.
|The name or IP address of a proxy-based firewall.
|The protocol used by a proxy-based firewall.
|The user name to use to authenticate with a proxy-based firewall.
|A path to the directory that contains the schema files defining tables, views, and stored procedures.
|A path to the log file.
|A string specifying the maximum file count of log files. When the limit is hit, a new log is created in the same folder with the date and time appended to the end and the oldest log file will be deleted.
|A string specifying the maximum size in bytes for a log file (for example, 10 MB). When the limit is hit, a new log is created in the same folder with the date and time appended to the end.
|Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time.
|Use offline mode to get the data from the cache instead of the live source.
|These hidden properties are used only in specific use cases.
|The allowed idle time for a connection before it is closed.
|The maximum connections in the pool.
|The minimum number of connections in the pool.
|The max seconds to wait for an available connection.
|The authentication type to use to authenticate to the ProxyServer proxy.
|This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings.
|A semicolon separated list of hosts or IPs that are exempt from connecting through the ProxyServer .
|A password to be used to authenticate to the ProxyServer proxy.
|The TCP port the ProxyServer proxy is running on.
|The hostname or IP address of a proxy to route HTTP traffic through.
|The SSL type to use when connecting to the ProxyServer proxy.
|A user name to be used to authenticate to the ProxyServer proxy.
|This property indicates whether or not to include pseudo columns as columns to the table.
|Set this property to control the number of rows scanned to determine column data types.
|The runtime key used for licensing.
|The certificate to be accepted from the server when connecting using TLS/SSL.
|This property enhances SQL functionality beyond what can be supported through the API directly, by enabling in-memory client-side processing.
|This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC.
|The value in seconds until the timeout error is thrown, canceling the operation.
|This property enables connection pooling.
|Boolean determining if simple names should be used for tables and columns.
|The verbosity level that determines the amount of detail included in the log file.
|Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC.