sf-apex-cursor

To paginate large SOQL result sets beyond OFFSET limits, use Database.Cursor to iterate up to 50,000,000 rows. This fetches pages of up to 2000 rows, preventing heap bloat and avoiding OFFSET-driven performance degradation in Apex.

Processing millions of rows without hitting heap limits requires using Database.Cursor to fetch pages of up to 2000 rows. Chaining Queueable jobs and passing the cursor ID across transactions iterates up to 50,000,000 records while keeping heap usage strictly per-page.

Yes, you can support infinite scroll in LWC using the PaginationCursor API. Exposing @AuraEnabled endpoints delivers paged query results directly to LWC UI components, replacing OFFSET-based UI pagination for large datasets.

Database.Cursor works with Queueable Apex by serializing cursor IDs and chaining Queueable jobs. This transaction-aware async chaining continues processing across jobs, enabling full result set iteration up to 50,000,000 records without exceeding transaction limits.

To migrate from Batch Apex to cursor-based iteration, open a Database.Cursor for your SOQL query, fetch pages of up to 2000 rows, and pass the cursor ID into chained Queueable jobs. This replaces heavy Batch Apex jobs while maintaining performance for large datasets.

Limitations of Database.Cursor include requiring strict lifecycle management (open, fetch, close) and capping fetch page sizes at 2000 rows. You must also design transaction-aware async chaining to process the maximum of 50,000,000 records effectively.