This content has been marked as final. Show 2 replies
HQ_METRIC_DATA is a view. The view includes all the HQ_METRIC_DATA_* (1h, 6h 1d etc) tables which means that it is GINORMOUS!
I presume you are tackling a similar issue to all of us. That is given the fact there is NO REPORTING TOOL anymore you are having to write custom code or jsp's to replace this very basic functionality.
Using the HQ_METRIC_DATA view for any queries is very inefficient and slow due to it's size.
The real mystery and something that has never been explained as far as I can tell is the tables named so:
Looking just from a logical naming perspective they would seem to refer to the age of the data making them great for development purposes (like only needing to query one smaller table of data for yesterday etc) but it turns out that data seems to rotate through these table seemingly at random. So one day, yesterdays data will be in 1d1s then tomorrow I might find yesterdays data in 3d1s or something
If we could understand how data flows through these tables then I am sure it would help us poor developers who are trying to replace functionality WE PAID FOR.