Using Progress® Analytical Tools Adam Backman White Star Software DONE-05:

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Outline ä List of available tools ä Using the tools ä Impact of running tools on the system ä Interpreting the data ä Taking action

© 2005 White Star Software DONE-05 Using Progress Analytical Tools List of Available Tools ä Progress monitor - promon ä Virtual System Tables - VSTs ä Database Analysis ä Chain analysis ä Index analysis

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Using the Tools - promon ä Command line tool promon promon ä Pros: Easy to use Nothing to write Low/no impact on the system ä Cons: No ability to customize No provision to run in batch No provision to output/save data

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Using the Tools - VSTs ä 4GL based tool ä Pros: Very customizable Ability to collect exactly what you are looking for Low/no impact on the system ä Cons: You need to write your own tool Determining the right VST is sometimes a challenge

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Special Options for Table and Index Statistic VSTs ä All VSTs are on by default but table and index statistics only display the first 50 entries (by number not by volume) ä Use the following options on broker startup -tablebase - The first table number to monitor -tablerangesize - The number of tables to monitor -indexbase - The first index number to monitor -indexrangesize - The number of indexes to monitor

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Record Block Summary RECORD BLOCK SUMMARY FOR AREA "Archived Ratings" : 151 Table Records Size Min Max Mean Count Factor Factor PUB.hsrad G PUB.hsrat G Subtotals: G RECORD BLOCK SUMMARY FOR AREA "Archived Comps" : 152 Table Records Size Min Max Mean Count Factor Factor PUB.hscma K PUB.hscmd G PUB.hscmp G PUB.hsgft M Subtotals: G

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Index Analysis INDEX BLOCK SUMMARY FOR AREA "Archived Ratings" : Table Index Fields Levels Blocks Size % Util Factor PUB.hsrad prradstat M prradstat M prrat G prrat G PUB.hsrat audit G audit G cmday G cmday G cmtbl G cmtbl G kkcus G kkcus G prrat G prrat G sltrn G sltrn G sylic G sylic G

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Impact of Running the Tools ä The information for both promon and VSTs is kept in memory anyway so the tools are just reading the data with little or no impact to the system ä DB analysis can have an effect on the system especially if you are tightly spec’ed on disk throughput capacity

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Interpreting the Data - promon ä What screens to use ä When to use them ä What does the data really mean ä How can I use it to take action

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Using promon ä What screen to use: ä Activity screen ä Block access ä When to run ä Beginning of the “day” ä Peak times ä End of the “day”

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Activity Screen

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Using the Tools - DB analysis ä Command line tool proutil -C dbanalys ä Pros: Only way to determine DB storage efficiency Low impact on the system Can be run while the system is up ä Cons: No historical storage of information No flexibility of output

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Block Access

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Interpreting the Data - VSTs ä Which VSTs to use ä When to use them ä What does the data really mean ä How can I use the data to take action

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Which VSTs to Use ä _TableStat - Table usage ä _IndexStat - Index usage ä _ActSummary - Activity information ä _Transaction - Active transaction listing ä _AreaStatus - Storage area information ä _UserIO - User data request activity

© 2005 White Star Software DONE-05 Using Progress Analytical Tools _TableStat ä Displays read, update, create and delete information about each table ä Don’t forget about -tablerangesize ä _TableStat-id = _File._File-Num FOR EACH _TableStat by _TableStat-Read DESCENDING: DISPLAY _TableStat. END.

© 2005 White Star Software DONE-05 Using Progress Analytical Tools _IndexStat ä Displays read, update, split and delete information about each index ä Don’t forget about -indexrangesize ä _ IndexStat -id = _Index._Idx-Num FOR EACH _ IndexStat by _ IndexStat -Read DESCENDING: DISPLAY _ IndexStat. END.

© 2005 White Star Software DONE-05 Using Progress Analytical Tools _ActSummary ä Akin to the activity screen from promon ä Need to do calculations to get differences ä Two free application (protop and VST dashboard) can show you how this is done. FIND FIRST _ActSummary. DISPLAY _ActSummary.

© 2005 White Star Software DONE-05 Using Progress Analytical Tools _Trans ä Good to find “old” transactions ä Could be used to alert the DBA if a transaction duration broke a threshold ä Long running transactions are generally not a good thing as they tend to grow the BI abnormally

© 2005 White Star Software DONE-05 Using Progress Analytical Tools _AreaStatus ä This allows you to know how full your areas is while the DB is up and running ä Record contains the total number and number of used (high water) blocks in an area ä If stored over time you could trend your storage and know when you will need to increase capacity in advance

© 2005 White Star Software DONE-05 Using Progress Analytical Tools _UserIO ä Total requests by the user ä Most writes should be done by the page writers ä No breakdown as to which tables are being accessed ä Good for initial track down of bad code

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Taking Action ä Immediate Action Things that can be changed on the fly ä Planned action Wait for a customary outage and make changes ä Advanced action Trending items to plan for future growth

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Immediate Action ä -spin ä Number of APWs ä Application code

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Planned Action ä Increasing broker parameters ä Increasing capacity (Disk, memory CPU) ä Changing application code

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Advanced Action ä Planning for growth ä Disk storage and throughput capacity ä CPU Utilization ä Memory utilization ä DB storage capacity ä Code efficiency

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Interpreting the data - DB analysis ä Should I do a chain analysis, a index analysis or both ä How often should I run the utility ä What does the data really mean ä How can I use it to take action

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Conclusion ä Lots of information available ä The utilities included in OpenEdge™ for free are great for a snapshot of how things are now ä For utilities that keep track over time you will need an additional product like Fathom Management or you can write your own

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Conclusion Continued ä Use promon to monitor during peak periods of activity or in isolation to determine program efficiency ä VSTs are the basis of Fathom Management and they can be used to determine the reliability and performance data about your database ä DB analysis should be run at least quarterly to determine the efficiency of the indexes ä DB Analysis can also be used to determine storage information for storage area split.

© 2005 White Star Software DONE-05 Using Progress Analytical Tools Questions