The Studio analyzes the script for the presence of DELETE, DROP, TRUNCATE, and UPDATE statements and produces a blocking message if the statements are used in certain types of environments. For example, it alerts you if the DELETE statement targets a production database. This feature helps prevent accidental or intentional data loss caused by untested code, unintended commands, leftover statements, or other errors that could irreversibly damage data or objects.

To configure the behavior of execution warnings:
1. Select Tools > Options.
2. Select Environment > Documents > Execution Warnings.
3. In Max script size to analyze, enter the maximum size (in kilobytes) of scripts that will be analyzed.
4. In the table, select the environments and statements to enable execution warnings for.

To disable execution warnings for a specific piece of code, wrap it with the nowarn and endnowarn tags.
--nowarn
<code>
--endnowarn

Execution notifications inform you about the query execution result. They appear in the lower-right corner of the screen.
The notification contains the following information:
Query execution status:

1. Select Tools > Options.
2. Select Environment > Documents > Notifications.
3. Adjust the settings:

Note
If a query exceeds 23:59:59 in execution time, the duration in the notification includes days.
If there are open transactions during the query execution, a notification appears in the lower-right corner of the screen.
The notification contains the document name and the number of open transactions.

Note
The VIEW DATABASE STATE permission must be granted on the database for this feature to work properly.
1. Select Tools > Options.
2. Select Environment > Documents > Notifications.
3. Clear Notify if execution contains open transactions.
