NOTE: This article is intended for Yellowfin power users with familiarity with the back-end Yellowfin Configuration Database.
Disclaimer: Making changes to the Yellowfin configuration database without direction of the Support staff or Yellowfin issued documentation is NOT supported, and can damage your installation.
There are times when it is useful for troubleshooting or tracking down particularly complex reports to learn how long it takes an individual Yellowfin report to run. If you have access to the Yellowfin Configuration Database, there are a couple of fields that are useful to know about.
The data we're interested in lives in the ReportInstance table of the Configuration Database. If desired, you can join the ReportId column in this table to the ReportId column in the ReportHeader table in order to obtain the plaintext report name.
The ReportTime column represents the time of the day when the report was run. Its unit is seconds and the it shows the number of seconds past midnight server time.
For example, if ReportGMTDateTime is showing 20160329050945, of we conclude that this represents 29th March 2016, 05:09:45.
Therefore the ReportDate will show 2016-03-29, and ReportTime will show:
(5 * 60 mins * 60 secs) + (9 * 60 secs) + 45 secs
= 18000 + 540 + 45
The other column of interest is ReportDuration. This represents the time the report query takes to return from the database. (This is NOT the total time the report takes to fully render in the browser. Rendering in the browser will take longer for reports with large amounts of post processing elements like cross-tabs, analytical functions, etc.)
This value is measured in whole seconds. The datatype is an INT, and therefore can't show less than 1 second with precision. This is why a large number of values in this column may be 0.