Refreshing IntelliSense in SQL Server Management Studio (Ctrl+Shift+R)

If you regularly develop in SQL Server Management Studio (SSMS), you have almost certainly encountered IntelliSense showing incorrect red underlines beneath valid database objects.

A common example is creating a new table, view, stored procedure or column, only for SSMS to insist that it does not exist. The SQL executes successfully, but the editor continues to report errors.

In most cases, the database is correct. IntelliSense simply hasn't refreshed its local cache.

Refreshing IntelliSense

Rather than closing and reopening SSMS, simply press:

Ctrl + Shift + R

This rebuilds IntelliSense's local metadata cache for the current database. Once complete, the editor recognises newly created or modified objects and the incorrect error markers usually disappear immediately.

It is a keyboard shortcut well worth remembering if you spend a lot of time writing SQL.

When Should It Be Used?

Refreshing IntelliSense is useful after:

Creating a new table or view.
Adding, removing or renaming columns.
Creating or altering stored procedures or functions.
Making schema changes from another query window.
Pulling down schema changes from source control.

Essentially, any time the editor appears to know less about your database than SQL Server itself.

What It Doesn't Do

Refreshing IntelliSense only updates the editor's metadata cache.

It does not:

Recompile SQL code.
Refresh Object Explorer.
Update execution plans.
Fix genuine SQL errors.

If the red underlines remain after refreshing IntelliSense, they are much more likely to represent a real problem with the query.

Why Doesn't SSMS Refresh Automatically?

That is a question many SQL Server developers have asked over the years.

This behaviour has existed for a remarkably long time and has survived numerous SQL Server and SSMS releases. Microsoft has never publicly described it as a bug, so it is probably more accurate to call it a design limitation or simply one of those long-standing quirks that every SQL developer eventually learns to work around.

There are probably sensible technical reasons for this. Continuously monitoring every possible schema change could introduce unnecessary overhead, particularly when multiple query windows or databases are involved.

That said, it still feels slightly odd that in an era of cloud databases, AI-assisted development and increasingly intelligent tooling, SSMS occasionally needs to be reminded that the table you created five seconds ago actually exists.

Perhaps it has simply become one of those "if it isn't broken enough, don't touch it" features.

Summary

If IntelliSense starts insisting that valid objects do not exist, don't assume your SQL is wrong.

Press Ctrl + Shift + R to refresh IntelliSense before spending time investigating errors that may not actually exist.

It only takes a second, and it is considerably quicker than closing and reopening SSMS—which, if we're being honest, is how many of us discovered this shortcut in the first place.