AllWe've Moved!
Please note that we have moved to our New Forum site.
Jason Neuman UCS Contacts Removal
Hello,
I've imported 2 Million + records into my test UCS db. I need to remove these records. What is the recommended approach for removal?
I've checked various eServices manuals as well as the KBs, but I'm not finding a solution. To be clear I need to remove the records from the underlying contact table and corresponding attributes in the contact attribute table. I would like to avoid truncating the tables or going through PSDK to do this.
If there is reference material, kindly point me to the appropriatre document.
Thanks in advance.
I've imported 2 Million + records into my test UCS db. I need to remove these records. What is the recommended approach for removal?
I've checked various eServices manuals as well as the KBs, but I'm not finding a solution. To be clear I need to remove the records from the underlying contact table and corresponding attributes in the contact attribute table. I would like to avoid truncating the tables or going through PSDK to do this.
If there is reference material, kindly point me to the appropriatre document.
Thanks in advance.
There is no other official and supported approach, because of the database changes are suggested and supported as well. According to the fact that your env is just LAB, you can easily try to make DB changes directly (of course with backuping DB before), but within any production environment this step will be just up to you and at your own risk (nobody will fix it).
From my point of view and according to my real-life experience, the best way is through the PSDK, where the data consistency is guaranteed.
HTH!
Regards,
--Jakub--
All Answers
There is no other official and supported approach, because of the database changes are suggested and supported as well. According to the fact that your env is just LAB, you can easily try to make DB changes directly (of course with backuping DB before), but within any production environment this step will be just up to you and at your own risk (nobody will fix it).
From my point of view and according to my real-life experience, the best way is through the PSDK, where the data consistency is guaranteed.
HTH!
Regards,
--Jakub--