Skip to main content
Luca_Lattarini
Level 9
Nov 18, 2021 6:31 AM UTC
Solved

Import Recipient Table and Other Custom Table information via FDA

Hello guys,

 

I am importing Recipient information by using FDA connector. My question is: is it better to link directly the Recipient table to the FDA Table Recipient (View) and change the Targeting Mapping or import the delta information via workflow and insert/update Recipient Table?

 

Thanks,

Luca

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
david--garcia
david--garciaAccepted solution
Level 10
Nov 19, 2021 12:20 AM UTC

Adobe recommends the latter approach in general.

 

I would personally opt for acc to ingest recipient data and other kind of data can be kept at source and used on ad-hoc/scheduled basis.

https://www.linkedin.com/in/david-garcia-uk/ | https://martech.network

2 replies

david--garcia
david--garciaAccepted solution
Level 10
Nov 19, 2021 12:20 AM UTC

Adobe recommends the latter approach in general.

 

I would personally opt for acc to ingest recipient data and other kind of data can be kept at source and used on ad-hoc/scheduled basis.

Translate
https://www.linkedin.com/in/david-garcia-uk/ | https://martech.network
LaurentLam
Level 5
Nov 22, 2021 12:32 AM UTC

Hello @luca_lattarini ,
Best practice is to just "import" required data.
There are 3 main reasons:
1- performance is better on your local database: your WKF will 
2- when you create a schema (so queryable) through FDA, there is a lot of intrusive objects that are created on the external database
  a- AC will have to create the OOTB AC Stored Procedures (in order to have the query expressions to work)
  b- AC will also create work tables (WKFxxxxxx) on the external DB when running a workflow that involve an activity on the schema
  c- AC will connect to the external DB with the clean up and try to delete work tables + some lists... When 2 AC instances are linked in FDA, it can be a high risk if FDA accounts are not correctly set (tables from AC on server B that deletes required tables on server A)
3- having tables on different DB is less resilient: you do not just have a risk on your DB + network but also on each external DB involved + network route to your DB. If everything is on your AC DB, your workflow will run, even with outdated data

Translate