Focal Point
[CLOSED]Which will take less time : A computed column or direct database column?

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/8587086976

December 08, 2015, 12:14 AM
sandy2sagar
[CLOSED]Which will take less time : A computed column or direct database column?
Hi,

There is a scenario that I have to used a database column on the report, whereas it can be computed in .fex code too by using other database columns.
Here is my question arise:
Which will take less time : A computed column or direct database column? and Why?

Please suggests me.


Regards,
Sandy Sagar

This message has been edited. Last edited by: <Emily McAllister>,


WebFOCUS 7.6
Windows, All Outputs
December 08, 2015, 12:27 AM
Waz
I would think DB column, not knowing all the details of the calc.

You are just pulling the data.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

December 08, 2015, 04:36 AM
Darryl_uk
I would propose that if the column is on a table you would otherwise not read then the extra i-o would take longer than a calculation against data you are already getting in your data block. But this would so much depend on whether extra disk access would be required versus data in memory. If this is time critical I would suggest trying both and getting some stats out of the box. (I've had this in oltp systems where the server is performing thousands of tps against stringent performance criteria - then disk access can be a significant performance issue)


7.7.05 Windows.