I'm trying to use TIBSqlMonitor as a centralized benchmarking and slowness (delay from request to
first response row)-detecting component for our already-large project. Not all of our SQL runs
through our own functions, particularly anything related to QR. Sadly, it seems whoever coded
TIBSqlMonitor (Jeff Overcash?) decided that 1000 or so characters would be plenty for any SQL,
which isn't the case (and of course it's a const, so I don't think I can just derive and override
the value.) Without the full SQL, it's hard to track down the source of the call, and therefore
what SQL or indices might need fixing. Any suggestions? I have the sourcecode, so I can technically
recode the darn thing to not have such a limit, but my pascal's a bit rusty and I was hoping maybe
someone else had already done so.

-Philip