Consider the following scenario:
- You enable the ALLOW_SNAPSHOT_ISOLATION option on a Microsoft SQL Server 2005, a Microsoft SQL Server 2008 or a Microsoft SQL Server 2008 R2 database.
- You perform a versioning operation on a table. For example, you update the table.
- You disable snapshot isolation level on the database.
- You update an index key column on a record that contains versioning information.
- You rebuild the online index on the table.
In this scenario, an assertion error occurs, and you receive the following messages in the SQL Server error log:
<Date><Time> <spid> * BEGIN STACK DUMP:
<Date><Time> <spid> *<Date><Time> <spid>
<Date><Time> <spid> *
<Date><Time> <spid> * Location: AppendOnlyVerStoreMgr.cpp:731
<Date><Time> <spid> * Expression: 0
<Date><Time> <spid> * SPID:<spid>
<Date><Time> <spid> * Process ID: 6328
<Date><Time> <spid> * Description: Cannot locate version record and page is not allocated. Status = 3
<Date><Time> <spid> *
<Date><Time> <spid> * Input Buffer 170 bytes -
<Date><Time> <spid> * ALTER INDEX <Table Name> ON <Index> REBUILD WITH(O
<Date><Time> <spid> * NLINE = ON)
This issue occurs because the versioning information for a new record of the index key is copied from the old record of the index key. Therefore, the error occurs when the index is rebuilt.
Cumulative update information
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2438347Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2438347/
)
Cumulative Update package 5 for SQL Server 2008 R2
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 2008 R2 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:
981356Â
(http://kbalertz.com/Feedback.aspx?kbNumber=981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
SQL Server 2005 Service Pack 4
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2464079Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2464079/
)
Cumulative update package 1 for SQL Server 2005 Service Pack 4
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 2005 fix release. Microsoft recommends 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:
2485757Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2485757/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2005 SP3
The fix for this issue was first released in Cumulative Update 12. For more information about how to obtain this cumulative update package for SQL Server 2005 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
2345449Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2345449/
)
Cumulative update package 12 for SQL Server 2005 Service Pack 3
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 2005 SP3 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:
960598Â
(http://kbalertz.com/Feedback.aspx?kbNumber=960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2413738
(http://vkbexternal.partners.extranet.microsoft.com/VKBWebService/ViewContent.aspx?scid=KB;LN;2413738)
Cumulative update package 11 for SQL Server 2008 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 2008 fix release. Microsoft recommends 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:
970365
(http://vkbexternal.partners.extranet.microsoft.com/VKBWebService/ViewContent.aspx?scid=KB;LN;970365)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467239Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2467239/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 2
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 2008 fix release. Microsoft recommends 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:
2402659Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2402659/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
To work around this issue, rebuild the index of this database by setting the
ONLINE option to
OFF in the query.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about online index operations, visit the following Microsoft website:
For more information about the details of online index operations, visit the following Microsoft website: