![]() This is a SQL trace that shows considerably more information about the executed SQL including wait events, time executed, and also the actual explain plan used with actual row counts. Toad does quite a bit more with the 10046 trace (pronounced “10 thousand 46”). This is the explain plan that it executed with and you can easily see any additional child cursors. SQL Developer produces an explain plan and pulls in the outline and some additional information. The tree format is more for the novice perhaps. There are a few other display options as well. Toad can also display Explain Plans in DBMS_XPLAN format. Toad can display the current Explain Plan after execution. Both tools can show the current explain plan after execution as well. This is probably where some of the bigger differences between the two tools areīoth tools have quite a bit of flexibility when it comes to the exposed Explain Plan content. The first panel above gives additional information about the entire execution process. In the above ‘Call Hierarchy’ tab, you can see the lines that took the longest to execute as well. This profiler gives a considerable amount of additional detail. SQL Developer has a nice interface to the Hierarchical Profiler introduced in Oracle11. Also, when you click on any line in the profiler output, the related line in the editor window highlights. Easy to see exactly where your PL/SQL routine spent its time. Toad has a nice interface to the PL/SQL Profiler.Įasy to use and get line-by-line execution time and number of passes in loops, etc. SQL Developer, I need to put a break point after the Begin if I want to start line-by-line debugging (using the ‘Step Into’ from the beginning of the program.) Other than this feature, both debuggers work very similarly, as they both use the same interface into the Oracle RDBMS. ![]() I can start the debugging process in Toad just by pressing the ‘Trace Into’ button. There is a feature in Toad’s version of the debugger that I like. This blog did point me in the right direction and I was able to get the debugger working, but not in time for the class… In older versions of the database and perhaps older versions of SQL Developer, the debugger worked right out of the box. I’m not a network hack and his instructions were good but not quite complete. I got quick assistance from the Oracle team and was referred to Galo Balda’s blog. I was caught off guard in a class becausethis feature that needed additional setup. SQL Developer’s debugger in Oracle12 needs some additional permissions to run. SQL Developer doesn’t have anything like this.īoth tools have a similar PL/SQL debugger. Click here to read my blog on Code Analysis. Team leads can quickly see the complexity of the code and make sure the correct people are assigned to a coding project. Developers can see how they did with both complexity of the PL/SQL and SQL code. Toad contains Code Analysis, a nice review using industry standard rules to view PL/SQL code complexity, complexity of the SQL inside the PL/SQL routines, and quality of the PL/SQL code in general. SQL Developer Code Templates/Auto Replace Both tools have good coverage of SQL and PL/SQL topics, including optimizer hints that I use from time to time when doing SQL tuning. Toad has a considerable bit more in both the code template area and the auto replace area. Both allow for coding shortcuts, with SQL Developer using its Code Template setup and Toad usingits Auto Replace feature. SQL Developer’s are signaled with their shortcut name and the space bar. Toad’s templates are signaled with a short name and the CTRL + space bar, or just CTRL + space bar to bring up the whole list. Toad has quite a few more code templates and they can be setup to be quite interactive with substitution variables. Toad has a more robust code template with just over 40 templates, where SQL Developer has templates as well their code examples are both in SQL Editor Code Template area (fewer than 10 templates and work more like Toad Auto Replace) and has better code templates in its snippets panel, but again not very many of them. Notice the slider bar, there are quite a few more selections than what would fit in this display box. SQL Developer has a separate snippets panel just for Analytical SQL. Both tools have a history of SQL executed.īoth have code snippets panel where you can drag and drop code examples/formats/hints/formatting/more to the editor window. I hope to do so in an objective way.īoth tools have insights…popup of available objects/columns where you can click and add to your SQL. Since I work with both tools in my training business, people often ask me to point out the differences in the two. ![]() Hi, This article hopes to compare Toad v13.0 and SQL Developer v18.1 a bit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |