Result Set Limit behavior in DBeaver Community Edition

Goal: Reduce resource usage on low‑traffic databases

DBeaver’s Result Set Limit setting caps the number of rows fetched per query, aiming to prevent excessive memory consumption and network overhead on lightweight workloads.

Unresolved Decision

While the feature is documented, it is unclear whether the limit applies globally across all connections, can be overridden per query, or if it is enforced after data retrieval on the server side. This ambiguity affects cost‑optimization strategies for environments that rely on DBeaver for occasional maintenance tasks.

Key Questions

• Does the Result Set Limit setting in DBeaver Community Edition apply globally to all database connections, or can it be configured per connection?
• Can a user override the global limit using query‑level hints or session variables within DBeaver, and if so, how does this interact with the client‑side fetch size?
• Is the limit enforced at the server side before data transfer, or does DBeaver fetch all rows and then truncate the result set client‑side?