I have users in InfoAssist who are attempting to create Year-to-Date reports. These reports have some BY fields in them. When this is sent as a query to the database, it adds the "ORDER BY" clause. Is there a way with such a large data set to allow the user to have BY fields but not send the "ORDER BY" clause to the database, essentially have WebFocus do the sorting instead?

What makes you think that would be advantageous?

Typically the servers where your databases exist have more memory and horsepower than the server with the WebFOCUS installation. Why would you think that WebFOCUS can sort your answer set more efficiently than the Database.

Well, someone please correct me if I'm wrong as I am far from knowing the "behind-the-scene" logic used by InfoAssist but my opinion is that InfoAssist *does not* create SQL code for you but "FOCUS" code instead, that is, TABLE FILE PRINT/SUM stuff based on what the user does on the front end.

You can potentially play with the SET ENGINE MSSQL (or whatever MS SQL Server uses) to try and disable optimization so order by and aggregations are not sent to the database but done by WebFOCUS, but I have to join j.gross and Alex to question why in the world you'd like to do that? Databases were designed precisely to do joins, aggregations, sorts, etc. and given that they're usually given more resources (CPU, memory, disk, etc.) than what the WebFOCUS servers get, I think you'd be better off letting WebFOCUS do its work and optimize the request the best way it can by leveraging the capabilities of your database.

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