Symptoms
Assume that you have some partitioned tables in Microsoft SQL Server 2012. You try to build a columnstore index on the partitioned tables. In this situation, the build operation may fail and you may encounter an out of memory error. Additionally, the following error is logged in the SQL Server error log:
<Date><Time> spid# Error: 701, Severity: 17, State: 193.
<Date><Time> spid# There is insufficient system memory to run this query.
Note The issue typically occurs when there are many partitions and concurrent threads that build the columnstore index.
Resolution
Cumulative update information
Cumulative update 4 for SQL Server 2012 Service Pack 1
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2833645 Cumulative update package 4 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around the issue, minimize the value of max degree of parallelism (MAXDOP).
