In the Netcool JDBC Probe it should be possible to configure a limit for the select statement

The Netcool Omnibus JDBC Probe uses a select statement to read event data from a table. The select returns everything that falls under the "where" condition - and all that data is ingested into the memory of the Probe for processing. When the number of records retrieved gets extremely high, the probe will fail with an OutOfMemory exception. Upon restart (by PA), it will either fail again, and/or, when the bkg-file already has been updated, it will loose events.
This can easily be avoided by limiting the number of records returned by the select statement. For MSSQL, this can easily be achieved by using a "select top 1000 x,y,z from a.b...". For DB2, Oracle, MySql/MariaDB and others, the limit must be post-fixed to the SQL statement (DB2: select x,y,z from a.b where condition FETCH FIRST 1000 ROWS ONLY).
Such a construct is currently impossible because the probe adds the condition for the MarkerColumn after the SQL-Statement resulting in a syntax error.
What I suggest is to add an "sql postfix" property which is pasted behind the final SQL statement by the probe. For above example, this would be "FETCH FIRST 1000 ROWS ONLY".
Apart form that, I'd also love to see a hint in the docs and the Support Guide on the fact that the probe reads everything from the select statement into memory.