Microsoft distributes Microsoft SQL 2008 R2 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 R2 update release.
Consider the following scenario:
You create a transactional publication in which a table is published in a SQL Server 2008 R2 database.
You create a subscription to this transactional publication.
You run INSERT or DELETE statements against the published table.
You run an ALTER TABLE statement that contains a SWITCH PARTITION command on the published table.
In this scenario, the INSERT or DELETE statements incorrectly run against the new partitioned table on the subscriber. Therefore, the statements do not run against the same table on the subscriber as they did on the publisher as expected.
Note The new partitioned table was created by the SWITCH PARTITION command.
Cumulative update information
The fix for this issue was first released in cumulative update package 2. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2567714 Cumulative update package 2 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 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.
For more information about how to use partition switching to transfer data efficiently, visit the following MSDN website: