It’s easy to forget that many people still have not discovered SQL Developer, or are just getting started. Many of my recent posts have been on advanced topics, hidden tricks, and productivity tips.
I want to spend some time in the next few weeks helping the beginners out there.
I can’t think of a better place to start than with how to ‘install’ SQL Developer.
I’ve been telling anyone who will listen than you can get up and running with SQL Developer in under 5 minutes. That’s a pretty big claim, and I reckon I should back that up now.
Disclaimer: I have a hi-speed residential network connection that was averaging 15.93Mbps this morning. I realize many of you have connections that are both slower and faster, so keep that in mind when I make my ’5 minute’ claim.
The Basics – Download SQL Developer
The hardest part is the first step – picking your download and waiting. If you have a 64 bit Windows machine, you’ll need to download the 64bit 1.6 JDK first.
JDK? JRE? Java? What?!?
SQL Developer is a Java application. To run it requires the Java Virtual Machine – this is the ‘go box’ for java applications. If you’ve ever seen that funny icon popup in your systray while running apps over a website, that’s probably java.
JDK – Java Development Kit. I call it the ‘Toolkit’, but it’s just a ‘Kit,’ but not THAT K.I.T.T.
The Java Runtime Engine (JRE) is a smaller and less powerful ‘go box’ for Java applications, but SQL Developer relies on some of the libraries included only in the JDK – so get the JDK!
Many versions of Java out there – 5, 6, and 7 are the most common. The name is ’6′, but the version is ’1.6.’ We develop, test, and support SQL Developer for 1.6. You can run other versions, but may get less than awesome results.
It’s an archive, not an installer. After you’ve downloaded SQL Developer, there’s no installer to run. Just extract the folder, then find the ‘sqldeveloper.exe’ and open it.
If you’ve downloaded the 32 bit windows version with the JDK bundled, you’re all set.
If not, you’ll need to tell SQL Developer where it can find it’s Java master, AKA the Java Virtual Machine. Be sure to point to the ‘java.exe’ in the full JDK (not the JRE.)
Once you hit OK, you’ll never have to answer this question again.
You can change this location later in the /sqldeveloper/bin/sqldeveloper.conf file. Change the following line -
SetJavaHome ../../jdk
SQL Developer will then start, and you can proceed by setting up your connection.
Before you can connect, you will need the following:
- database user account (complete with username and password)
- location of database (either via TNSNames, LDAP, or servername/IP, port, and SID/Service)
If you don’t have an account, don’t go online asking people for a ‘default.’ Find the owner of your application or database and ask them for an account. If you don’t want to involve them, then you’re looking for a backdoor and could be labeled a ‘hacker.’
Now what?
Now you get to learn by doing. Many of you won’t have access to formal training, and I think that’s a real shame. If your organization provides training or compensation for taking classes – do it! Lots of free resources out there, including my blog of course.
Here’s a rundown of the official stuff from Oracle:
- OTN SQL Developer Forum – ask questions here
- 60+ video tutorials in the Oracle Learning Library (OLL)
- 10 Step Getting Started Guide


Twitter
RSS
GooglePlus
Facebook
May 08, 2012 @ 10:48:35
Nice slipping in the reference to Knight Rider.
May 08, 2012 @ 11:11:22
One of my primary motivations for blogging, nostalgia for my favorite childhood TV programs
May 09, 2012 @ 11:15:24
The is one issue that you should point out which I ran into the other day. In the directory which was set a the location of the tnsnames.ora file I had a couple of files called for example tnsnames.sav or tnsnames.old. I had a failure to connect to databases using the TNS method in SqlDeveloper until I removed all files having any name that started with tnsnames. When asked I was told that it is a known issue but not a bug? I’m not sure why it isn’t a bug since there can exist on one tnsnames.ora file at a time but it took a bit of time to figure out what was causing the issue.
May 09, 2012 @ 12:55:06
Dennis, were you working on the OTN SQL Developer Forums or did you contact support? If support, could you send me the SR details to my email, jeff.d.smith@oracle.com?
I’m of the same opinion as you, but I’ll withhold judgement until I can gather all the facts
Jun 01, 2012 @ 21:02:17
Some follow-up information for those reading Dennis’ comment. It turns out that SQL*Plus will read all upper(filenames) starting with ‘TNSNAMES.’ So if you have multiple old copies archived off as tnsnames.old1, tnsnames.old2, etc – SQL*Plus will see all of those entries.
SQL Developer has the same behavior. Since we have a TNSNames selector, you may see multiple entries of the same name – that’s SQL Developer parsing multiple TNS files. To avoid this behavior, add a _ or any other character to the beginning of your old TNSNAMES.ORA files.
Oct 12, 2012 @ 15:11:51
Love the videos on your website, Jeff. What software do you use to record these videos?
Thanks,
Marilyn
Oct 12, 2012 @ 15:22:24
Camtasia Studio 7. I use it produce the GIFs that I have embedded in my blogs posts as well. Super easy to use.