I have the same table in two different publisher databases, however in one database replication successfully replicates changes to a values case (upper to lower or lower to upper ) but in the other it does not.
Both pairs of tables are exactly the same at the publisher and subscriber. Specifically in terms of collation and the NOT FOR REPLICATION settings. There are also no triggers on any of the tables. All databases have the same database level collation and both databases live on the same publisher server and subscriber server respectively.
The articles appear to be the same with the same schema_options configured.
Replication does not appear to replicate any values over to the subscriber for the table not being updated. I determined this by hacking the subscriber UPDATE stored procedure to log all parameters passed in.
Is there an option somewhere I'm missing which defines how replication handles values set back to themselves but in a different case, and whether these values will be replicated or not?