Transferrinf from Toad to PL/SQL developer and struggling with tasks

[Boydy]

Can anyone help with the following points? My company have recently transferred from TOAD to PL/SQL Developer and I am getting lost with the functionality. Any chance someone could point me in the right direction with some points?

They are

Seems very resource hungry

I cannot connect to 2 different dBases at the same time

No script output that I can see

Not easy to run lots of small scripts

Navigation is not as well laid out

Cannot run install packages saved as SQL files - need to change the file extension

If you include the line 'show errors' in your SQL code it will not compile

Some files that will compile in Toad or SQLPlus will not compile in PLSQL - this could mean many of our standard scripts need rewritten.

All the available plug ins are not supplied or supported and may only work for certain versions

It does not provide all of the functionality that we currently use via TOAD - No autocomplete for example

Thanks in advance for help. I know these issues have probably been mentioned already but I was hoping by lumping them all together it would make them easier to answer.

There may be more after this as well

Cheers

Boydy

 

[mike]

Any change is often not fun. Here are a few things that might help. I think it's going to be helpful to go through a lot of the preferences.

*** Seems very resource hungry - This is interesting to me, because I've said that about TOAD. Perhaps things have changed.

*** I cannot connect to 2 different dBases at the same time - this is true. You can have more than one PL/SQL Developer running at the same time connected to different databases though. Also, next to the "key" icon, there is a drop down and you can easily switch databases if you enable the "Oracle/Logon History/store history" and "store with passwords" preferences.

*** No script output that I can see
*** Not easy to run lots of small scripts
It's my understanding that TOAD now has one editor for all things. PL/SQL Developer has several dedicated editors. The "Command Window" has script output and is useful for scripts. It has an "editor" tab for your script and a "Dialog" tab. It's similar to using SQL Plus and the edit command. I believe the output of scripts is set in the "files/Directories" preference. I'm not sure what you mean by running lots of small scripts being easier in TOAD.

** Cannot run install packages saved as SQL files - need to change the file extension - You can change the extensions in the "files/Extensions" preference to be "sql".

*** If you include the line 'show errors' in your SQL code it will not compile - If you put a "/" after the package and then have "show errors" it will open the "show errors" in a separate tab next time it's opened. If you enable the preference "Window Types/Ignore Unrecognized PL/SQL" you can compile without it complaining. I usually have the "show errors" commented out until I save and exit the first time.

*** Some files that will compile in Toad or SQLPlus will not compile in PLSQL - this could mean many of our standard scripts need rewritten.
I haven't heard of this. You might consider e-mailing the code that won't compile to Allround Automations support. They are very good at responding to any problems I've had.

*** All the available plug ins are not supplied or supported and may only work for certain versions.
I think that's probably true. Many of the plug-ins were written by people other than Allround Automations, so support will vary. I've noticed that some of the plug-ins are now standard functionality for later versions of PL/SQL Developer also.

*** It does not provide all of the functionality that we currently use via TOAD - No autocomplete for example.
PL/SQL Developer has what is called "AutoReplace". That way you can have "S" replaced with "Select" for example. This is set up in the preference "User Interface/Editor/AutoReplace". There is also a "User Interface/Code Assistant" that is helpful. If there is missing functionality, you might ask for specifics or look for it in the manual. Perhaps it's there, but different, or there's a workaround in some cases.

 

[Boydy]

Thanks very much fort he reply. your comments are very useful and hopefully will solve some of the problems we are having. I also think there may be more questions so watch this space lol

 

[mike]

Oops - I forgot something.

I modified my template for package bodies and specs like below. That way the "show errors" comes up in a separate tab as soon as I start a new program and I don't worry about it:

CREATE OR REPLACE PACKAGE [NAME]
AUTHID DEFINER AS
--[Synopsis]
--#version $Header: [NAME]_s.sql$
--#author $OSUSER

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- MAINTENANCE HISTORY
--
-- DATE NAME COMMENTS
-- ----------- ------------------ -----------------------------------------
-- $Date $OSUSER NEW PACKAGE
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

-- Public Functions and Procedures

END [NAME];
/
show errors;

 

[Boydy]

Ok guys told you I'd be back.

Next problem is this.

Trying to run 288 insert statements in sequence to amend tables every month.

Used to be a ble to do this in TOAD but now getting a " Maximum Open Cursors " Error and it looks like a cursor is being open for every statement which never happened in TOAD. Any ideas as to what is causing this and what can be done to ensure it doesn't happen.

Cheers,

Robert