Snapshots
In Toad Edge, snapshots are a way of storing database structure (without data) as a readable JSON file. This file can be subsequently used as a create script source or as a Schema Compare source/target in Continuous Integration and Delivery (CI/CD).
There is also another type of snapshot - baseline snapshot. It is nearly identical to regular snapshot except it can be used in CI/CD in the Compare database with baseline build step. This build step will return an error if the database is different from the baseline snapshot. See Continuous Integration and Delivery Wizard for more information.
To take a snapshot of a database
- In Object Explorer, right-click any database and select Take Snapshot
- Change the snapshot name if you wish. Then click OK
Snapshots are stored in the Toad Edge folder structure. You can access the snapshot files in Snapshots View.
Templates
Templates are script snippets that can be reused in various editors. In Toad Edge, templates can be defined in three contexts:
To configure templates
- Go to Preferences (View menu | Preferences or press ALT + P)
- Switch to the Templates tab. Here you can add/edit/remove templates
|
|
TIP: You can use variables in the code of your templates by typing ${variableName}. If you need to enter a literal dollar symbol, enter two dollar characters in sequence $$.
When a template is used, its variables can be quickly set to specific values. You can also jump between the variables by pressing TAB and SHIFT + TAB. |
User Privilege Managements
The subsections below explain the various user privilege views provided by Toad Edge®Edge and their management w.r.t to an object or an user.
About User Privileges
Toad Edge provides a number of options related to user privileges and how to grant/revoke them. As a general overview, user privileges are granted/revoked on three levels.
- Server (global level)
- Database/Schema
- Database objects (tables, views, routines - procedures and functions)
These levels also represent a hierarchy where privileges on higher level are inherited at lower levels by default.
User privileges can be of several types:
- Inherited (
) - the privilege has been granted on higher level and it is not possible to revoke it on the current level
- Example: User has been granted the CREATE privilege on the server level. It appears as inherited on the database/object levels and cannot be revoked there. It can be granted again on lower levels although this is unnecessary
- Granted & Inherited (
) - this privilege has been granted on higher level and also on the current level
- Example: User has been granted the SELECT privilege on the server level and then again on the database level. It appears as granted & inherited on the database level
- Granted (
) - the privilege has been granted on the current level and can be revoked
- Example: User has been granted the UPDATE privilege on the object level. It appears as granted on the object level, and it can be revoked
- Revoked (blank value) - the privilege has not been granted on any level
- Example: User has been revoked the EXECUTE privilege on the database level. It appears as revoked on the object level. It also appears as revoked on the server level as if it were granted on the server level, it could not be revoked on the database level in the first place
The following table describes how privileges set on higher levels affect privileges on the other levels:
| Granted |
Inherited (granted) |
Inherited (granted) |
| Revoked |
Inherited (revoked) |
Inherited (revoked) |
| Revoked |
Granted |
Inherited (granted) |
| Granted |
Granted & Inherited |
Inherited (granted) |
