FIX: Error message when you synchronize data for a transactional publication in SQL Server 2008: "Procedure or function 'sp_MSins_dbo<TableName>_msrepl_ccs' expects parameter '@c7', which was not supplied"

Consider the following scenario. In Microsoft SQL Server 2008, you configure a transactional publication. You add a table that contains a computed column to the publication as an article. The table has a composite primary key that contains the computed column. When you synchronize data, the Distribution Agent fails, and you receive the following error message in the Replication Monitor:

In the scenario that is described in the "Symptoms" section, when a concurrent DML statement is pending and a snapshot is being created, a specific stored procedure that is named sp_MSins_dboTableName_msrepl_ccs is created to propagate the DML statement. A required parameter is not passed to the stored procedure when the Distribution Agent calls the stored procedure. Therefore, the Distribution Agent fails.

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 2008, click the following article number to view the article in the Microsoft Knowledge Base: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:

To work around this issue, use one of the following methods:

• Do not create the snapshot when a DML statement is running.
• Modify the table schema so that the computed column is not included in the primary key.
• Change the replication settings for the article. To do this, set the INSERT delivery format option to INSERT statement instead of to Call <stored procedure> in the Article Properties dialog box. By default, the the INSERT delivery format option is set to Call <stored procedure>.
• Create a custom stored procedure that perform the insert operation. Publish that stored procedure so that any call to that stored procedure will be replicated.
• Synchronize data by using a backup. For more information, visit the following Microsoft Web site:
  http://msdn.microsoft.com/en-us/library/ms151705.aspx (http://msdn.microsoft.com/en-us/library/ms151705.aspx)

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

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:

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: 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: 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: