Assume that you have a database that contains large columnstore indexes in Microsoft SQL Server 2014. When you execute DBCC CHECKDB command for the database, you receive the following error message from SQL Server error log:
The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset 0x00004a21310000 in file '<Disk Name>:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\XXXX.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
When you execute DBCC CHECKTABLE command for the table that has the columnstore index, you receive the following error message:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
At the same time, you receive the following error message in error log:
DBCC CHECKTABLE (<Table_Name>) executed by DomainName\UserName terminated abnormally due to error state 6. Elapsed time: 0 hours 3 minutes 36 seconds.
This issue occurs because of a defect in the prefetch mechanism of SQL Server columnstore index feature. This defect causes data pages to unnecessarily populate the snapshot database that would lead to a premature operating system 665 error.
NoteDBCC CHECKDB command automatically creates a database snapshot internally. You can encounter the same problem when you manually create a database snapshot and perform several queries that use the columnstore index.
Service pack information
To resolve this issue, obtain Service Pack 1 for SQL Server 2014.
For more information about SQL Server 2014 Service Pack 1 (SP1), see bugs that are fixed in SQL Server 2014 Service Pack 1.
Cumulative Update information
The issue was first fixed in the following cumulative update of SQL Server.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.