Follow

ID749 - eAuto Meter Reading Tables "Bloat" Prevention Overview & Sample:

 

Clean up your eAuto Meter Reading Tables to prevent the database from bloating (slowing your eAuto)

Jump to a specific section by clicking a link

Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts

 

Click to Subscribe

Overview

Overview

Bloat (too many records) in eAuto's Meter Reading tables are a serious source of performance issues for larger clients, or clients who have been on eAuto for a long while. This process runs monthly to purge unneeded Meter Readings from the tables (indexes are updated nightly), keeping those tables smaller and performing better. 'Unneeded' is defined as Meter Readings over X months old which are not tied to a Contract Billing or Service Call and are not the most recent read for the meter in question.

 

Run Schedule:  11th Each Month at Night (no options to run at different time due to server performance)

Type of Output: Email 

 

*  *  *

Sample

Sample

ID749Sample.png

 

*  *  *

Variables

Variables

ID749Variables.png

Variable W: Enter Number of months old a Meter Reading Group needs to be to qualify for deletion (in addition to other controls preventing deletion of reads which must remain). **Minimum is 24-months, even if you enter a value less than 24. Note that this process looks at the date the meter was created in the system and not the date of the meter.

 

*  *  *

Alert Functionality

Alert Functionality

1. Cleans up your eAuto Meter Reading Tables to prevent slowing down and lock up of eAuto (also improves your CEO Juice processes). 

2. We will start in Test Mode so your IT can choose a time slot for the initial run. Test results will send an email daily. Ideally this process fires in an after-hours window of at least 120 minutes during which NO SQL maintenance is running and no external integrations are inserting Meter Readings. **Your IT MUST BE INVOLVED and give approval on enrollment and schedule.

3. Once running live, we will purge Meter Reading tables on the 11th each month, with reminder emails sending on 8th, 9th, and 10th to give you plenty of notice. Indexes are updated nightly.

4. VariableW should be no less than 24-months. If you enter value less than 24, we will still only consider minimum of 24-months.

5. What eAuto activity we consider so as not to delete:

What meter readings are NOT deleted:

Most-recent Meter Reading for any Meter

Meter Reads marked as an Override

First (initial) Valid read for any Meter

Any Meter used as Beginning or Ending Meter on a Contract Billing

Most-recent Default Meter Reading for any Equipment

Most-recent Default Meter Reading on any Equipment Profile History record

Most-recent Default Meter Reading for the Host on any Equipment Profile History record

Expiration Start or End Meter Reading on any Contract Equipment Meter

First-billed or Last-billed Meter Reading on any Contract Equipment Meter

What Meter Reading Groups are NOT deleted (including any Meters in the Group):

Meter Reading Group attached to any Service Call

Start or End Meter Reading Group on a Contract Equipment

Warranty Expiration Meter Reading Group (deprecated in EA as of version 17.1)

 

*  *  *

 

Best Practices & Tips

Best Practices & Tips

1. You should have someone from your IT included as recipient to emails via your subscription.

SendToCCBCC.PNG

 

*  *  *

Related Alerts

Related Alerts

None at this time

 

*  *  * 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk