How can we help you today? How can we help you today?

Still no fix for queued updating replication triggers?

My biggest gripe with sql compare to date has been that although Red Gate advertises the option to exclude replication triggers, it still does NOT ignore the replication triggers on the subscriber side for transaction replication with QUEUED updating.

This would not be so bad, if triggers were elevated to a first class object, but since they are treated as an attribute of tables, this release does not help in my scenario.

Oh well, I guess I'll wait and see what version 7 brings. Maybe I'll have to just roll my own comparison tool by DOM parsing a an xml representation the SQL-DMO/SMO object model.

Was this an oversight again, or just 'not real high' on the priority list?
dakaratekid
0

Comments

1 comment

Sort by
  • Michelle T
    I couldn't find a previous report in the bug database for this issue, so I've raised it with the developers. I'm not certain that it will be fixed for the initial 6.0 release as our schedule is quite tight, but rest assured that it is now in the queue and will get looked at for this release and for any subsequant point releases if we don't manage to fix it in time for the major release.
    Michelle T
    0

Add comment

Please sign in to leave a comment.