DI-019 Data Integration - Court The extraction queries must be able to Queries do not have to be re-written Migration be re-usable, allowing the migrating between passes court to perform any data fixes that may be required multiple times Data Integration - Court Data cannot change until all data for a End user applications are turned off during DI-020 Migration court has been migrated the migration and aren't turned back on until migration is complete DI-021 Data Integration - Court The migration database must be The local court has a complete copy of the Migration transferred to the local court for their migration database. local conversion DI-022 Data Integration - Ongoing Transactional replication shall be used The ODS is updated by transactional Updates to update the ODS replication Data Integration - Ongoing Delete triggers shall be added to any Delete triggers exist on each table DI-024 Updates new table added to the ODS DI-025 Data Integration - Ongoing The delete triggers shall mirror the Delete triggers perform the same function Updates functionality of the other ODS Tables. as the other delete triggers DI-026 Data Integration - Purge Data stored in the migration database Purge scripts grab data from the migration shall be the source for purging data databases to determine which data in JIS to from JIS purge Data Integration - Purge Data stored in the migration database Once migration is complete, the migration DI-027 shall remain as a source for recovery of database is set to read only mode and kept purged data. available if needed for reversal of the purge Data Integration - Purge Purge of migrated data must be done Only records that are not marked as "do DI-028 after converting court is done not purge" will be purged from JIS and performing their conversion and subsequently the EDR. sending "do not purge" records
DI-019 Data Integration - Court Migration The extraction queries must be able to be re-usable, allowing the migrating court to perform any data fixes that may be required multiple times Queries do not have to be re-written between passes DI-020 Data Integration - Court Migration Data cannot change until all data for a court has been migrated End user applications are turned off during the migration and aren't turned back on until migration is complete DI-021 Data Integration - Court Migration The migration database must be transferred to the local court for their local conversion The local court has a complete copy of the migration database. DI-022 Data Integration - Ongoing Updates Transactional replication shall be used to update the ODS The ODS is updated by transactional replication DI-024 Data Integration - Ongoing Updates Delete triggers shall be added to any new table added to the ODS Delete triggers exist on each table DI-025 Data Integration - Ongoing Updates The delete triggers shall mirror the functionality of the other ODS Tables. Delete triggers perform the same function as the other delete triggers DI-026 Data Integration - Purge Data stored in the migration database shall be the source for purging data from JIS Purge scripts grab data from the migration databases to determine which data in JIS to purge DI-027 Data Integration - Purge Data stored in the migration database shall remain as a source for recovery of purged data. Once migration is complete, the migration database is set to read only mode and kept available if needed for reversal of the purge DI-028 Data Integration - Purge Purge of migrated data must be done after converting court is done performing their conversion and sending "do not purge" records Only records that are not marked as "do not purge" will be purged from JIS and subsequently the EDR.
EXHIBIT%20J%20-%20KCDC%20Data%20Replication%20HL%20Design.docx