Quoting each claim next to its docs page made this easy to trust. Two additions for Pattern A at the 80,000-row scale. Since you already sort on a unique key, keyset paging is an option: WHERE ORDER_ID > last_seen_id ORDER BY ORDER_ID LIMIT 200, then carry the last ORDER_ID of each page into the next query. Inserts and deletes no longer shift the pages, and Snowflake does not have to skip past an ever larger prefix on each of the roughly 400 calls. For the "keep the data still" problem, Time Travel gives a fixed snapshot without copying anything: capture one timestamp before the loop and add AT(TIMESTAMP => that value) to the table in every page query, as long as it stays inside the table's retention period.
HK
Hayrullah Kar
Founder & Automation Strategist @MageSheet | Google Apps Script & AI Specialist.
Quoting each claim next to its docs page made this easy to trust. Two additions for Pattern A at the 80,000-row scale. Since you already sort on a unique key, keyset paging is an option: WHERE ORDER_ID > last_seen_id ORDER BY ORDER_ID LIMIT 200, then carry the last ORDER_ID of each page into the next query. Inserts and deletes no longer shift the pages, and Snowflake does not have to skip past an ever larger prefix on each of the roughly 400 calls. For the "keep the data still" problem, Time Travel gives a fixed snapshot without copying anything: capture one timestamp before the loop and add AT(TIMESTAMP => that value) to the table in every page query, as long as it stays inside the table's retention period.