Question
TheHartford
CA
Last activity: 8 Sep 2023 17:53 EDT
Pega SLA table pr_sys_queue_sla to be migrated or not from onprem to pegacloud for inflight cases
we are having 4 applications hosted on different on premise servers , planning to migrate to one pegacloud server now.
we have included work, history, assignment, attachment , data tables for the data migration from on prem to cloud.
Question is what all tables need to be included for SLAs to be correctly working for inflight cases, is it just pr_sys_queue_sla table or any other table data?
If the answer is yes to pr_sys_queue_sla table, then since we are having multiple application data to be pushed to single table, is there a chance of same key issue and entry conflicting with other application data, key is pyItemId for this table, so there may be a chance of another application having same key, is that a possibility?
Pegasystems Inc.
CA
I think you're missing a few tables - Data tables and index tables. Please ensure that you list all the required tables before migration.
Answering your question - If I understand your question correctly, there won't be duplicate keys assuming all 4 applications are hosted in a single Premise instance.
TheHartford
CA
@RameshSangili my question was only around SLA related tables, rest all we handled for migration.
4 applications are not hosted in single on premise, they are on 4 different onpremise, that was the reason for my question on duplicate keys.