Is it possible to limit the number of database schemas that are visible/accessible in a Qlik ODBC connection?

[sravanthiG]

Is it possible to limit the number of database schemas that are visible/accessible in a Qlik ODBC connection?

For example – Would it be possible to build one connection that points at “db_test” and another connection that only shows “db_test1”?  can this be achieved by creating the data connection with single ID?

[SushilKumar]

Hello @sravanthiG 

Thanks for reaching out to Qlik via Qlik Community Support page. We would like to have more info regarding which Source endpoint you are using . Although Qlik require certain privlages to Access the metadata of the Schema table/user table so that you can access all the table except System tables. 

in null shell there is no way to refrain Qlik to see the Schema tables. However you can control tables selection via putting correct schema name or Find pattern accordingly.

As pattern matching works like function and in your case db_test is command between (db_test and db_test1)

If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer.

Regards,

Sushil Kumar

[SachinB]

Hello @sravanthiG ,

Thanks for reaching out Qlik community forum.

Practically saying yes, it is possible to build separate ODBC connections in Qlik that point to different schemas (like "db_test" and "db_test1") within the same database while using a single database user ID. This approach leverages the connection string parameters and SQL commands to limit schema visibility per connection.

Some ODBC drivers allow specifying the default schema in the connection string. Check your database and ODBC driver's documentation to see if this is supported.

Connection for db_test:

Connection string: Driver={PostgreSQL};Server=your_server;Port=5432;Database=your_database;Uid=your_user;Pwd=your_password;SearchPath=db_test;

Connection for db_test1:Connection string: Driver={PostgreSQL};Server=your_server;Port=5432;Database=your_database;Uid=your_user;Pwd=your_password;SearchPath=db_test1;

Hope this helps.

Regards,
Sachin B