FIX: Error 602 when you run a stored procedure repeatedly in SQL Server 2012 or SQL Server 2014
Content provided by Microsoft
Applies to: Microsoft SQL Server 2012 Service Pack 2SQL Server 2012 DeveloperSQL Server 2012 EnterpriseSQL Server 2012 StandardMicrosoft SQL Server 2014 Service Pack 1SQL Server 2014 DeveloperSQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 EnterpriseSQL Server 2014 StandardSQL Server 2014 StandardSQL Server 2014 DeveloperSQL Server 2014 DeveloperSQL Server 2014 EnterpriseSQL Server 2014 EnterpriseSQL Server 2014 StandardSQL Server 2014 StandardMore
Assume that you use Microsoft SQL Server 2012 or SQL Server 2014. When you repeatedly run a stored procedure that retrieves data from a temporary table in a single session, you receive the following error message:
Error: 602, Severity: 21, State: 30.Could not find an entry for table or index with partition ID <partition ID> in database <database name>. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Note This issue is more likely to occur on a system that has many CPUs, for example, a computer that has 20 CPUs.
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: