Toad for Oracle 2026 R1 Beta

Toad for Oracle - Beta
1

We are pleased to announce the Toad for Oracle 2026 R1 beta

We encourage you to participate in the beta program to help us deliver a high quality product. This is your opportunity to participate in the development, direction, and testing of Toad for Oracle. By becoming a beta tester you will have direct access to the development team and product management via the Toad World forum.

How to join the Beta program:

  1. Read the Beta Agreement. Downloading the Toad Beta constitutes usage agreement.
  2. Install Toad for Oracle version 25.3 for Windows first.
    a. This must be a licensed, non-trial version
    b. Run version 25.3 at least once before running the beta.
    c. Leave 25.3 installed. The beta does not replace it.
  3. Download and install the beta (links below)

Which version?

If you have a 32-bit Oracle client currently installed in a 32-bit or 64-bit environment:

If you have a 64-bit Oracle client currently installed in a 64-bit environment:

Beta expiration

Each beta expires after 4 weeks, but new versions with later expiration dates are released often, typically on Mondays. An indicator will appear on Toad's status bar when a new version is available. Click it to download and install the update (No need to remove the old beta first, just install the new one on top of it). It's very easy. In this way you can continue to use the beta until the next version of Toad is officially released.

We encourage you to stay up-to-date with the most recent beta version, and do not hesitate to post suggestions or problem reports to this forum. The development team reads every post and typically responds very quickly.

A note about Oracle clients:

  • 12cR2 and 18c are the recommended client versions.
  • 19c and 21c clients will work, but they leak memory with LOBs, and sometimes hang when cancelling queries against 11gR2 servers. The memory leak is not terribly severe, but something to be aware of. You can just restart Toad if/when you need to reclaim the leaked memory.
  • 12cR1 and older clients don't handle XMLTYPE natively.

Toad's no-client option

  • Uncheck the "Use Oracle Client" box on the login window to connect to the database without an Oracle client.
  • Pros of no-client option:
    • No setup required
    • It is a bit faster than using a client.
    • Supported: LDAP, TNSNames.ora, TNS_ADMIN environment variable, Oracle Encryption and Data Integrity, Spool SQL, SSH, TCPS, IPV6, External authentication, and Oracle Wallet connections.
    • Can connect to every database version since 7.3!
    • Can connect to very old and very new database versions at the same time.
  • Cons of no-client option:
    • Not supported: Oracle client style tracing/logging, proxy connections, Kerberos
    • If you don't have an Oracle client installed, of course you won't have their tools like SQL*Plus, DataPump, Import/Export, but if you have a client installed Toad can still use these tools, even if you run Toad in no-client mode.

What is this sorcery that Toad can connect to the database without an Oracle client?

  • The Oracle client is just DLLs (and some other files) produced by Oracle that know how to connect to the database. Toad now contains code that can achieve the same thing. We did not compile Oracle DLLs inside of Toad, or package them together in any way.

The beta change log is below

9 Likes
36

Toad Beta Change Log

Toad Beta 26.1.38.7475, Released 17-Nov-2025
Bug Fixes

  • Connections: Connection bar button does not display new container when changed by ALTER SESSION command from Editor
  • Data Grids: BFILE not displayed correctly in no-client mode
  • Data Grids: Custom Column filter on timestamp columns allow only one character of input
  • Data Grids: Custom Column filter not showing dropdown items (Equals, Greater than, etc) properly when primary display is scaled over 100%
  • Data Grids: Pivot grids don't show grand totals if scientific notation option is unchecked
  • Edit Login Window: Oracle clients not shown in dropdown
  • Editor: Status bar customize dialog gave access violation if down button clicked without first selecting an item in the listbox
  • Editor: Save as dialog showing "All Files" for file type on first save
  • Editor: Script execution did not run script in some environments
  • Export Dataset: ANYDATA columns not exported correctly
  • Export DDL: Create trigger script incorrect for disabled compound trigger
  • Export DDL: Script incorrect for interval-partitioned tables with all system-named partitions
  • Export DDL: Non-unique indexes used for constraints appear after their constraints in the script, resulting in SQL error
  • High DPI: Undocked output/spool SQL window not scaling/sizing correctly
  • High DPI: Object Search window sometimes has unneeded scrollbar
  • High DPI: Font Size may be incorrect in SQL Recall
  • Login Window: Access violation when window opens if datagrid is grouped and filtered so that all connections are filtered out
  • Login Window: Access violation when filtering connection color column in grid, but not selecting a color
  • Options: Data Grids-Visual - Importing styles does not work well and results in access violation in some cases
  • Options: Editor Font/Styling - changing one of the background colors from a color to "None" results in access violation
  • Schema Browser: Invalid Objects RHS does not update when switching between package spec and body in LHS
  • TNSNames: Connections with multiple names not fully supported

Enhancements

  • Data Grids: ANYDATA values now displayed and can be edited via popup dialog
  • Icons: Improved the look of a dozen or so icons
  • Login Window: If "Favorites Only" is checked, new connections automatically marked as favorite
  • QSR: Added caret position to status bar
  • QSR: DBMS Output added
  • QSR Script timing added
  • Session Browser: Many enhancements, see this document for details

The change log for Toad version 25.3 is here

5 Likes