Re-import of TmpV2 data from Julie's Export 2014-09-18

Original import of TmpV2 into the live Centralized_data.mdb went wrong. Julie provided a new export 2014-09-04. That import went wrong as well, so here instructions for new import with 2014-08-18 data. These are the instructions for the one-time import of her data into the live Centralized_data.mdb.

File location

The files for this process are stored in x:\CCMDB\z_archive\2014-09-18_Tmp_reimport

Steps

The following steps then have to be done on live data in a "pull" state

1. copy centralized_data.mdb to the directory containing the remaining files
2. use Access 2010 PC (too much data for 2003) to open tmp_to_centralized_importer.mdb with tasty pw
3. import data from L_TmpV2_cleaned_18Sept2014.xlsx
4. run query step2_delete_completes_and_vetteds and delete contents to eliminate all but incomplete records; close the query
5. run query step31_put_orphans_into_separate_table to put the orphans into table 2014-09-18_orphans (236 rows...)
   • there are a number of orphans in the .mdb that have become disconnected from their parent record in L_Log, likely due to location chagnes; this was flagged during analysis and decided to just segregate the records for now and have Pagasa correct later if needed. The records would already be in the correct format to cut-and-paste them into L_TmpV2 once the D_ID gets corrected.
6. run query step32_append_matches_to_L_TmpV2 to do the actual import.
7. move centralized_data.mdb back to the output directory on the Regional Server

possible future steps

If we need to reinstate any of the records that were orphaned:

1. open #File location\tmp_to_centralized_importer.mdb
2. open table 2014-09-18_orphans
3. correct the D_ID for the relevant records
4. cut-and-paste the records into an up-to-date copy of centralized_data.mdb