The CONNECT statement is used to define Qlik Sense access to a general database through the OLE DB/ODBC interface. For ODBC, the data source first needs to be specified using the ODBC administrator.
ODBC CONNECT TO connect-string
OLEDB CONNECT TO connect-string
CUSTOM CONNECT TO connect-string
LIB CONNECT TO connection
|connect-string||connect-string ::= datasourcename
The connection string is the data source name and an optional list of one or more connection specification items. If the data source name contains blanks, or if any connection specification items are listed, the connection string must be enclosed by quotation marks.
datasourcename must be a defined ODBC data source or a string that defines an OLE DB provider.
conn-spec-item ::=DBQ=database_specifier |DriverID=driver_specifier |UID=userid |PWD=password
The possible connection specification items may differ between different databases. For some databases, also other items than the above are possible. For OLE DB, some of the connection specific items are mandatory and not optional.
The name of a data connection stored in the data load editor.
The syntax for a data connection in a space is (space_name):(connection_name).
You can specify a data connection in the current space with the syntax :(connection_name).
If no space is specified, it will look for the connection in the space the app is in. For more information on syntax for spaces, see Connect to data sources in the data load editor
If the ODBC is placed before CONNECT, the ODBC interface will be used; else, OLE DB will be used.
Using LIB CONNECT TO connects to a database using a stored data connection that was created in the data load editor.
ODBC CONNECT TO 'Sales
The data source defined through this statement is used by subsequent Select (SQL) statements, until a new CONNECT statement is made.
LIB CONNECT TO 'DataConnection';
The script looks for a connection named DataConnection in the user running the script's personal space.
LIB CONNECT TO 'Sales:DataConnection'
The script looks for a connection named DataConnection in a space called Sales.
This statement is used the same way as the CONNECT statement, but forces a 64-bit system to use a 32-bit ODBC/OLE DB provider. Not applicable for custom connect.
This statement is used the same way as the as the CONNECT statement, but forces use of a 64-bit provider. Not applicable for custom connect.