Introspecting server objects - very slow

Hello,

I'm connecting to AWS Redshift using PyCharm Pro's database features, and the 'Introspecting server object' feature is extremely slow. We do have a large data warehouse that I am connecting to, but with only a few schemas included the introspection action can take 30 minutes or more. Clearly this is not good for productivity, and I find myself having to use another database client to get the table information quickly. What control do we have over the introspection to make the time sink manageable? How can I optimize this?

10 comments
Comment actions Permalink

1. What schemas do you use: external or not?

2. What kind of objects do you have in the database mostly?

3. Please send SQL log (Help -> Show SQL Log) to datagrip@jetbrains.com

0
Comment actions Permalink

Hi Maxim,

Hopefully I can answer your questions correctly.

1. We have a few external schemas, but I'm not accessing those.

2. The databases are a 50/50 mix of tables and views. A variety of data types but mostly string-based data

3. Sending

0
Comment actions Permalink
Didn't get the logs :( Can you please resend to maxim.sobolevskiy@jetbrains.com
0
Comment actions Permalink

Hey Maxim, any clues on this? It's been an issue in DataGrip as well as PyCharm Pro. Currently our best practice is to use the JDBC introspection, as that seems to help, and turning off autosync.

0
Comment actions Permalink

In logs, we see that you use JDBC-based introspection. Please, turn it off and see what happens.

 

0
Comment actions Permalink

I switched to JDBC in reaction to the slow introspection. It seemed to perform better. FYI in the latest update (PyCharm 2019.1) the introspection is really fast, usually resolving the schemas, tables and columns in 1 minute or so. Problem solved?

0
Comment actions Permalink

I m having a similar problem when introspecting my database. It takes approximately 5 minutes and i then receive 

Error encountered when performing Introspect database ve202 schema dev_jones_data_collection (details): [Vertica][VJDBC](2472) ERROR: Cannot prepare statement - too many prepared statements.
[Vertica][VJDBC](2472) ERROR: Cannot prepare statement - too many prepared statements
and 96 duplicate reports (4 m 7 s 496 ms)

How can i solve this ? 

Is it possible to only introspect a specific schema that i select from the database overview tree ?

 

0
Comment actions Permalink

Hi, Theves! We've got your email and answered.

0

Please sign in to leave a comment.