Catalog Navigation - Add the possibility to filter before query the DB2 catalog
Opened this issue · 8 comments
There are a lot of objects in our production system. It would be better to have the possibility to set filters before I click on "Databases", "Tables" and so on in the catalog navigation feature.
When I try to list the tables in our production system it takes a lot of time (1 minute and 4 seconds) until I see a result.
Even on our development system useres are hitting ASUTIME limit when they try to list the tables.
In my point of view this issue should get a high priority. Thats one of the main use cases for catalog navigation and it is not usable on big DB2 systems.
Hi Marty, Thanks for the enhancement request. As this request has been raised by many of our customers, we are actively looking into this feature and designing it.
Hi @Marty850, we currently limit default catalog navigation objects to first 500 objects. Is it with this limit that it takes 1 minute 4 seconds or is it with the limit set to -1 (retrieve all objects) that it takes that long?
Hi @b-tsao ,
I've the ASUTIME limit when I try to list the tables on the Catalogue whatever the number of objects to display (500 or -1)
We have a big DB2 systems.
To filter by a object on the catalogue before the search begins, for example if i could click right to bring up a context menu and enter a filter on the DB2 schema, and the catalog shows me tables from that schema only. It'will be perfect !
The answer of Vanessa also fits for our systems. I checkt the SQL statement that was issued by the extension. It ends with "FETCH FIRST 500 ROWS ONLY" and still hits the asutime limit.
Your SQL filters by "WHERE NAME LIKE '%' and that leads into a bad access path with tablespace scans. We need the possibility to set filters first.
Thank you for the feedback @VanessaLimsavanh and @Marty850, we will investigate this.
FYI, I have the exact same need in my company, Even with a limit at 50, the request never ends (especially on Tables)
It would be great to be able to add this default filter to the connection object itself. I could see a use case where I create multiple copies of the same connection with different default filters: this connection is "System 1, Application A", and that connection is "System 1, Application B", and so forth.