Trace All Feeders Database Compression

One of the greatest benefits of running the standalone executable TraceAllFeeders, as opposed to running the tool in ArcCatalog, is the standalone performs a compression after each feeder.

As a reminder, below is the sequence of actions taken by TraceAllFeeders:

1. Attempt a compress action on the database. This allows TraceAllFeeders to indicate if it is unable to compress during the sequence of events. Compress is crucial to performance on large networks.

2. Identify all island features and set their FeederID, FeederID2, and FeederInfo values to reflect their island status.

3. Trace all features energized by any circuit source and set their FeederID values accordingly. This is done one circuit (or feeder) at a time.

4. Update the FeederSourceInfo field of the CircuitSource class to flag any feeders that possess loops or participate in a multiple-feed condition, based on results in step 3.

5. Identify all non-island features that are not energized by any circuit source and set their FeederID accordingly. This is done by resuming a trace from each feature that stopped a tracing action in step 3 (by virtue of its switching state and/or phase designation, as appropriate).

6. Identify all tie or terminal devices and modify their FeederID values to reflect their tie or terminal device status. These devices are identified based on the trace performed in step 3.

As stated, the tool attempts a compress at Step 1 to ensure it is able to perform the action. Then, save and compress are performed after steps 2, 4, 5, 6, and after each individual feeder’s update within step 3. All attempts to compress generate an event that appears as an entry in the application event log.

What Happens if it Cannot Compress?

When running the standalone, two consecutive attempts are made to compress before any editing is done. If either of the first two attempts fails, a message displays saying the compress is not succeeding, and it gives you the option of either continuing with no further attempts to compress or to abort the operation.

If you continue without compression, the application informs you it is tracing without compression in two ways:

• The title bar of the progress dialog reads "Tracing all feeders (no compress)...”

• Upon completion, the summary statistics include the message "TraceAllFeeders complete (without compressing).”

All attempts to compress, including the first two, generate an entry in the application event log when event logging is turned on. This is in addition to the “Continue Yes/No?” message that is issued when either of the first two compress attempts fails.

Failed Compression

If TraceAllFeeders hangs during compression, contact your Database Administrator to run the following command. This command executes compress on the database via the command line. Then, try TraceAllFeeders again.

   sdeversion -o compress -s <server_name> -i <service> -p <db_user_password>