Red-gate Sql Prompt [updated]

Highlight a messy IN list → “Expand wildcard” to see every column. Or “Qualify object names” to add schema prefixes to every table/view. Or “Introduce alias” – it re‑writes the query with meaningful aliases. I used to do these by hand during code reviews. Now it’s a few keystrokes.

SSMS has built-in IntelliSense, but it is often slow and gets confused by complex syntax or database changes. SQL Prompt is significantly faster and "smarter." red-gate sql prompt

Users can define short aliases (e.g., ssf ) that expand into full code blocks (e.g., SELECT * FROM ), significantly reducing keystrokes. Highlight a messy IN list → “Expand wildcard”

After 5 years of fighting with SSMS, Red‑Gate SQL Prompt changed my life – here’s what I didn’t expect I used to do these by hand during code reviews

The most significant recent update is the integration of directly into the query window.

One of its most loved (and sometimes feared) features is its ability to detect . As you type, the tool underlines questionable practices—like using SELECT * or missing a WHERE clause on a DELETE statement—with a green wavy line. It doesn't just point out the problem; it explains why it's a risk and offers a one-click fix to "de-stink" your script. The Great History Savior

However, SQL Prompt’s true value lies in its ability to solve the chronic problem of inconsistent code formatting. In collaborative environments, different developers often have different styling preferences—some may use uppercase keywords, others lowercase; some may place commas at the end of a line, others at the beginning. This inconsistency degrades readability and complicates code reviews and version control merges. SQL Prompt offers a comprehensive formatting engine that can be customized to enforce a single, project-wide style. With a single keyboard shortcut, a developer can reformat an entire script, aligning indentation, line breaks, and case. This automated standardization transforms messy, ad-hoc queries into professional, maintainable artifacts, effectively turning code review discussions away from style debates and toward substantive logic and performance issues.