Migrating indicator scores
The Performance Analytics Scores [pa_scores] table was split into two tables. This structure helps with processing large numbers of scores. You can migrate your scores from the old table structure to the new, using the score migration tool.
In Istanbul, the Scores [pa_scores] table was split into Scores Level 1 [pa_scores_l1] and Scores Level 2 [pa_scores_l2]. The pa_scores_l2 table contains the second-level breakdown matrix of scores and the pa_scores_l1 table contains all other scores. This separation of scores ensures optimal performance when collecting and analyzing scores, and enables larger sets of scores. New instances created on the Istanbul release or later use the new scores tables by default.
Instances created prior to Istanbul still use the original Scores [pa_scores] table after upgrading.
Migration Monitor
After beginning the migration, you can track the migration status by navigating to
If any errors occur during migration, contact Customer Service and Support to resolve the issue.
Delays in starting score migration
- Data collector jobs
- Collection cleaner jobs
- Scoresheet editing
Schedule the Performance Analytics scores migration
Schedule the automated migration process to move existing scores to the new table structure.
Avant de commencer
Pourquoi et quand exécuter cette tâche
Migrating scores improves performance and scalability of Performance Analytics. Migration should be performed during off-peak hours.
During migration you cannot collect, modify, or delete scores. Scheduled data collection jobs do not run during migration. After migration completes, check any data collection jobs that were scheduled to run during the migration, as these jobs were suspended.
- The scores migration can take several hours to complete, depending on the number of scores. Schedule the migration in a non-production instance and then carefully plan the migration in production.
- The original Scores [pa_scores] table is truncated 10 days after successful migration.