Recently I received an email from a reader… they didn’t quite see the value of using Query Manager vs. Query/400. I answered him via email but I also wanted to expand a little on my reply.
In some ways I agree, Query/400 is quick and easy. Believe it or not I still use it from time to time today.
But the real bonus to Query Manager is SQL. In fact any tool on the system that uses SQL is more efficient.
SQL is fast, it is the standard way to access, retrieve and modify data on the platform now.
SQL makes your life so much easier. Database admins from other platforms probably look at that in a weird kind of way since SQL is sort of synonymous with databases.
But if you have been around the platform like I have – SQL wasn’t always so and we used other tools to get things done. Remember using PFE?
Yeah PFE was sort of like the dark days before we had SQL on the 400.
SQL is just so much more efficient and it is faster. If you take a Query definition that joins multiple files and it takes some time to run, I can assure you by porting it over Query Manager, it will run faster… probably without tweaking the SQL statement at all.
You can also finesse the underlying SQL statement used by Query Manager. You can tune it. You can work with it. This cannot be accomplished with Query/400.
With SQL also comes a whole new bag of goodies that have no equivalent in Query… things like CASE, casts, and sub-queries.
Query Manager is not a glorious report building package with slick formatting and a nice GUI, but it is an excellent alternative to Query/400.
You probably already have Query Manager installed and licensed… along with the tools available on the system you can port your query definitions right over.