Friday, 17 August 2007

Other 11g news: The little SQL Developer editor that could

The new 11g release of the RDBMS has brought an interesting array of new features for database administrators and developers, including new tuning features, revisions to SQL and PL/SQL and the inclusion of the latest version of Oracle Application Express (APEX).

One additional inclusion in the 11g release that hasn't received much press is the inclusion of SQL Developer in the default RDBMS install package. As of the 11g release SQL Developer v1.1.3 is now included by default.

This brings up an interesting point. SQL*Plus for many years has been a dominant SQL editor for the Oracle RDBMS for the fact that it's a common dominator on all Oracle installs. Guaranteed between Oracle sites, you can ensure SQL*Plus is installed. I often make this point to students when teaching SQL why SQL*Plus is preferred.

So it's now possible with the inclusion of SQL Developer we may see a gradual change in SQL*Plus's dominance given that SQL Developer will be readily available for use on all installs. You never know, you might even see hardcore DBAs using it ;)

Oh, and before the SQL*Plus lovers jump on my back, I'm not advocating SQL*Plus's replacement, that one tool is better than another, that SQL Developer should be used in a production environment, just the fact above. It's nearly the weekend here. Who needs another flame war?

Thanks to Sue Harper for the heads up & confirmation on this factoid from this OTN Forum post.


Laurent Schneider said...

Thanks for mentioning this!

Niall said...

This hard core DBA does use it. Really quite a lot. Not for automation where sqlplus excels, but for code review, pl/sql development and so on.

Marco Gralike said...

Also see "the new and the old" in post (June 23rd, 2007)




Chris Muir said...

Thanks for the comments gang.

Niall, I must admit I'm using it more and more too (not that I'm a hardcore DBA).... Because of the usual Toad licensing issues at each new customer's site I visit (I'm too cheap to buy it, so the customer must have a licensed version otherwise I wont use it), and for the fact I really only use 10% of Toad anyway, SQL Developer is hitting a sweet point with myself at the moment.

I've still some major gripes about the PL/SQL editor, in that it's just frustrating to use in general (and that's not a comparison to Toad, but more a comparison to JDeveloper and a text editor like UltraEdit), but I'm sure usability will get better in time.

Cheers all,


PS. For a proper link to Marco's post go here.