Troubleshooting SQL Server 2014 Indexes (Part 2)
If you have problems with SQL Server 2014 indexes, review this troubleshooting checklist
to find potential solutions.
1. The error occurs when you try to create indexed view on a partitioned table that
has a clustered columnstore index.
This is the error message text: “Internal Query Processor Error: The query processor
could not obtain access to a required interface.” This bug was first fixed in Cumulative
Update package 3 for SQL Server 2014. You can download the Cumulative Update package 3
for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2984923
2. The error 2601 occurs when you update a table by using a bitmap index that
contains a partition key in SQL Server.
This error indicates that you cannot insert duplicate key, but the index is not unique
index and allows duplicates. This bug was first fixed in Cumulative Update package 4 for
SQL Server 2014. You can download the Cumulative Update package 4 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2999197
To work around this problem, you can enable trace flag 8690 to disable the
Spool operation.
3. UPDATE STATISTICS performs incorrect sampling and processing for a table with
columnstore index in SQL Server.
This problem occurs when a table has a clustered index and has no non-clustered index.
This bug was first fixed in Cumulative Update package 4 for SQL Server 2014. You can
download the Cumulative Update package 4 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197
To work around this issue, you can add a non-clustered index on the table.
4. The error 7105 occurs when you execute UPDATE on sparse column set while
ONLINE INDEX REBUILD is running on the same table.
This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 4
for SQL Server 2014. You can download the Cumulative Update package 4 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197
To work around this problem, you can schedule ONLINE INDEX REBUILD activity at a
different timeframe when such updates are not being executed.
5. The error 8654 occurs when you run “INSERT INTO … SELECT” on a table with clustered
columnstore index.
This is the error message text: “A timeout occurred while waiting for memory resources
to execute the query in resource pool”. This bug was first fixed in Cumulative Update
package 4 for SQL Server 2014. You can download the Cumulative Update package 4 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197
6. The view indexes are not visible in SQL Server 2014 Management Studio (SSMS 2014)
Object Explorer.
This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 5
for SQL Server 2014. You can download the Cumulative Update package 5 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
7. The error 35377 may occur when you try to access clustered columnstore indexes.
This is the error message text: “When MARS is on, accessing clustered columnstore
indexes is not allowed.” This bug was first fixed in Cumulative Update package 5
for SQL Server 2014. You can download the Cumulative Update package 5 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3011055
8. Maintenance Plan performs offline index rebuild for large object table even if
you select the “Keep index online while reindexing” checkbox in Maintenance
Plan Wizard.
SQL Server 2014 allows indexes containing XML, varchar(max), nvarchar(max), and
varbinary(max) columns to be created, rebuilt, and dropped as an online operation.
This problem occurs because Maintenance Plan does not take account of the new feature.
This bug was first fixed in Cumulative Update package 6 for SQL Server 2014. You can
download the Cumulative Update package 6 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047
9. Access violation may occur when you delete rows from a table that has clustered
columnstore index.
This problem occurs after you drop the first column of the table and then restart
SQL Server. This bug was first fixed in Cumulative Update package 6 for
SQL Server 2014. You can download the Cumulative Update package 6 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/3031047
To work around this problem, you should rebuild the clustered columnstore index.
10. The error 8646 occurs when you run DML statements on a table with clustered
columnstore index.
This error indicates that the index is corrupt or there is a problem with the current
update plan. This bug was first fixed in Cumulative Update package 6 for SQL Server 2014.
You can download the Cumulative Update package 6 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3031047