I love SQL Prompt, and it’s one of my favorite tools from Redgate. However, if I’ve made a mistake, I just hit enter, take the default, and then fix things. If I want to clear a table, and sometimes I do in demos, I click “Execute”. This is exactly what I need to prevent me from doing something stupid that I didn’t mean to do. I could turn off the warning, but I love it. Or in production, where it’s happened a few times. I can’t tell you how many times I’ve done this in a presentation. What if I highlighted just part of a script? This made me pause in front of the audience for 10 seconds while I read it, but I clicked “Execute anyway”, things worked, and I went on. There are deletes, and in this case they don’t matter. I’ve got multiple items without WHERE clauses in the script. In the middle of my SSMS window was a warning. While demoing some tSQLt stuff, I wanted to show how to install the framework.

In this case, I got an unexpected surprise.

The team led by David and Aaron are always adding cool new features, and have almost never broken my flow, so I usually take the changes they’ve made whenever they appear.

I upgraded my SQL Prompt recently, mostly as a habit. SQL Prompt will be yours as well if you give it a try. I’ve got a series of SQL Prompt posts here on little things I like. I work for Redgate and write about products.

Sql prompt where clause warning