-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvement - Oracle - Very slow retrieval of foreign keys and references in Table Information Panel #39
Comments
Ah, it is a neverending story about Oracle system schemas reading performance. Could you also check Query Manager to see what metadata queries work so long? |
When you making a select from a table from some schema for the first time DBeaver caches all tables, columns an constraints in that schema. In the progress bar you see it as "binding". It takes time. In case of SYS schema it takes pretty much time. But all consequent queries should work fast. Although 30sec is more than too much. Unless you are working with remote Oracle using slow network. |
Hi Serge, yes, at work we have a remote Oracle server, but I don't suppose our network is so slow... I (hopefully) posted all the metadata queries that DBeaver performs :-( |
I'll add a few metadata loading performance improvements. |
Please check performance in 3.5.3 |
Hi Serge, retrieval time for Foreign Keys has dramatically improved, however DBeaver is still a little slow when retrieving References (on a table it took up to a minute to complete the retrieval query, whether the retrieval of Foreign Keys took less than 5 seconds). |
Same problem in informix. |
Using Oracle 11g, the time needed to retrieve foreign keys and references for a table is far greater than the time required to do the same operation on other databases.
I tried using MySQL and Sybase ASE and the retrieval was matter of seconds. Using Oracle it takes up to 30 seconds and above. Doing the same operation with another tool (i.e. TOAD) on the same table, the operation takes less than 2 seconds.
The text was updated successfully, but these errors were encountered: