Hi Guys,
Just encountering a issue when using backup&restore to initialize a subscription where the publisher table contains identity column (and configured as "Not for replication"). As you known, after restoring the backup on the subscriber side, the identity property will be left. Under this situation, SQL Server tries to create the "sp_MSupd" stored procedure which tries to update this column. Did you try to initialize a subscription with backup&restore method, and the publisher table contains an identity column as primary key? If so, can you share your solution?
彼节者有间，而刀刃者无厚；以无厚入有间，恢恢乎其于游刃必有余地矣！