Transcript In The Data – Keeping it going - Wiki

2010 USER FORUM
In The Data – Keeping it going
Jaime Cummings & John Bonney
Topics
•
•
•
•
•
Superscreen
Mobile Device Manager
Enhanced Troubleshooting Techniques
Preventative Maintenance
Q&A
Superscreen
The SuperScreen is an administrative
tool that offers users the ability to
perform corrective actions and database
maintenance tasks, including:
•
•
•
•
Trim HH Session log data
Repost failed HH imports
Edit finalized transactions (orders,
transfers, purchases, etc…).
Validate records and Generate
“Key99’s”
NOTE: An access code (provided by the
R&A support team) must be obtained in
order to gain access to the superscreen
module.
Validate RecKeys
The Validate RecKeys options
serves two purposes:
1.
2.
To identify and repair
record numbers and names
that hold values that
violate interface
constraints.
To populate “Key99” values
for each record set. The
Key99 field allows for true
numerical record sorting
with reports.
NOTE: This is primarily used
after new data is converted
into eoStar from an external
source.
RecKey vs. Key99
Sorted by RecKey
Sorted by Key99
Handheld Log Trimmer
The HandheldLog table stores the raw
data uploaded to - and downloaded
from - each mobile device at the time
the HH or tablet is synced. To improve
system performance (route analyzer
access for example) and minimize
database growth, it is recommended
that the log table routinely be
trimmed of unneeded data.
Using the spinner button, choose the
number of months of data to keep.
Once this is complete, click the Trim
Logs button.
Handheld Order
Scanner
This panel looks for orders that may
not have been posted correctly in
either a pre-sell and/or an off-truck
route for the selected date range.
To use, select the from and through
date and then the checkboxes
correlating to the route type. Any
missing orders will appear in the
message box at the bottom of the
screen.
Ticket Meddler
The Ticket Meddler provides the ability to
make updates to transactions that are now
restricted from being updated via SQL. The
following tables may be updated via the
Superscreen:
•Orders
•Order Lines
•Purchases
•Item Transfers
•Item Transfer Lines
Depending on the table type (header or
detail) a ticket number or line item NID must
be provided (respectively) to identify which
rows are update candidates. These can be
provided as comma separated values, or by
providing a SQL script that gathers the
desired transaction numbers
NOTE: There is no way to undo a change in
ticket meddler. Use with extreme caution.
Mobile Device Manager
The Mobile Device Manager was
designed to:
•
•
•
•
swiftly deploy new software
releases to mobile devices
Assign invoice logos
determine which devices should
receive product image data
Provide an efficient way to
determine which license number
an employee is assigned to.
NOTE: Too many product images on
the mobile device may result in an
‘Out of Memory’ error.
Initiating the upgrade
Enhanced Troubleshooting Techniques
• Maintaining a Current Test DB
• Utilizing Database Snapshots
• “Push” Reporting (eoStar® Scheduler)
Maintaing a Current Test DB
•
Keep your test database fresh (as current as your last live backup) by using a simple SQL script in
conjunction with a scheduled job.
Database Snapshots
Snapshots are a read only, static view of the source database.
• Inserts and updates are not permitted.
• eoStar cannot connect to a database Snapshot.
How are Snapshots beneficial?
• Snapshots offer an instantaneous copy of a database.
• Multiple snapshots may be taken against a single database.
• Useful in testing environments (before/after queries).
• Snapshots may be used as an update source.
• Source databases may be restored from Snapshots.
Additional things to know:
• Snapshot databases occupy as much disk space as the source database.
• The snapshot feature is only available in SQL Server Enterprise editions.
Example Code:
“Push” Reporting
The eoStar® Scheduler may be used to schedule the
delivery of ION and SQL reports via email. Use
this functionality to become aware of potential
problems early on.
•
•
•
•
•
•
•
Invoice pricing adjustments
Missed stops
Erroneous entries (qty keyed in as 1222 vs. 12)
Plus-option record changes
HH Session Events
Inventory alarms
?
Example A
Example B
The “Alog” tables track all changes made to plus option records.
Preventative Maintenance
• Index Defragmentation
How do Indexes work?
Indexes greatly increase
query speeds by providing
quick access to rows in the
data tables, just like a book’s
index helps you find
information quickly within
that book.
Identifying Fragmented Indexes
SQL “DMV’s” (Dynamic Management
Views) can be used to quickly identify
indexes that are fragmented greater than
a chosen percentage.
In this example we see a listing of indexes
that are greater than 30% fragmented,
which meets the rebuild threshold
suggested by Microsoft.
On the Wiki: http://www.wikieostar.com/index.php?title=Rebuilding_I
ndexes
Rebuild Indexes Frequently
Consider utilizing a script (within a scheduled job) similar to the example below to keep your database
running smoothly
Discuss | Ask | Suggest
• Jaime Cummings
[email protected]
• John Bonney
[email protected]
Discussions online at www.wiki-eostar.com
Handheld Messaging
HH Message deployment
The Handheld Messaging feature
can be used to send broadcast
messages to specific mobile device
users.
Handheld Messaging
Message Administration
Administrators can quickly see
the employee “read” status for
each message that is currently
deployed. Messages can be
removed after the employee
has indicated they have been
read, or when they are no
longer valid.