DBeaver Data tab row fetch limits and low-traffic workload cost tuning

For a low-traffic workload, tuning DBeaver's initial row fetch in the Data tab is intended to reduce client memory and database load, but the default and override behavior vary by database driver and edition. Identical tables may display different row counts across connections, complicating cost control.

Raising or disabling the fetch limit removes the safeguard that protects client and server resources, potentially increasing consumption on large tables and negating the intended low-traffic benefit. Applying filters or sorting issues a new query subject to the fetch limit, though the interaction between client-side paging and server-side fetch size remains version-sensitive.

Because preference labels and default values differ between DBeaver versions and database drivers, and the row limit controls display fetching rather than the total result set when a custom SQL query requests more rows, the boundary between display paging and server-side execution cost is not always clear.

What is the documented behavior for the Data tab row fetch limit when a filter or sort is applied, and does the limit apply uniformly across database drivers and DBeaver editions? How does client-side paging interact with server-side fetch size when the row limit is adjusted, and where is this interaction documented for a version? Is there a supported way to configure the initial fetch size for low-traffic cost tuning without disabling the resource safeguard?