Transactional Replication with AX 2012 and SQL Server 2014

(0) Share

Report

Posted on by Community Member

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.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

nunomaia 25 Moderator on at

Like (1)

Report

Transactional replication is supported in AX with KB2765281, I think that fix is already applied in R3.

technet.microsoft.com/.../dd362068.aspx;MSPPError=-2147217396

I don’t know if the issue that you described still happens in R3.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

Offcourse you can use Transactional Replication in AX/SQL combination. But why should you enable it in a development environment? If you develop Ax in Dev environment without TR, import XPO or model, modelstore in test/UAT. You can test TR in that environment to avoid having this problem in the first place.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Cheers! I was wondering if anyone could enlighten me as to the details of KB 2765281.

I have asked our AX Support team to look it up. I assume it's not a SQL Server HotFix.

I keep getting 'Page not available' problems.

Perhaps I don't have access myself.

Was this reply helpful? Yes No
nunomaia 25 Moderator on at

Like (1)

Report

I have found it in

https://mbs2.microsoft.com/Knowledgebase/kbdisplay.aspx?WTNTZSMNWUKNTMMYMWMSYTMOWZPWLSWNKQXNMYZQQQOQVLKK

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

We attempted a data dictionary synchronisation on AX2012 in our sandpit environment and still we are experiencing the same sort of problems we have been encountering since we first attempted this with AX 4.0.

Whilst this looks to me like Microsoft's right and left hands not speaking to each other - I'm sure there must be others out there who have experienced this problem. There must be a workaround otherwise Transactional Replication cannot be truly said to be supported.

SP_RENAME is used during the synchronisation process but there are certain things like renaming columns that cannot be done on a table published for replication (or CDC).

This is a major issue if replicating tables with millions of rows as we really cannot afford the downtime to reestablish replication if we are forced to take tables out of replication for the purpose of releases.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Also tried this using the TFS approach. This fails too.

The way adding adding column/dictionary synchronisation works must surely be considered to be incompatible with replication and therefore a bug.

I will see if I can get it raised as one through our reseller.

Was this reply helpful? Yes No
Chris_Richards 10 on at

Like (0)

Report

John we are experiencing this same issue and would prefer to not have to remove tables and/or views from our transactional replication in order to successfully perform and AX Database Synchronization. Were you ever provided a resolution to this issue?

Was this reply helpful? Yes No