Hi All
When loading data from a DB, am I better off to set a custom property to hold the data and refrence that or create multiple named quiries and bind them to the objects themselves. e.g. If i am loading 24 hours of data to show some data with multiple columns, should I load it once and then just extract via script the data I want, or create a named query for each data point that I want and use that? How does it scale when having multiple displays showing the same data? Is the gatway loading the data and pushing to clients?
I'm wanting to graph some of it, show it as "max/min" data as well as gauges
S
There is no one right answer here, as it greatly depends on the data and how you prepare timestamp endpoints for your named queries. Specifically, if you arrange your endpoints to have zero minutes, zero seconds, and zero milliseconds, then you can expect named query caching to dramatically improve performance.
As for querying once and separately extracting with scripts: this moves workload from DB to gateway (not to browser client--it doesn't run scripts). This may or may not be desirable. If it makes sense for your specific workload, I would do it with expressions from my Integration Toolkit, not with scripts.
Share more details for more specific answers.