I have watched the database logs (~/.cache/JetBrains/DataGrip2020.2/database-log/database.log) and identified that DataGrip spends 12 minutes running SHOW GRANT statements. I'm hoping there might be a solution because I'm pretty working without the benefits of an introspected database schema because the task ultimately never completes before I need to move the next database and inspection starts all over again.
Datagrip jetbrains show time 12hh vs 24hh full#
If you alter a table in any database, it seems to trigger a full re-inspections of everything where it could just re-inspect the one table that was altered. When it queries database users, it does this one user at a time. I'm using a local mysql CLI - so it's not network lag.Īside from DataGrip having very slow execution of queries, it seems to skip obvious optimisations. If I run that same query using the mysql CLI it takes a fraction of second.
Each query it fires can take up to 2 seconds to complete.
If I tail the log to see what DataGrip is doing I can see that it's queries are excessively slow. Having maybe 4 database inspected with 200 tables each can take hours to complete. However, as of a recent version (perhaps 2019.3) DataGrip became excessively slow. I'm having the same issue with excessively slow schema inspections.ĭataGrip has always been a poor performer (in comparison to HeidiSQL which can very rapidly inspect an entire database.) As a result, where our servers may have up to 100 database, I toggle which ones I'm working with so DataGrip only inspects a couple. Using it for the first time with was looking so good, I was so excited to see packages in full detail and not have to be in SQLDeveloper from Oracle.but I might have to switch back to that for a bit. I love DataGrip and used it with Postgres and Snowflake at my last place of work with no issues. I'm really hoping that I didn't just bring down my organization's oracle server to it's knees from an introspection on a large schema that took a while. I tried to cancel it and it just kept hanging, ultimately I force quit the application and then wasn't able to connect back to the database.
I ended up walking away as I was kinda signing off for the day, but came back and hour and some change latter and it was still introspecting, granted the schema was massive. I had been doing some work, then wanted to add an additional schema to the managed schema list and it started introspection. And today, I'm nervous that I might of bogged down my organization's oracle server because of this product's problem with introspection.
0 kommentar(er)
