SQL Query VI Fetch Mode Change in LabVIEW 2022 SP1: Transaction Isolation Implications

When using the SQL Query VI in LabVIEW 2022 SP1 with Fetch Mode set to 'Stream As Needed', the VI returns data in configurable chunks while keeping the ODBC cursor open until the VI is closed or the Maximum Rows limit is reached.

The goal is to determine how this streaming behavior interacts with transaction isolation levels on a non‑autocommit connection, specifically whether the read lock is held for the entire cursor lifetime or released after each chunk, and what impact this has on concurrent update transactions. What lock duration does the VI impose when Stream As Needed is active? Does adjusting Chunk Size or enabling autocommit alter the lock scope? Are there documented limits or recommended settings to avoid blocking concurrent updates while still benefiting from chunked retrieval?