Most of the other developers I work with refuse to leave toad for SQL Developer in it's current state, even if the TOAD version they have access to is a couple releases behind the current. I liked the idea of being able to build extensions/plug-ins, even if I really haven't had the time. I was brought up on TOAD but I've been using SQL Developer pretty much since the 1.5 release. On the plus side, if you're doing reports, sql developer lets you 1) share reports from a single xml file, 2) do some very basic graphing (I have a set of reports for process performance monitoring), and 3) you can create reports with parent/child relationships that let you alter each one with just clicking a row from the parent. Also, if you do PL/SQL Debugging, supposedly each uses a different method to do it in the background, but a debugger is a debugger.

TOAD offers a lot of stuff out of the box that CAN most likely be mimicked with SQL Developer with reports, extensions, and plugins.you just have to put the work into getting there. TOAD seems to have the advantage of being less buggy, at least from my experience.but none of the bugs have been showstoppers. 1.7K Training / Learning / Certification.165.3K Java EE (Java Enterprise Edition).7.9K Oracle Database Express Edition (XE).3.8K Java and JavaScript in the Database.

Toad for oracle 12