Why does replication merge fail when setting the LOCK_ESCALATION table?

Question

We have a problem with merge replication. Our publisher is launching SQL Server 2008, and our two subscribers are working in 2005. Our publisher is trying to send a team to ALTER TABLE Foo SET (LOCK_ESCALATION)our subscribers. I think I remember reading that this command is new in SQL Server 2008, and if so, it makes sense that the command will fail on our 2005 servers. However, our merge replication is configured for 2005 compatibility.

Script 'scheme if object_id (N' [dbo]. [Users] ') is not null exec (' ALTER TABLE [dbo]. [Users] SET (LOCK_ESCALATION = TABLE) ')' cannot be passed to the subscriber.

Any ideas on why our publisher is trying to do this?

Edit: Our 2008 server compatibility level is set to "Sql Server 2005 (90)"

Answer 1

sql 2008 2005 . , , , 90 (sql 2005), , sql 2008 . , , . - 32 , .

, , . , SQL 2005. , 2008 2005 , ()

SQL dev a

Answer 2

, sql server 2005 , , , , .

: , , . - sysmergeschemachange , - :

script ', object_id (N '[dbo]. [Users]') null exec ('ALTER TABLE [dbo]. [] SET (LOCK_ESCALATION = TABLE) ')' .

, .