Slow response from various areas

[molloycp]

Just starting using PL/SQL Developer, so please be patient.

When selecting tables in Query builder, I'm experiencing extrememly long waits for the tables to actually appear. So long that it makes working with query builder impossible.

In the object browser, I've learned not to "expand all" as it will chug away for longer than I can stand.

I also clicked on the link query button once (to see what it does) and my control of the application disappeared, forcing me to teminate the application.

As well, I find the copy to excel functionality very slow. I typically move 2000-30000 records for analysis but when I use this functionality instead of the CSV route I can actually watch record by record the inserts into excel...Is this the way it is suppposed to work?

Do these issues have anything in common? and are there settings that can be changed to improve the response time in query builder, the object browser, and the copy to excel?

Other than the above...I am extrememly pleased with the application and it's many features.

 

[mike]

I used to not worry about the browser filters and it seemed slow. Setting up a few browser filters to select only tables I normally use noticeably speeded things up in the browser and query builder so now I always use them.

Just look at the pre-defined ones (click on the wrench on top of the object browser to change them) and it's pretty easy to figure out how to create new ones and ignore stuff you don't need.

When I have thousands of records to copy to Excel, I don't use the copy to Excel option since it's slow. Instead, do a "copy with header", open up Excel and paste it. Then you need to format/column/autofit selection to make it look good. It's more work, but it's faster.

 

[Marco Kalter]

The first 3 performance issues (query builder, object browser, linked query) could be caused by poor performance of the Oracle dictionary views. This would make a lot of features slow.

It may help to change the "Use DBA views if available" preference (Tools > Preferences > Options tab page).

The Excel issue seems like a local problem, since it does not require much database access. If there is a lot of disk activity during this operation, it may be a memory issue.

------------------
Marco Kalter
Allround Automations

 

[molloycp]

Thanks for the quick reply. I tried using the DBA views as suggested and limiting my browser window, but it had no effect. In query builder, when I select a 2 field table it takes 8 seconds for the table to appear. A 22 field table takes 40 seconds, a 210 field table takes 3 minutes and 50 seconds.

I also use "SQL Navigator" that has a similar query tool in which I do not experience delays at all.

Any further ideas on what could be wrong? I'm running this on a 2ghz compaq running windows 2000 with 512 meg ram and a 1.6 Ghz windows XP with 512 meg ram.

 

[Marco Kalter]

What happens if you select the same table in PL/SQL Developer's Object Browser, right-click on it, and select "View" from the popup menu. Does this also take such a long time? If not, what happens if you expand the "Foreign key references" folder of this table in the Object Browser?

------------------
Marco Kalter
Allround Automations

 

[molloycp]

I tried the largest table (210 fields) and it took 1 minutes 35 secs after selecting "view" for the info to come up. There are no foreign keys for this table.

Any ideas on what could be causing this type of response? Is/has anyone else experienced this and resolved it?

 

[Marco Kalter]

My guess is that your dictionary views have a performance problem.

Perhaps you (or your DBA) can try verify this? Maybe you can see the active SQL statement during the 1:35 minute delay?

------------------
Marco Kalter
Allround Automations

 

[TenGor]

Hy,

perhaps i have the same problem...
I have a DB with over 500 tables.
If i set the Session-Mode to "Multi-Session" it takes a very long time to query a table.
When i set to "Single-Session" the speed is ok, but you must remember that only one session is open...

In smaler DB's (about 100 Tables) there is no Problem with this.

Hope i could help...
CA
TenGor

 

[molloycp]

Tried changing to single session. It had no effect on the response time. I will talk to the DBA to see if there are performance problems with the dictionary views. However, I run SQL Navigator as well, and there are no delays when getting info from the dictionary so it may be a difficult problem for the DBA to resolve.

Thanks for your help...has anyone else experienced this?

 

[Marco Kalter]

The delay may be caused by one specific query that PL/SQL Developer executes and that SQL Navigator does not execute. If this one query takes more than a minute, your DBA may be able to find it.

------------------
Marco Kalter
Allround Automations