Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
Overview

...

Stage NumberStageCategorySummaryEnvironmentIterationsEstimated Person TimeEstimated Computer Time
1Import and parse reference dataset (Optional)ParsingThis optional step in the Bulk Loader process is to cross check an address for a match in a reference data set. If a source address is found in the reference dataset the address makes it to the next step. If not found the address is put aside in an exclusion set for later review.

Python 3

PostgreSQL / pgAdmin

Once per Bulk Loader process1 hour10 minutes
2Import, parse and filter source datasetParsingImport the dataset destined for the EAS. Parse and filter the set.

Python 3

PostgreSQL / pgAdmin

Once per Bulk Loader process90 minutes15 minutes

3

Geocode and filterGeocodingGeocode the set and filter further based on the geocoder score and status.ArcMapOnce per Bulk Loader process1 hour 5 minutes
4Export full set (single batch) or subset (multiple batches)GeocodingFor large datasets, create one of many subsets that will be run through the Bulk Loader in multiple batches.ArcMapOne or more batches for each Bulk Loader process30 minutes per batch5 minutes per batch
5Bulk Load batch (full set or subset)Bulk LoadingRun the entire batch or each subset batch through the Bulk Loader.

EAS <environment>(+)

PostgreSQL / pgAdmin

One or more batches for each Bulk Loader process1 hour per batch5 minutes per batch
6Extract resultsBulk LoadingExtract and archive the list of addresses that were added to the EAS . Also archive the unique EAS 'change request id' associated with this batch. Also archive the addresses that were rejected by the Bulk Loader in this batch.PostgreSQL / pgAdminOne or more batches for each Bulk Loader process1 hour per batch5 minutes per batch
7Cleanup and RestorationBulk LoadingClean up database, restore services and in the event of a failure, restore from backup.PostgreSQL / pgAdminOne or more batches for each Bulk Loader process1 hour per batch5 minutes per batch

...

Anchor
stage1
stage1
Stage 1 Import and parse reference dataset (Optional)

This optional stage is run once per Bulk Loader process. This stage can be skipped if the reference dataset is already available or if the optional 'filter by reference' step (Step 2.5) is skipped.

...

Anchor
stage3
stage3
Stage 3 
Geocode and filter

  •  

    Step 3.1 - Geocode source dataset

...

Anchor
stage4
stage4
Stage 4 
Export full set (single batch) or subset (multiple batches)

Note
titleA note about batches

Stages 4, 5 and 6 can be run one time with the results from Stage 3, or they can be run in multiple batches of subsets.

A major consideration of when to run the full set at once versus in batches is the number of records being Bulk Loaded.

The size of each Bulk Loader operation affects the following aspects of the EAS:

  • The disk space consumed by the database server
  • The EAS user interface section that lists addresses loaded in a given Bulk Loader operation
  • The weekly email attachment listing new addresses added to the EAS

For medium-to-large datasets (input sets with over 1,000 records) it is recommended that the process first be run on a development server to assess the implications of the operation. Where appropriate, perform the Bulk Loading process in batches over several days or weeks.

The remaining steps will document a single batch example iteration of a multi-batch process.

...

Anchor
stage5
stage5
Stage 5 
Run the Bulk Loader

(info) For a complete set of steps and background about the Bulk Loader, see also Running the Bulk Loader, a page dedicated to its input, operation and results.

...

Anchor
stage6
stage6
Stage 6 
Extract results

  •  

    Step 6.1 - Archive exceptions

...

  1. Get the unique EAS change_request_id created by the Bulk Load operation. The value of <change_request_id> will be used in the next steps to count addresses added to the EAS.
    1. Query the 'public.change_requests' table for the new 'change_request_id' value.

      Code Block
      languagesql
      firstline1
      titlechange_request_id
      linenumberstrue
      SELECT change_request_id FROM public.change_requests 
      WHERE requestor_comment LIKE 'bulk load change request' 
      ORDER BY change_request_id DESC 
      LIMIT 1;


    2. Save the file in the network folder dedicated to artifacts for the Bulk Loader iteration.
      • For example, R:\Tec\..\Eas\_Task\path\to\archive\bulkloader_YYYYMMDD\bulkloader\batch_002\change_request_id.csv
  2. Artifacts
    1. change_request_id.csv - The unique EAS change_request_id created by the Bulk Load operation.


  •  

    Anchor
    step6.3
    step6.3

    Step

    Step 6.3 -

    Archive new EAS address_base

    Archive new EAS addresses records

  1. Get all the base address records (including units) added to the EAS during the Bulk Loader operation..
    1. Query the public.address_baseaddresses table on the new change_request_id value.

      Code Block
      languagesql
      firstline1
      titlepublic.address_baseaddresses
      linenumberstrue
      SELECT activate_change_request_id, address_id, public.address_base.*
      * FROM public.address_base, public.addresses
      WHERE public.address_base.address_base_id = public.addresses.address_base_id
      AND public.addresses.address_base_flg = TRUE
      AND public.addresses.activate_change_request_id = <change_request_id>;


    2. Save the file in the network folder dedicated to artifacts for the Bulk Loader iteration.
      • For example, R:\Tec\..\Eas\_Task\path\to\archive\bulkloader_YYYYMMDD\bulkloader\batch_002\address_baseaddresses.csv
  2. Artifacts
    1. address_baseaddresses.csv - All the base address records (including units) added to the EAS during the Bulk Loader operation.


  •  

    Anchor
    step6.4
    step6.4
    Step 6.4 -

    Archive new EAS addresses

    Archive new EAS address_base records

  1. Get all the address base records (including units) added to the EAS during the Bulk Loader operation..
    1. Query the public.addressesaddress_base table on the new change_request_id value.

      SELECT * FROM public.addresses WHERE
      Code Block
      languagesql
      firstline1
      titlepublic.addresses
      linenumberstrue
      titlepublic.address_base
      linenumberstrue
      SELECT activate_change_request_id, address_id, public.address_base.*
      FROM public.address_base, public.addresses
      WHERE public.address_base.address_base_id = public.addresses.address_base_id
      AND public.addresses.address_base_flg = TRUE
      AND public.addresses.activate_change_request_id = <change_request_id>;


    2. Save the file in the network folder dedicated to artifacts for the Bulk Loader iteration.
      • For example, R:\Tec\..\Eas\_Task\path\to\archive\bulkloader_YYYYMMDD\bulkloader\batch_002\addressesaddress_base.csv
  2. Artifacts
    1. addressesaddress_base.csv - All the address base records (including units) added to the EAS during the Bulk Loader operation.

...

Compare the results of Stage 5 with the results from Stage 6.

  1. The number of base addresses found in the Stage 5 Analysis Step 5.6 (2) should be identical to the number of base addresses found in Step 6.3.

  2. The number of base addresses found in the Stage 5 Analysis should be less than or equal Step 5.6 (2) should be identical to the number of base addresses listed found in Step 6.4. (The Bulk Loader does not provide enough information in the the bulkloader.address_extract table to determine the exact number of new addresses added. But there is enough information to determine an upper limit.)

Anchor
stage7
stage7
Stage 7 
- Cleanup and Restoration

...

  1. If the Bulk Loader Process was run on the production server then restore services
    1. SKIP Turn on production-to-replication service
      • Re-enable database replication by restarting the database service on the replication server (DR PROD DB).


        Code Block
        languagebash
        titleStop PostgreSQL
        linenumberstrue
        sudo -u postgres -i
        /usr/pgsql-9.0/bin/pg_ctl -D /data/9.0/data start


    2. SKIP Turn on downstream database propagation service(s)
      • Resume downstream replication to internal business system database (SF PROD WEB).

        Code Block
        languagetext
        firstline1
        titlestart xmit
        sudo /var/www/html/eas/bin/xmit_change_notifications.bsh start


    3. Enable front-end access to EAS
      • Place the Web servers into live mode (SF PROD WEB, DR PROD WEB).

        Code Block
        languagebash
        linenumberstrue
        cd /var/www/html
        sudo ./set_eas_mode.sh LIVE


...