Oracle SQL Developer guides

blog posts All guides

blog scope What these cover, and what they do not

The rest of this site is about getting Oracle SQL Developer onto your machine: which build to take, what it needs, and what to do when the install goes wrong. These guides pick up after that — the questions that only occur to you once the tool is open and connected.

• Configuration — dark mode, memory limits, startup time, keyboard shortcuts.
• Comparisons — how Oracle SQL Developer sits against other clients, and when a different tool is the honest answer.
• Errors — the connection failures and Java problems that send people searching, with what each code actually means.

What you will not find is release-note churn or news. Oracle publishes that already, and repeating it adds nothing. These pages are written to stay useful for as long as the behaviour they describe stays true.

blog accuracy How these are kept accurate

Guides about software rot quietly. A version number changes, a build stops bundling Java, a download moves — and a page that was correct last year now confidently tells you something false. That is the normal failure mode of this kind of writing, and this site has been on the wrong side of it: an earlier version of these pages named a release six versions out of date.

• Version, build and file sizes are checked against Oracle automatically, not from memory. Sizes are measured from Oracle’s own servers rather than copied from a page, because Oracle does not publish them.
• Checksums are re-verified on every check. A stale hash is worse than none — it tells a reader their good download is corrupt.
• Claims that can be tested are tested. The answer to whether you need an Oracle account came from requesting the file and reading the response, not from repeating what other guides say.
• Dates are on the page. Where something was verified on a particular day, that day is written down, so you can judge how stale it is rather than guessing.

None of that makes a page permanently correct. It makes the page honest about when it was last known to be correct, which is the most any guide can offer. If you find something here that is wrong, the contact address in the footer reaches a person who will fix it.

blog next What is coming

Topics get written when there is something worth adding, not on a schedule. These are the ones currently worth writing, judged by what the existing pages get asked about and where the honest answers are hardest to find elsewhere:

• Connecting to Oracle Autonomous Database — wallet files, connection strings, and the parts of the process that differ from a local database.
• SQLcl for people who know SQL Developer — when the command line is the better tool, and which habits carry over.
• The VS Code extension — what it does and does not replace, now that Oracle ships one alongside the desktop application.
• Running Oracle SQL Developer against a container — the fastest route from nothing installed to a working connection.

If one of those would be useful sooner, saying so is the fastest way to move it up the list. Requests from people actually stuck on something make better guides than a list written in the abstract.

blog who Who writes these

This site is independent and not affiliated with Oracle. It exists because Oracle’s download page is organised around Oracle’s products rather than around the question most people arrive with, which is simply which file to click. Everything here links to Oracle’s own servers; nothing is rehosted, and there is nothing to sign up for.

One person writes and maintains all of it, which is a limitation worth stating plainly: coverage is narrower than a team could manage, and a guide here exists because someone hit the problem and wrote down the answer. The upside is that nothing is published without being checked, and there is no incentive to pad these pages with content nobody needs — the site sells nothing and tracks nobody.