DBeaver
Analyzing query for proposals takes a long time #37612
-
DescriptionI am using Dbeaver Community Edition version 25.0.0.202503021833 and connect to Snowflake with Snowflake jdbc version 3.20.0. I have noticed that the Analyze Query for proposals task is running and it seems to get stuck at 50%. I have had to cancel that process as it is competing with my normal queries. I tried to find way to turn off this feature but has not been successful. Can you let me know what the issue might be and whether or not I can turn off this feature? Thanks
DBeaver VersionCommunity Edition 25.0.0.202503021833 Operating SystemWindows 10 Database and driverSnowflake jdbc 3.20.0 Steps to reproduceAnalyzing query for proposals started running by itself but did not get pass 50%. I cancelled it but it kept running again and again. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
If you don't want completion autoactivation, you can turn it off by unchecking corresponding checkbox in the connection settings or for all connections in the global preferences. Then you can use Ctrl+Space hotkey to call for it explicitly when needed.
If you want to use completion, you can try to wait for it to load data until the proposals list appear for the first time. At this point the cache should be populated and further completion requests should be served much faster and without extra queries. Until you reconnect of course. PS Also it would be nice to know your definition of "long time": is it 15 seconds? 5 minutes? two hours? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I appreciate the quick response. Found that option and also the background queries finished. |
Beta Was this translation helpful? Give feedback.
If you don't want completion autoactivation, you can turn it off by unchecking corresponding checkbox in the connection settings or for all connections in the global preferences. Then you can use Ctrl+Space hotkey to call for it explicitly when needed.
If you want to use completion, you can try to wait for it to load data until the proposals list appear for the first time. At this point the cache should be populated and further completion requests should be served much faster and without extra queries. Until you reconnect of course.
If you are always canceling it, you are basically just preventing it not only from preparing proposals, but also from populating schema cache. So the next ti…