Yes I agree, SQL is really powerful and helpful.
But also the build in “hopping” features help in certain scenarios much more efficient.
With hopping feature I mean things like the Traceability View, Find in Project Browser, Find in all Diagrams…, …, especially when you try to discover things of a certain element as starting point.
For instance if I select a transition in a state machine I can discover that the related trigger is of type signal with its the related signal (first hop). Next hop would be going to that signal, where the “Find in Project Browser” feature would certainly be nice, but is not offered in the properties dialog.

Managed this second hop e.g. with Search in Model (SQL) the traceability window shows all send signal actions sending that signal (third hop). By "Find in all Diagrams..." I am able to find when the send signal action is fired in the activity (forth hop).
Such a hopping with some simple “Search in Model” bridges work for me in many scenarios but in cases my staring point is a Trigger (maybe some other elements as well) I am kept alone.