The Future of Logical Records in SQL Merge Replication

Question

I am creating a new application that will use SQL Merge replication over very bad networks. It seems that the Logical Records feature will help to deal significantly with these network issues, ensuring that we can get complete “entities” replicated one after the other in separate transactions, and not in the table after table.

However, the documentation states

This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new developments and plan to modify applications that are currently using this feature.

What I cannot find in the documentation is a recommendation for what should be used instead to get similar functionality. Is there such a recommendation? If not an official recommendation, what did people come up with on their own?

Answer 1

The following quote was marked as correct Microsoft Tech Support on the same issue in msdn .

"... only the concept of Logical records is being deprecated.  
We can still define relationships using sp_addmergefilter @filter_type=1 ..."

If you read the sp_addmergefilter documentation , you will see that you can accomplish the same purpose of the deprecated function by using the join @filter_type = 1 filter (unlike the deprecated @filter_type = 2).