Prepare to be amazed. Really.
What do you know about grouping sets? Not much?…
Let’s see how hard it is to build this query first. From the Databases tab, on the left, I right-click on the emp table and select Add to New Query. I keep checked only the DEPTNO, JOB and SAL shape items. I show only the Field, Lookup, Group, Sort and Format builder bars. I click on Page Size to turn paging off. (more…)
Here is why Query Xtractor users may call them LEFT/RIGHT JOIN, without being specific. You could not always tell if a diagram shape is at the left of the other joined shape. And you should not actually care, this is a SQL implementation detail. Leave it to us, to our SQL query generator, to determine if this will translate into a “a LEFT JOIN b” or “b RIGHT JOIN a”.
Grouping is great, but it should be just the beginning. How many times you had some aggregates (totals, counts etc), but could not immediately and instantly expand ANY row, to see what records have been actually considered together? In Query Xtractor, result rows of any GROUP BY query are designed to be further navigated this way!
It bothered me for a long time there was no data modeling tool to represent, in the conceptual view of a relational database model, many-to-many relationships with just a straight connector between the two tables and nothing more. With no required intersection table, as long as this was a physical level implementation detail.
Our suite may be the only such database tool on the market today that offers this important security level: making sure data and metadata are only “xtracted” from a database, and never altered (including deletions and insertions). Our customers will just drill-down on relational relationships the fastest possible way, looking for data. They will reverse engineer your database metadata and expose comprehensible and flexible data models as diagrams. But they may never, and they should never, alter whatever your connected databases may have.