FIX: "sp_special_columns" returns incorrect result in SQL Server 2014 and 2016

Applies to: SQL Server 2016 Enterprise CoreSQL Server 2016 StandardSQL Server 2016 Developer


Assume that you create a primary key or a unique index that consists of more than one column in a table in Microsoft SQL Server 2014 and 2016. When you run the sp_special_columns system stored procedure on the table, not all the participating columns are returned.

Note This issue may occur if you have one or more columns deleted from the table.


Service pack information for SQL Server

This update is fixed in the following service packs for SQL Server:

       Service Pack 2 for SQL Server 2016

       Service Pack 3 for SQL Server 2014


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.