Vsn 7.1.5 much slower than 7.0.3

[moshe]

I am running versions 7.1.5 and 7.0.3 side by side. Version 7.1.5 takes more than 70 seconds to open a database, whereas version 7.0.3 takes 8 seconds for the same database. I tried the QueryHints parameter but it doesn't seem to have any effect on the loading times for 7.1.5.

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer directory (e.g. C:\Documents and Settings\\Application Data).

Do this both for 7.1.3 and 7.1.5.

 

[radino]

I tried DebugSQL, but didn't found the problem:

c:\Program Files\PLSQL Developer>a.bat

c:\Program Files\PLSQL Developer>ECHO | TIME
Aktu

 

[Marco Kalter]

Can you check if the default printer is defined correctly in Windows, and is it is accessible?

 

[mike]

You know what? I've had the same trouble for a long time now. You gave me an idea. I disabled my plsqldoc plug-in this morning and it starts up fast again!

It's too early to tell if it will always start fast now, but it might be worth trying.

 

[radino]

Thank you, Marco
Default printer was accessible and defined correctly, but it has duplicate entry. I removed it and I also removed some other old unused printers.. Developer starts fast, now..
But, why it depends on printers? I've installed Developer on laptop, and I often work at various places, where my default printer is not accessible..

 

[mike]

Mine was slow again, so it must not have been the plug-in. I tried deleting printers. Mine seems fast again. Hopefully it will stay that way!

P.S. It didn't stay fast. Oh well. I guess I'll wait and hope for version 8

 

[Marco Kalter]

The issue seems to be related to Service Pack 3 of Windows XP in relation to the printer configuration. The exact cause of the problem is unknown, and it happens even before the application logging starts (which is the first thing PL/SQL Developer does.