DBeaver Forum

Hi!

I have a little problem. I dunno why but the database (schema, tables) discovery is veeeeery slow.
I press the table expand button, and I wait.... about many-many minutes (!!!)

Any idea? I miss some configuration? (I see the select .... background task is working, so it's doing something...)

Thanks

It's quite a strange behaviour. We've tested Oracle plugin in many different environments and Oracle versions and it worked fine.
Moreover - DBeaver doesn't perform any database roundtrips on table expand action.

Could you open QueryManager view and check what query exactly is executed at that moment?

Thanks!

I not run any query. I simply want to browse the database tables... (the query executed automatically).

DBeaver logs every query it executes.
You may configure it on page Preferences -> Database Configuration -> Query Manager.
Check all query types and object types.
Each time DBeaver reads any metadata you will see it in the query manager view.

Could you check which query executes so long?

Thanks a lot!

Hi!

This query is NOT listed in the query manager. (When I expand the "Tables" level in the database).
I attached a screenshot with the SQL (shown on the background tasks):

Veeeeery long running query

2011-11-18_002.png (10.52 KiB) Viewed 30775 times

This step (open the tables level on the tree) in 1.3 is work very well and fast...

Thanks
b0c1

Oh. Thank you for detailed report!

Some Oracle databases contains a lot of metadata and in some Oracle versions metadata reading may be not so fast as in others.
I can't reproduce this problem in my environments but I think I know the cause of this problem.
We'll simplify tables/views metadata reading, fix will be available in next EA version (will be available at Nov 20-21).

Thanks!

Thanks, we are waiting the next version...

b0c1

EA version is available here - .
Note - it contains some new features (db tools, native clients management and some other) which are partially implemented at he moment. I'd suggest not to use them All existing features should be stable.

Please check Oracle metadata reading performance in this version.

Thanks!

Oracle metadata reading was fixed in 1.4.5