How to prevent users from doing inserts, updates and deletes from within TOAD?
You can restrict individuals or groups of users from accessing some TOAD features using Toad Security. In addition, you can make TOAD read-only for individuals or groups of users.
You can change Toad to be read-only using the two license files: READONLY.LIC and FULLTOAD.LIC.
TOAD.EXE only reads TOAD.LIC to determine if it is full TOAD or read-only. The license file contains a setting for read-only database access. The network administrator can copy READONLY.LIC over the TOAD.LIC on an individual workstation to make TOAD read-only at that workstation. Remember, the TOAD.LIC file must be in the TOAD folder.
In addition, we can provide a read-only copy of TOAD. The TOAD Standard Edition - READ ONLY install is a read-only executable designed to prevent its users from changing the database. For this reason, it does not include Quest ScriptRunner (which lets a user write a script that can update database objects), SQLMonitor (which logs SQL calls via the OCI layer), and Server Side Install (which lets users make changes to TOAD schemas).