In the past we have encountered problems with the sync breaking in AX2009 because of Transactional Replication.
This is the problem where a new column added in AX adds the column with a dummy name and then renames it to the name you think you have created it as in the first place - it's always seemed odd to me as Transactional Replication is said to be supported yet AX/SQL Server (both Microsoft products) cannot cope with this simplest of schema modifications.
I am hoping that someone can reassure me that this has been addressed in AX 2012 / SQL Server 2014.
Any news or advise gratefully will be gratefully received.