There are two primary methods for achieving a portable state with PL/SQL Developer:
This is the bigger issue. PL/SQL Developer requires an (or Instant Client) to connect. If you move to a machine without Oracle libraries, you’ll get a dreaded “ORA-12154: TNS could not resolve the connect identifier.”
Let’s cut to the chase—Allround Automations (the maker of PL/SQL Developer) does not officially release a portable version. However, that doesn’t mean you can’t achieve a portable-like workflow. In this post, I’ll break down why you might want a portable setup, the official limitations, and the safest workarounds to take your IDE on a USB stick.
Portable versions do not write to the Windows Registry. This results in a "clean" host machine, avoiding "DLL hell" or conflicts with other Oracle tools (such as differing OCI versions). It also simplifies the process of running multiple versions of PL/SQL Developer concurrently (e.g., version 12 for legacy systems and version 15 for modern environments).
Allround Automations distributes PL/SQL Developer as an ( .exe ). However, a lesser-known fact: you can extract that installer using tools like 7-Zip or simply run it once, then copy the installation folder.
: Use a launcher script that backs up/restores Registry keys on the fly or redirects them using PortableApps.com launcher technology.