Toad versus Database Security
Probably the most frequent question asked by shops new to Toad is “Will Toad enable my developers or business analysts to do things in the database that they’re not permitted to do?” Because Toad is so easy to use and so powerful, some fear that it might allow users to do bad things—like drop a production table or delete all of its data.
The simple answer is “definitely not,” because Toad cannot override or supersede Oracle’s inherent security. A Toad user has only whatever roles, system privileges, or object grants exist for the user he or she connects as. Thus users can do no more in Toad than they could in SQL*Plus (they simply can do it more easily and faster via Toad). To reiterate, Toad permits database users ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access