Expand my Community achievements bar.

SOLVED

Any limits on how many foreign keys can we use on the Recipients schema?

Avatar

Level 6

Hi there, 

Currently we have a lot of columns on our recipients extension schema. We're planning on moving most of the columns to other tables, to clean the recipients and just be more ordered.

In order for the users to do not use so many enrichement activities in their workflow; we would like to make 20 foreign keys to the recipients table (most of them 1 to Many). 

Are there any limits on this? Would connecting 20 schemas to recipients make it slow when in use in the workflows for the campaigns?

Thank you.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @god_prophet 

 

While there's no explicit limit on the number of foreign keys you can create in Adobe Campaign, introducing 20 foreign keys to the recipient's table could potentially impact performance. Here's why:

  • Database Performance: Each foreign key adds an index to the database, which can increase query complexity and potentially slow down data retrieval in WF.
  • Workflow Complexity: Managing multiple foreign keys within workflows can become more intricate, potentially impacting campaign execution time.
  • Data Consistency: Ensuring data consistency across multiple linked tables can be challenging, especially when dealing with large volumes of data.
  • Query Complexity: Queries and workflows that need to access data from multiple linked tables will become more complex, which will also affect performance.

Hope this helps.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @god_prophet 

 

While there's no explicit limit on the number of foreign keys you can create in Adobe Campaign, introducing 20 foreign keys to the recipient's table could potentially impact performance. Here's why:

  • Database Performance: Each foreign key adds an index to the database, which can increase query complexity and potentially slow down data retrieval in WF.
  • Workflow Complexity: Managing multiple foreign keys within workflows can become more intricate, potentially impacting campaign execution time.
  • Data Consistency: Ensuring data consistency across multiple linked tables can be challenging, especially when dealing with large volumes of data.
  • Query Complexity: Queries and workflows that need to access data from multiple linked tables will become more complex, which will also affect performance.

Hope this helps.

So, would be 5, 10 foreign keys ok?

For the rest of the tables, the best approach is to use Enrichment activities to make any joins we need?