SQL bridge and tag historian module

hello everyone,
when I buy the SQL bridge module, i can use the transaction and the named query? And no need for the tag historian module if I have knowledge in SQL to call a querry to binding a chart component for example right?

SQL Bridge module is only for the transaction groups. Named queries are a standard feature.

Tag historian module has some advantages for configuring history on many tags very quickly and handling all of the partitioning for you, plus I think Ignition Edge sync requires it.

But yes, you can do most of it with just transaction groups. And using a named query to read data for your trending.

3 Likes

Note that you won't be able to use Perspective's PowerChart component without the historian.

1 Like

So event if the tables are there, power chart won't load in the data? (are the functions disabled due to no licence?)

Actually, that's what the read only tag historian licence is for. Well, to read from a licensed tag historian really, but if you really wanted to script your own to mimic IA's, you could use that potentially... Good luck to those who inherit the system though!!

The Perspective PowerChart does its own queries via a history provider, and history providers depend on the historian module. PowerChart cannot accept custom datasets or series.

yes you are right but what the difference between power table component and use to combine table and chart component to poll trends from my table transaction in the database?

A lot of programming overhead, and your own solution for a tag browser.

Do able? Yes. Straight forward and trivial? No.

You might check out other third party charting modules, which provide more comprehensive charting solutions than the standard Timeseries and XY Chart components.