How to Disable Edit SQL Popup in PLSQL Code

[Laurie Jacobson]

I recently upgraded to TOAD 11.5.1.2****

** **

Prior to this I often troubleshoot pl/sql packages by pulling up the code,
making a quick mod to the code to add bind variables if necessary, or
hard-code some values, etc. so it can run as sql, hit Shift-F9 and away I
go! Super fast. ****

** **

Now I do the same thing and it takes 8-10 minutes and finally a window pops
up saying “Edit SQL” and then I can hit OK to have it bring up the
variables window.****

** **

I would like to disable this new feature so I can go back to working
quickly. ****

** **

I saw someone else online ask about this and I understand it is related to
the fact that the code is within the PL/SQL code and TOAD is trying to be
“helpful” by analyzing the pl/sql to figure out what are the bind
variables, etc. But it’s extremely painful. ****

** **

Other than going back to an older version of TOAD .. any thing I can do?
Or other than copy/paste to another window to execute as SQL which just
makes it harder to follow the stream of code, particularly if it’s not
originally mine.****

** **

Thanks!

[Bert Scalzo]

Remember the toad advisor (main menu -> help -> toad advisor). This screen will show you which things might be slowing down toad and double clicking on them takes you right to options spot to change it

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of Laurie Jacobson
Sent: Tuesday, March 05, 2013 7:51 AM
To: ***@yahoogroups.com
Subject: [toad] How to Disable Edit SQL Popup in PLSQL Code


I recently upgraded to TOAD 11.5.1.2

Prior to this I often troubleshoot pl/sql packages by pulling up the code, making a quick mod to the code to add bind variables if necessary, or hard-code some values, etc. so it can run as sql, hit Shift-F9 and away I go! Super fast.

Now I do the same thing and it takes 8-10 minutes and finally a window pops up saying "Edit SQL" and then I can hit OK to have it bring up the variables window.

I would like to disable this new feature so I can go back to working quickly.

I saw someone else online ask about this and I understand it is related to the fact that the code is within the PL/SQL code and TOAD is trying to be "helpful" by analyzing the pl/sql to figure out what are the bind variables, etc. But it's extremely painful.

Other than going back to an older version of TOAD .. any thing I can do? Or other than copy/paste to another window to execute as SQL which just makes it harder to follow the stream of code, particularly if it's not originally mine.

Thanks!

[Michael Staszewski]

If you can send an example to me offline that might help. Also, have your DB stats been analyzed recently? Toad needs to parse the statement (quick) and resolve identifiers it locates within. This uses a combination of parsing/querying so be sure that your stats are up to date so the queries are as quick as possible. If you're unable to send an example, spool your SQL and reproduce and send me the spooled SQL output. There may be a query in there that can be tuned as well.

Michael

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of Laurie Jacobson
Sent: Tuesday, March 05, 2013 8:51 AM
To: ***@yahoogroups.com
Subject: [toad] How to Disable Edit SQL Popup in PLSQL Code




I recently upgraded to TOAD 11.5.1.2

Prior to this I often troubleshoot pl/sql packages by pulling up the code, making a quick mod to the code to add bind variables if necessary, or hard-code some values, etc. so it can run as sql, hit Shift-F9 and away I go! Super fast.

Now I do the same thing and it takes 8-10 minutes and finally a window pops up saying "Edit SQL" and then I can hit OK to have it bring up the variables window.

I would like to disable this new feature so I can go back to working quickly.

I saw someone else online ask about this and I understand it is related to the fact that the code is within the PL/SQL code and TOAD is trying to be "helpful" by analyzing the pl/sql to figure out what are the bind variables, etc. But it's extremely painful.

Other than going back to an older version of TOAD .. any thing I can do? Or other than copy/paste to another window to execute as SQL which just makes it harder to follow the stream of code, particularly if it's not originally mine.

Thanks!

[Bert Scalzo]

Just in case someone asks how to gather the stats - here's the two commands a DBA user needs to execute

exec dbms_stats.gather_dictionary_stats;
exec dbms_stats.gather_fixed_objects_stats;

But again the toad advisor would help you to turn off options for features that you may not desire - so don't discount looking there ....

Bert

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of Michael Staszewski
Sent: Tuesday, March 05, 2013 8:50 AM
To: ***@yahoogroups.com
Subject: RE: [toad] How to Disable Edit SQL Popup in PLSQL Code


If you can send an example to me offline that might help. Also, have your DB stats been analyzed recently? Toad needs to parse the statement (quick) and resolve identifiers it locates within. This uses a combination of parsing/querying so be sure that your stats are up to date so the queries are as quick as possible. If you're unable to send an example, spool your SQL and reproduce and send me the spooled SQL output. There may be a query in there that can be tuned as well.

Michael

From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of Laurie Jacobson
Sent: Tuesday, March 05, 2013 8:51 AM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] How to Disable Edit SQL Popup in PLSQL Code





I recently upgraded to TOAD 11.5.1.2

Prior to this I often troubleshoot pl/sql packages by pulling up the code, making a quick mod to the code to add bind variables if necessary, or hard-code some values, etc. so it can run as sql, hit Shift-F9 and away I go! Super fast.

Now I do the same thing and it takes 8-10 minutes and finally a window pops up saying "Edit SQL" and then I can hit OK to have it bring up the variables window.

I would like to disable this new feature so I can go back to working quickly.

I saw someone else online ask about this and I understand it is related to the fact that the code is within the PL/SQL code and TOAD is trying to be "helpful" by analyzing the pl/sql to figure out what are the bind variables, etc. But it's extremely painful.

Other than going back to an older version of TOAD .. any thing I can do? Or other than copy/paste to another window to execute as SQL which just makes it harder to follow the stream of code, particularly if it's not originally mine.

Thanks!

[nr_mendes]

Hi Laurie,

I had the same "problem" when runnig with CTRL+ENTER the solution i've found was: to run with the cursor on a line that doesnt bellong to the sql statement.

declare
v varchar2(1);
begin
for r1 in (select * <-- if the cursor stays here it will open the sql editor
from dual) loop
--do nice things
end loop;
--
dbms_output.put_line('hello'); <--- put the cursor here and run
--
end;

Regards,

Post by Bert Scalzo
Just in case someone asks how to gather the stats - here's the two commands a DBA user needs to execute
exec dbms_stats.gather_dictionary_stats;
exec dbms_stats.gather_fixed_objects_stats;
But again the toad advisor would help you to turn off options for features that you may not desire - so don't discount looking there ....
Bert
Sent: Tuesday, March 05, 2013 8:50 AM
Subject: RE: [toad] How to Disable Edit SQL Popup in PLSQL Code
If you can send an example to me offline that might help. Also, have your DB stats been analyzed recently? Toad needs to parse the statement (quick) and resolve identifiers it locates within. This uses a combination of parsing/querying so be sure that your stats are up to date so the queries are as quick as possible. If you're unable to send an example, spool your SQL and reproduce and send me the spooled SQL output. There may be a query in there that can be tuned as well.
Michael
Sent: Tuesday, March 05, 2013 8:51 AM
Subject: [toad] How to Disable Edit SQL Popup in PLSQL Code
I recently upgraded to TOAD 11.5.1.2
Prior to this I often troubleshoot pl/sql packages by pulling up the code, making a quick mod to the code to add bind variables if necessary, or hard-code some values, etc. so it can run as sql, hit Shift-F9 and away I go! Super fast.
Now I do the same thing and it takes 8-10 minutes and finally a window pops up saying "Edit SQL" and then I can hit OK to have it bring up the variables window.
I would like to disable this new feature so I can go back to working quickly.
I saw someone else online ask about this and I understand it is related to the fact that the code is within the PL/SQL code and TOAD is trying to be "helpful" by analyzing the pl/sql to figure out what are the bind variables, etc. But it's extremely painful.
Other than going back to an older version of TOAD .. any thing I can do? Or other than copy/paste to another window to execute as SQL which just makes it harder to follow the stream of code, particularly if it's not originally mine.
Thanks!

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/toad/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/toad/join
(Yahoo! ID required)

<*> To change settings via email:
toad-***@yahoogroups.com
toad-***@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
toad-***@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/