FIX: Access violation when you split a partitioned table in SQL Server 2012
Content provided by Microsoft
Applies to: Microsoft SQL Server 2012 Service Pack 1SQL Server 2012 DeveloperSQL Server 2012 EnterpriseSQL Server 2012 ExpressSQL Server 2012 StandardSQL Server 2012 WebSQL Server 2012 Enterprise CoreMore
Consider the following scenario:
You have a partitioned table that contains an identity column in Microsoft SQL Server 2012.
The table is referenced by an indexed view.
You split a partition of the table by using the ALTER PARTITION function.
In this scenario, an access violation may occur.
This issue occurs because SQL Server 2012 typically checks whether the identity column increases or decreases when you split the partition. However, this operation fails. Additionally, this verification is not a required operation when you split a partitioned table.
Cumulative update information
Cumulative update 2 for SQL Server 2012 Service Pack 1 (SP1)
The fix for this issue was first released in Cumulative Update 2. 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:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1
Note 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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, remove the indexed view. Then, create the indexed view after you split the partition.