Incorporating data from the 2023 KKFU database into the 2024 version

KKFU Field officers can work with the new 2024 version of the KKICO System. However some are still working with the older 2023 version. Users of the 2023 version provide data which is added the the 2023 database, which has version differences with the 2024 version. 
Updates from the 2023 version cannot be incorporated directly into the 2024 version. Instead the updates are loaded to the main 2023 database. Then a procedure is run to load the data from the 2023 version into the 2024 version.

Steps needed to load 2023 data into the 2024 server

Backup Database	On the 2023 server, apply all updates from ICO Officers, and then backup the database In EDB Manager, find the "KK" database-session. Open the "Data" database. Click o "Backup Database" Enter a name for the backup file. Click OK
Restore Database	On the 2024 server, copy the backup file into the Backup folder, then Restore the "OldDB" database using this backup file. Select the "OldDB" on the new server. Click on "Restore Database". Ensure that the "Backup" Store is selected (where the backup file has been copied). Select this file. Click on the "Selection" tab to go to the next step.
Restore database "Selection" tab	On the "Selection" tab of the Restore database dialogue Ensure that the "Restore Catalog from Backup" check-box is ticked. Click "OK" to restore the database. NOTE: Take care during the "Restore" phase that you restore the "OldDB", if you restore the "Data" database by accident, you will overwrite the 2024 system.
Run the "Old-New UPDATE script.SQL"	Run the "Old-New UPDATE Script" to incorporate the data from the 2023 version into the 2024 version Ensure that the "Data" database is selected. Open the SQL file from disk. Review the contents of the file. Click "Execute" to run the script.

Notes on the UPDATE process

• The update process is slow. Running it in June 2024 required about 2 hours of time. This is because for every update/insert the procedure must test for the prescence of the row in the destination database before adding it. For this reason it is best to run the process at a time when the database is not active.
• The update process captures changes made by ICO Officers to their core tables in the database. The tables for which updates are captured are: Societies, People, Farmers, Staff, Phones, CoopTransactions, FarmFields, FarmerDeliveries, MembershipDetails, EditHistory. Other tables are not touched by the update process.
• The update process should not result in data being lost from "data clashes", but this cannot be guaranteed. Usually different ICO officers enter data for different farmers. However it is possible that one ICO Officer working with the 2024 system has gathered data for the same farmer as an officer working on the 2023 system. In most cases this would not be a problem. Data from both ICO officers would be added and saved. However, this could result in farmers having unusal number of records, for example duplicate Phones or FarmerDelivery data. If both officers edit the same data record (for example both edit the farmer's date-of-birth) then one update and over-write another.