Configurable Execution Warnings
The new Execution Warnings functionality to warn of UPDATE or DELETE statements without a WHERE clause is great; however, the warning triggers even when the code is in the definition of a Stored Procedure.
It would be good then to have advanced functionality to allow for us to be able to select whether to warn on SP definition text, or to turn on the warnings when running against temporary tables.
Thomas Rushton
shared this idea
This feature was released in version 7.3 of SQL Prompt.
If there are any missing features please let us know by creating a new suggestion.
Kind Regards,
The Prompt Team
-
Steve King
commented
Would be really useful to have the ability to add custom search terms to warn on.
E.G. we try and avoid developers creating objects in the primary file group but are often provided scripts to deploy which have "ON [PRIMARY]" where they have scripted the object from a dev db.
It would be nice to have a warning in case I forget ti check/don't notice this. -
Thomas Rushton
commented
There's at least one other UserVoice thread on this...
-
Matt Harper
commented
A couple of other suggestions for execution warnings: be able to choose "Don't show this warning again in this session" and "Don't show this warning again in this database".
When doing dev work I'm not usually bothered by these warning...when I'm in Prod however I always want to see them. -
Thomas Rushton
commented
(Based on support Request #65447)