Skip to main content

Connecting to a Qlik Big Data Index data model with the Qlik Selection Language

The connection definition for Qlik Big Data Index is similar to the Qlik syntax used to connect to other data sources. It uses a single connection definition followed by one of the load statement options.

The Qlik CONNECT TO statements have the structure like the following for ODBC and OLEDB:.

Syntax:  

ODBC CONNECT TO Connection String;

OLEDB CONNECT TO Connection String;

 

For Qlik Big Data Index, the statement syntax is.

Syntax:  

BDI CONNECT TO 'DataModelName QSLManagerServerAddress:Port';

IMPORT LIVE 'DataModelName';

Qlik Sense on-demand apps can extract data from the Qlik Big Data Index. The process for creating on-demand apps is basically the same as when you use other data sources except that you use the Qlik Selection Language (QSL) to connect to a Qlik Big Data Index data model.

Information noteIMPORT LIVE must be the last statement of the load script. Script code after IMPORT LIVE will not be executed.

Example:  

BDI CONNECT TO 'banking 20.100.0.101:55000';

IMPORT LIVE 'banking';

A connection with data import statements uses selection statements.

Syntax:  

BDI CONNECT TO 'DataModelName QSLManagerServerAddress:Port';

LOAD *;
QSL SELECT <ColumnList> from <Table>;
Information noteNote that the port at the end of the BDI CONNECT statement is the port on which the QSL Manager Service listens and not the port on which the QSL RegEx or Indexing Registry Services are listening. Port 55000 is the default for the QSL Manager Service, but that can be changed.

Predefined data sources for Qlik Big Data Index connections are also supported. The statement for a predefined data source connection is generated by the Data load editor.

Syntax:  

LIB CONNECT TO 'DefinedDataSource';

You can see an example of this statement when you click the Insert connection string icon Ø in the Data load editor.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!