Do I really need other these nodes in calculation views?

[former_member633778]

Knowing that SQLScript provides a lot more possibilities when modeling (window functions, statistics function etc) and also Table Functions can now be used as datasources (well for a while now 🙂 ).

My questions then :

1. Are there any technical benefits of modeling in graphical calculation views besides ease (i.e drag and drop)?

2. Are there any demerits to adopting a model as below for example?

table —> Table function (SQLScript) —> Calculation view —> SAC/BO

why would I need these other nodes (join, union, excepts) if I can achieve the same via SQL!!! There must be something

Are there any documentation / References or blogs or best practices?

Regards

[KonradZaleski · Accepted solution]

If you are using XS classic you can check out my blog post where I described pros and cons of using TF (cons regarding performance is not valid anymore, since Graphical CV are processed through the same optimization stack as SQL queries).

If you are using XSA I think the main drawback is only maintenace of TF (CV are much flexible for simple changes like adding/removing new fields)

[former_member633778 · Accepted solution]

thank you Konrad for your reply.

Yes, I have read your blog about TF. It is great news that performance is no longer an issue with TF. I actually did some tests with TF and CV and found very negligible differences in terms of performance.