Redgate Hub

All products

SQL Code Analysis (40)

All databases

How to (40)

SQL Prompt logo

Finding code smells using SQL Prompt: TOP without ORDER BY in a SELECT statement (BP006)

Using TOP in a SELECT statement, without a subsequent ORDER BY clause, is legal in SQL Server, but meaningless because asking for the TOP x rows implies that the data is guaranteed to be in a certain order, and tables have no implicit logical order. You must specify the order. Read more

SQL Prompt logo

Choosing Between Table Variables and Temporary Tables (ST011, ST012)

Phil Factor demonstrates the use of temporary tables and table variables, and offers a few simple rules to decide if a table variable will give better performance than a temp table (ST011), or vice-versa (ST012). Read more

SQL Prompt logo

Avoid use of the MONEY and SMALLMONEY datatypes (BP022)

Use of the MONEY and SMALLMONEY datatypes can lead to unintentional loss of precision, due to rounding errors, during calculations. It is generally far better to use the DECIMAL, a.k.a. NUMERIC, type. Read more

SQL Test logo

Effective Database Testing with SQL Test and SQL Cover

Julia Hayward describes the basics of how SQL Test’s code coverage can help uncover the darker, untested paths in your database code. Read more

SQL Prompt logo

When to use the SELECT…INTO statement (PE003)

SELECT…INTO is a useful shortcut for development work, especially for creating temporary tables. However, it no longer has a clear performance advantage and should be avoided in production code. It is better to use a CREATE TABLE statement, where you can specify constraints and datatypes in advance, making it less… Read more

SQL Prompt logo

Consider using [NOT] EXISTS instead of [NOT] IN with a subquery (PE019)

Phil Factor explains why you should prefer use of [NOT] EXISTS over [NOT] IN, when comparing data sets using a subquery. While there is no longer any significant performance advantage, using NOT EXISTS will avoid unexpected results when the subquery’s source data contains NULL values. Read more

SQL Prompt logo

Misuse of the scalar user-defined function as a constant (PE017)

The incorrect use of a scalar UDF as a global database constant is a major performance problem and should be investigated whenever SQL Prompt spots this in any production code. Unless you need to use these global constants in computed columns or constraints, it is generally safer and more convenient… Read more

SQL Prompt logo

Finding code smells using SQL Prompt: the SET NOCOUNT problem (PE008 and PE009)

Generally, you should prevent rowcount messages being sent, by adding a SET NOCOUNT ON at the start of every stored procedure, trigger and dynamically executed batch. Phil Factor demonstrates, and explains the nuances and exceptions. Read more

SQL Prompt logo

Finding code smells using SQL Prompt: old-style join syntax (ST001)

There are no advantages to using old-style join syntax. If SQL prompt identifies its use in legacy code, then rewriting the statements to use ANSI-standard join syntax will simplify and improve the code. Read more

SQL Prompt logo

Finding code smells using SQL Prompt: procedures that lack schema-qualification (PE001)

SQL Prompt will warn you if it spots use of EXECUTE, without specifying the schema in which the stored procedure resides, because it can cause slower execution times, or even result in running of the wrong procedure. Read more

Security and compliance

Database monitoring and observability

Database change management

Productivity and workflow automation

AI data readiness

Database modernization

Efficiency and cost optimization

Cloud migration and workload optimization

Redgate Flyway

Redgate Monitor

SQL Toolbelt Essentials

Redgate Hub

Finding code smells using SQL Prompt: TOP without ORDER BY in a SELECT statement (BP006)

Choosing Between Table Variables and Temporary Tables (ST011, ST012)

Avoid use of the MONEY and SMALLMONEY datatypes (BP022)

Effective Database Testing with SQL Test and SQL Cover

When to use the SELECT…INTO statement (PE003)

Consider using [NOT] EXISTS instead of [NOT] IN with a subquery (PE019)

Misuse of the scalar user-defined function as a constant (PE017)

Finding code smells using SQL Prompt: the SET NOCOUNT problem (PE008 and PE009)

Finding code smells using SQL Prompt: old-style join syntax (ST001)

Finding code smells using SQL Prompt: procedures that lack schema-qualification (PE001)

2026 State of the Database Landscape

Introduction to PostgreSQL for the data professional

Security and compliance

Database monitoring and observability

Database change management

Productivity and workflow automation

AI data readiness

Database modernization

Efficiency and cost optimization

Cloud migration and workload optimization

Redgate Flyway

Redgate Monitor

SQL Toolbelt Essentials

Cookies on red-gate.com