HeZa

1 hour ago, Stefan Glienke said:

Hundreds of lines of code within one routine and you think that *with* is the problem? LOL

Yes, because with this WITHs it's very hard to do secure refactorings to solve other problems.

8 hours ago, Larry Hengen said:

@Hans J. Ellingsgaard  I am using SQL Server.  The query uses an inner join on about 5 tables, a left outer on one and a cross apply with a group by and order by on the results  Pretty much a worst case scenario.  Some of the criteria is not indexed, and due to the data layout requires a large # of reads.  Some work has been done on the query to optimize it, and it's now better, but the question remains; what are the best settings to use for FireDAC when the cost and row count of a particular query is not generally known at design-time, as is the case with many dynamically built SQL queries.

To give you one more idea to try: Use a sql window function to get the total count of all records as an additional column. Syntax for the column should something like this "count(*) over () as total".

SELECT - OVER Clause (Transact-SQL)

But I don't tried it by my self 🙂

On 8/12/2020 at 3:26 AM, Mike Torrettinni said:

Does anybody have a good rule or practical advice when to use class fields directly and when to pass them as parameters, when used in class methods?

If you call SearchByFieldname always with fFieldName as parameter then don't use a parameter because it is totally normal for a method to use fields of it own class.

On 4/26/2020 at 1:39 AM, Attila Kovacs said:

As I could not find anything measuring the InitUnits, and it has its reasons, I come up with this poor mans profiler: ...

Oh, I'm only seeing it now. Thanks for sharing it.

Is anybody aware if there is a profiler, which can profile the unit initialization, with output of unit name and time?