Any limits on how many foreign keys can we use on the Recipients schema? | Community
Skip to main content
G
god_prophet
Level 6
August 7, 2024
Solved

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

  • August 7, 2024
  • 1 reply
  • 620 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Pradeep_Kumar_Srivastav

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.

1 reply

Pradeep_Kumar_Srivastav
Community Advisor
Pradeep_Kumar_SrivastavCommunity AdvisorAccepted solution
Community Advisor
August 8, 2024

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.

    G
    god_prophetAuthor
    Level 6
    August 8, 2024

    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?

    Terms & ConditionsAccessibility statement

    Loading footer...