Posted: 23 Mar 2016 23:46 EDT Last activity: 17 Aug 2016 6:50 EDT
Maximum value of pyID
We have a requirement to maintain case details in data analytics platform for nearly 10 years. And our application is a Call center application with huge volume of cases per day. So this being the case we have concern about the maximum value of the pyID we can go upto.
What is the maximum value of a pyID? Are there any restrictions?
We in Pega have an app we've used for years, and what we did is, after the id's had crept up from W-1 to about W-222222 (some 6 digit number I don't know what exactly), we started with W-A1 and kept going, so now we're up to W-A30000.
pyid is defined as varchar(32) in pc_work table. Pending on the prefix of your work objects, conservatively, you are left with 10 to the power of 27 (assuming five characters prefix). You can then estimate your case volume for 10+ years to see if that is big enough. Remember this is only for one work type, not the summation of all types.
Besides pyID you also should consider table pc_data_uniqueid column, pylastreservedid which is "only" 18 digits.
However assuming you processed a call from everyone in the world (rough estimate 10billion) calls per day, you would still only need to store
36,500,000,000,000 in 10 years. or 14 digits worth, so you could do this for a very long time, and I think you would need to worry about the database needed to store the info more than running out of id numbers.
You may find additional information in the help documentation