SQL Developer Alert Notification Suppression and Scope

Answer to the Question

In the current releases of Oracle SQL Developer (up to 21.2 as of 2026‑10‑18), the IDE offers a client‑side alert mechanism that fires whenever a user‑defined threshold is exceeded during a polling cycle. There is no built‑in option to configure a suppression window (cool‑down period) or to scope alerts to a particular database user or schema. The alerts are tied to the active connection and affect every session that has the alert enabled.

Why the Limits Exist

• The alert engine lives inside the IDE, not on the database server, so it cannot remember when a notification was last sent.
• Because the alerts are generated locally, the IDE cannot filter them by database role or schema without additional logic.

What Can Be Done

To achieve suppression or scoping you must move the monitoring logic out of the IDE and into the database. Typical approaches involve:

1. Creating a small metadata table to record the last notification time for each monitored object.
2. Writing a PL/SQL block that compares the current row count with the threshold and checks the elapsed time against a desired cooldown interval.
3. Scheduling that block with DBMS_SCHEDULER so it runs at a fixed frequency.
4. Sending email (via UTL_MAIL or DBMS_ALERT) to a specific list of recipients, thereby limiting the audience to the intended users or schema owners.

Practical Verification

To confirm that the IDE itself does not support suppression:

• Open Preferences > Database > Alerts (or the equivalent menu in your version) and look for any “cool‑down” or “suppress after” fields – they are absent.
• Enable a row‑count alert and observe that each poll that violates the threshold produces a pop‑up, even if the same threshold was triggered in the previous cycle.

Next Steps for Your Environment

If you need a quieter notification system or want to target alerts to a subset of users, consider:

• Implementing the database‑side solution described above.
• Using a lightweight monitoring tool (e.g., Oracle Enterprise Manager) that supports suppression windows and role‑based alert delivery.

Missing Diagnostic Detail

Does your current alert configuration rely on a third‑party plugin or a custom script executed in the SQL Worksheet, or are you using the native IDE alert feature?