Suggest an Idea

[iFahm]

Hi,

Currently Attunity Replicate will store the Change Tables (with suffix __ct) on the same schema as the original Table in Target DB. And it makes the number of objects in Source DB and Target DB are not same. 

And it also impact to the user privilege in Target DB, e.g. user A could access the original Tables, user B only could access the Change Tables.

We need an option in which schema the Change Tables should be stored in the target DB.

Thanks,

iFahm

[Ola_Mayer]

Thank you for your feedback. We are collecting input from additional customers.

[gdoyle]

Any update on this? Currently trying to put our change tables into a separate schema than our full load schema. Tried doing the global rule but no luck. 

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.