In some exceptional cases, it may be necessary to perform a "dirty" read on a database. A "dirty" read occurs when a transaction reads data that has not yet been committed.
The Strategy SQL Engine does not have any settings for the transaction isolation level for warehouse table access. Strategy uses the default settings set at the database/ODBC level for transaction isolation. It is up to the driver/database to decide how the data is retrieved (dirty read, read committed, etc.).
If a dirty read is desired, it may be possible to use some database specific syntax and submit it as custom SQL prior to the execution of a report. This may be achieved by using the VLDB property, 'Report Pre-Statement', at either the report level or the project level, as desired.
An example of this workaround for an Informix database is shown below:
set isolation to dirty read;
select * from LU_TABLE;
NOTE:
Administrators should determine if a dirty read is an acceptable option in their environment.
