Transact-SQL Syntax Supported by IntelliSense

 

Applies To: SQL Server 2016

This topic describes the Transact-SQL statements and syntax elements that are supported by IntelliSense in SQL Server 2016.

In SQL Server 2016, IntelliSense supports only the most commonly used Transact-SQL statements. Some general Database Engine Query Editor conditions might prevent IntelliSense from functioning. For more information, see Troubleshooting IntelliSense (SQL Server Management Studio).

System_CAPS_ICON_note.jpg Note


IntelliSense is not available for encrypted database objects, such as encrypted stored procedures or user-defined functions. Parameter help and Quick Info are not available for the parameters of extended stored procedures and CLR Integration user-defined types.

SELECT Statement

The Database Engine Query Editor provides IntelliSense support for the following syntax elements in the SELECT statement:

SELECTWHERE
FROMORDER BY
HAVINGUNION
FORGROUP BY
TOPOPTION (hint)

Additional Transact-SQL Statements That Are Supported

The Database Engine Query Editor also provides IntelliSense support for Transact-SQL statements that are shown in the following table.

Transact-SQL statementSyntax supportedExceptions
INSERTAll syntax, except the execute_statement clause.None
UPDATEAll syntax.None
DELETEAll syntax.None
DECLARE @local_variableAll syntax.None
SET @local_variableAll syntax.None
EXECUTEExecution of user-defined stored procedures, system stored procedures, user-defined functions, and system functions.None
CREATE TABLEAll syntax.None
CREATE VIEWAll syntax.None
CREATE PROCEDUREAll syntax.There is no IntelliSense support for the EXTERNAL NAME clause.

In the AS clause, IntelliSense supports only the statements and syntax that are listed in this topic.
ALTER PROCEDUREAll syntaxThere is no IntelliSense support for the EXTERNAL NAME clause.

In the AS clause, IntelliSense supports only the statements and syntax that are listed in this topic.
USEAll syntax.None

IntelliSense in the Database Engine Query Editor supports the following syntax elements when they are used in one of the supported Transact-SQL statements:

  • All join types, including APPLY

  • PIVOT and UNPIVOT

  • References to the following database objects:

    • Databases and schemas

    • Tables, views, table-valued functions, and table expressions

    • Columns

    • Procedures and procedure parameters

    • Scalar functions and scalar expressions

    • Local variables

    • Common table expressions (CTE)

  • Database objects that are referenced only in CREATE or ALTER statements in the script or batch, but which do not exist in the database because the script or batch has not yet been run. These objects are as follows:

    • Tables and procedures that have been specified in a CREATE TABLE or CREATE PROCEDURE statement in the script or batch.

    • Changes to tables and procedures that have been specified in an ALTER TABLE or ALTER PROCEDURE statement in the script or batch.

    System_CAPS_ICON_note.jpg Note


    IntelliSense is not available for the columns of a CREATE VIEW statement until the CREATE VIEW statement has been executed.

IntelliSense is not provided for the previously listed elements when they are used in other Transact-SQL statements. For example, there is IntelliSense support for column names that are used in a SELECT statement, but not for columns that are used in the CREATE FUNCTION statement.

Within a Transact-SQL script or batch, IntelliSense in the Database Engine Query Editor supports only the statements and syntax that are listed in this topic. The following Transact-SQL code examples show what statements and syntax elements IntelliSense supports. For example, in the following batch, IntelliSense is available for the SELECT statement when it is coded by itself, but not when the SELECT is contained in a CREATE FUNCTION statement.

USE AdventureWorks2012;  
GO  
SELECT Name  
FROM Production.Product  
WHERE Name LIKE N'Road-250%' and Color = N'Red';  
GO  
CREATE FUNCTION Production.ufn_Red250 ()  
RETURNS TABLE  
AS  
RETURN   
(  
    SELECT Name  
    FROM AdventureWorks2012.Production.Product  
    WHERE Name LIKE N'Road-250%'  
      AND Color = N'Red'  
);GO  

This functionality also applies to the sets of Transact-SQL statements in the AS clause of a CREATE PROCEDURE or ALTER PROCEDURE statement.

Within a Transact-SQL script or batch, IntelliSense supports objects that have been specified in a CREATE or ALTER statement; however, these objects do not exist in the database because the statements have not been executed. For example, you might enter the following code in the Query Editor:

USE MyTestDB;  
GO  
CREATE TABLE MyTable  
    (PrimaryKeyCol   INT PRIMARY KEY,  
    FirstNameCol      NVARCHAR(50),  
   LastNameCol       NVARCHAR(50));  
GO  
SELECT   

After you type SELECT, IntelliSense lists PrimaryKeyCol, FirstNameCol, and LastNameCol as possible elements in the select list, even if the script has not been executed and MyTable does not yet exist in MyTestDB.

Community Additions

ADD
Show: