When using SQL pass thru is it good to directly apply filters (WF where conditions) on SQLOUT or is it better to save SQLOUT as HOLD and then apply filters? This is performance wise..

Thanks

This message has been edited. Last edited by: Kerry,

Hi!

As a rule, your filters should be applied at the earliest possible point. So, put as many as you can right in the SQL, then, when you TABLE sqlout, add whatever else you can there.

There are exceptions, which you'll find as you work with your data - sometimes a filter in an SQL statement will produce a sub-optimal execution plan for the SQL, and it will actually end up being more efficient to pull a large data set with SQL and then filter it in WebFocus.

Hope that helps!
Rob

Thanks Rob. I will try that. And can you help me with one thing.


I am passing multiple values from listbox to webfocus procedure which is a SQL query. How to add it as a filter to SQL query. If its one value I don't have any problem. If its multiple, there is problem with quotes etc. Do you have any dialog manager code for this?

Thanks

Hi Enigma,

It is good to apply filer values in SQL query itself rather than you do on the SQLOUT.
Thatz the better way for higher performance.

But there are few scenarios you need to do that in WF. As said by Rob is one...

Other one... If you have multiple select parameter in your dashboard, you cant directly assign that to a where clause variable in Query(1 OR 2 OR 3). You need to frame the variables as per the DB need. In such cases that can be done as part of SQLOUT.

Pass it to SQL SP

Yes, you can pass multiple values to the Stored Proc...

Thanks tom. But I figured it out myself. Its somewhat similar to this..thanks all..