SQL Developer 4.0


Oracle have given birth to SQL Developer 4.0 today, as announced by Jeff Smith.

I had access to the first Early Adopter a few weeks before it hit the OTN download page, so it feels like I’ve been using some flavour of SQL Developer 4 for ages. I’m kinda old-school, so I still find myself working with a text editor (UltraEdit) and SQL*Plus a lot, but I’m trying to use SQL Developer more these days. The addition of the Performance Reports (AWR, ADDM and ASH) was certainly a nice touch.



Performance Reports in SQL Developer 4 EA2


SQL Developer 4 EA2 includes a performance node in the DBA tree.



You can use this to view ADDM, AWR and ASH reports directly from SQL Developer. I know I can get these from Cloud Control, but previously I tended to pull these out from the command line on the server. This is a much better approach IMHO.

I found out about this stuff at OOW2013, whilst talking to Jeff Smith and Barry McGillin in the demo grounds. I tweeted some pictures at the time, but figured it was worth a post for those that don’t do Twitter. :)



PS. Yes, it is only going to be of use to people connecting to Enterprise Edition databases with the Diagnostics & Tuning Pack.

SQL Developer 4 EA2 Connecting to SQL Server


I wrote a blog post some time ago about using SQL Developer 3.x to connect to SQL Server. I tried the same thing today from SQL Developer 4 EA2 and it works just fine.

You have to download the 3rd party JDBC driver and point SQL Developer to it. You can read how to do it here.



Update: My colleague just told me this.

“If you at any point decide to use Windows authentication to connect (like I just did), you might hit this error:

Status : Failure -I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.

…found a work around, which involves copying the ‘jtds-1.2\x86 (or X64)\SSO\ntlmauth.dll’ from the JTDS directory to the JDK’s \jdk\jre\bin folder. Then I restarted SQL Developer and it worked J”

SQL Developer 3.1 : Scheduler Support…


I had a play around with the scheduler support in SQL Developer 3.1 today. I’m late to the party because most of it has been there since 3.0, but what the hell.

It’s more of an opinion piece, so it started as a blog post, but it got too big. Not really what I usually put on the website, but I figured if I put it on the blog it would get in the way of the movie and book reviews and that simply wouldn’t do… :)

I am still worried about feature creep turning SQL Developer into the new TOAD, but so far so good. I’m liking it more and more with each release.



SQL Developer 3.1 : Data Pump Wizards…


One of the things that sounded kinda neat in SQL Developer 3.1 was the Data Pump Wizards, so I thought I would have a play with them.

As you would expect, they are pretty straight forward. They can’t do everything you can do with expdp and impdp, but they are pretty cool for on-the-fly tasks.

You can use the wizard to generate data pump definitions using the PL/SQL API. It would have been a nice touch if it gave you the option to see a regular command line or parameter file definition also, since I would be more likely to put that into source control than the API definition of a job. Even so, a nice little feature.



SQL Developer and MS SQL Server…


This afternoon I’ve been cleaning up some data in an SQL Server database. I decided to use SQL*Developer to connect to SQL Server by following this post.

I made liberal use of the following tip when dealing with TEXT and NTEXT types.

The joys of dealing with multiple engines…