Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You cannot disable the CDC feature if you drop the cdc.change_tables CDC system table in SQL Server 2008

FIX: You cannot disable the CDC feature if you drop the cdc.change_tables CDC system table in SQL Server 2008

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

↑ Back to the top

Symptoms

Consider the following scenario:
  • In Microsoft SQL Server 2008, you enable the change data capture (CDC) feature for a database.
  • You drop the cdc.change_tables CDC system table.
  • You run the sp_cdc_disable_db stored procedure to disable CDC.
In this scenario, you may receive the following error message:
Msg 208, Level 16, State 1, Procedure sp_cdc_disable_db_internal, Line 82 Invalid object name 'cdc.change_tables'.

Msg 266, Level 16, State 2, Procedure sp_cdc_disable_db_internal, Line 82 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.

Msg 266, Level 16, State 2, Procedure sp_cdc_disable_db, Line 0 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
If you try to re-enable CDC for the database by using the sys.sp_cdc_enable_db stored procedure, you may receive the following message:
Database '<Database>' is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view.

↑ Back to the top

Resolution

Cumulative update information for the release version of SQL Server 2008

The fix for this issue was first released in Cumulative Update 4 for the release version of SQL Server 2008. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
963036 Cumulative update package 4 for SQL Server 2008
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. 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

Cumulative update information for SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
969099 Cumulative update package 1 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. 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

To prevent this problem, avoid removing CDC system tables manually.


You can list many CDC system tables by reviewing the objects in the CDC schema. To do this, run the following query:
select * from sys.objects where schema_id=schema_id('cdc')
If the settings are in a damaged state and you cannot disable CDC, you can try to manually re-create the missing CDC tables and the indexes that are required for those tables. You can script those objects from a new dummy database in which you have successfully enabled CDC. Then, run the sp_cdc_disable_db stored procedure after correcting the missing objects.

More information about cumulative update package 4 for SQL Server 2008

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
963036 Cumulative update package 4 for SQL Server 2008

More information about cumulative update package 1 for SQL Server 2008 Service Pack 1

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
969099 Cumulative update package 1 for SQL Server 2008 Service Pack 1

↑ Back to the top

References

For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:

956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbfix, kbqfe, kbexpertiseadvanced, kbsurveynew

↑ Back to the top

Article Info
Article ID : 966306
Revision : 6
Created on : 9/29/2020
Published on : 9/29/2020
Exists online : False
Views : 74