NMSRECIPIENT.IRECIPIENTID reset | Community
Skip to main content
Prasanna_Soni
Prasanna_Soni
Level 4
February 8, 2022
Solved

NMSRECIPIENT.IRECIPIENTID reset

  • February 8, 2022
  • 2 replies
  • 1112 views

It appears we have taken over all values of NMSRECIPIENT.IRECIPIENTID and its time to reset? Anyone else faced similar issue ? 

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 Amine_Abedour

Hello @prasanna_soni ,

 

The OOTB schema nms:recipient is set to use the sequence ''XtkNewId'' from table ''XtkNewId'' (yes the sequence and the table share the same name 😋).

 

The default StoredProcedure that manage the sequences is set to loop back to negative idSeed if the current Seed is greater than 2 100 000 000 :

 

 

So, theoretically you do not have to worry about it 😁.

 

P.S : all the above is true for an instance under the build 8984 using Microsoft SQL Server for database.

 

last but not least, i would like to direct you to this article that explains the sequences exhaustion problem and how to avoid it : https://helpx.adobe.com/customer-care-office-hours/campaign/sequences-exhaustion-campaign-classic.html

 

Br,

 

Amine

 

 

 

 

 

2 replies

Amine_Abedour
Community Advisor
Amine_AbedourCommunity AdvisorAccepted solution
Community Advisor
February 8, 2022

Hello @prasanna_soni ,

 

The OOTB schema nms:recipient is set to use the sequence ''XtkNewId'' from table ''XtkNewId'' (yes the sequence and the table share the same name 😋).

 

The default StoredProcedure that manage the sequences is set to loop back to negative idSeed if the current Seed is greater than 2 100 000 000 :

 

 

So, theoretically you do not have to worry about it 😁.

 

P.S : all the above is true for an instance under the build 8984 using Microsoft SQL Server for database.

 

last but not least, i would like to direct you to this article that explains the sequences exhaustion problem and how to avoid it : https://helpx.adobe.com/customer-care-office-hours/campaign/sequences-exhaustion-campaign-classic.html

 

Br,

 

Amine

 

 

 

 

 

Amine ABEDOUR
    Jyoti_Yadav
    Jyoti_Yadav
    Level 8
    February 9, 2022

    Hi @prasanna_soni ,

     

    Are you keeping all the records since the start of application? If no, then you must have designed some cleanup workflow to delete recipient data after 'n' number of years.

    In that case, you can design another workflow to look for primary key gaps in your recipient table and then point out your Id to start counting for that point. Make sure the gap is sufficient enough to add data in the table without giving 'Primary Key Exhaustion'  or 'Primary Key already exist' error.

     

    Thanks,

    Jyoti

      Terms & ConditionsAccessibility statement

      Loading footer...