Edit

Share via

Identify issues with IntelliSense (SQL Server Management Studio)

Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW)

There are certain cases when the IntelliSense options might not work as you expect.

Conditions that affect IntelliSense

The following conditions might affect the behavior of IntelliSense:

  • There's a code error above the cursor.

    If there's an incomplete statement or other coding error above the location of the insertion point, IntelliSense might be unable to parse the code elements, and therefore doesn't work. You can comment out the applicable code to enable IntelliSense again.

  • The insertion point is inside a code comment.

    IntelliSense options aren't available when the insertion point is within a comment in your source file.

  • The insertion point is inside a string literal.

    IntelliSense options aren't available when the insertion point is inside the quotation marks around a string literal, for example:

    WHERE FirstName LIKE 'Patri%|'

  • The automatic options are turned off.

    Many IntelliSense features work automatically by default, but you can disable any feature.

    Even when automatic statement completion is disabled, you can use an IntelliSense feature. For more information, see Configure IntelliSense (SQL Server Management Studio).

Database Engine Query IntelliSense

The following issues apply to the SQL Server Database Engine Query Editor:

  • The IntelliSense functionality of the Database Engine Query Editor doesn't support all Transact-SQL syntax elements. Parameter help doesn't support the parameters in some objects, such as extended stored procedures. For more information, see Transact-SQL Syntax Supported by IntelliSense.

  • IntelliSense is only available when the Database Engine Query Editor is connected to an instance of the Database Engine from SQL Server 2008 (10.0.x) or later. IntelliSense isn't available when the Query Editor is connected to earlier versions of the Database Engine.

  • IntelliSense is turned off in the Database Engine Query Editor when the SQLCMD mode is set on.

  • IntelliSense functionality doesn't cover database objects created by another connection after your editor window connected to the database. If objects are missing from IntelliSense features such as completion lists, you can choose one of these three mechanisms to refresh the cache of objects for your editor window:

    • Select the Edit menu, select IntelliSense, then select Refresh Local Cache.

    • Use the Ctrl+Shift+R keyboard shortcut.

    • Disconnect your editor window from the instance of the Database Engine and reconnect.

  • Completion lists don't include database objects for which you don't have permissions. IntelliSense flags references to objects for which you do have permissions. For example, if you open a script written by someone else, any references to objects for which that person has permissions and you don't, are flagged as incorrect.

  • Completion lists might stop working if you lose the connection to the instance of the Database Engine. Reconnect to the instance.