We all know that only manipulation (DML) statements like insert,update and delete are logged in a database created with log facility. I would like to know why a sub-query involved SQL SELECT statement generates logical log data!
Example:
Test these commands in single user mode so that other sessions are not involved in the logs. Even a checkpoint also adds certain entries in the logical log. Execute following commands immediately after a checkpoint is completed or force a checkpoint using onmode -c before proceeding.
1. Note down the current log position and %used using onstat -l
2. Using dbaccess run SQL: select rowid from systables where tabid in (select tabid from syscolumns) or to have greater effect one can use any user defined tables having huge rows for sub-queries.
3. Note the %used and calculate the difference.
I have noticed this behaviour using IDS 7.31.UC5 for HP-UX 10.2 and IDS 2000 Version 9.20.UC1 for RedHat Linux 7.2
Regards,
Shriyan
"LIKE A SPRING ALL THINGS BIG STARTS SMALL"
Example:
Test these commands in single user mode so that other sessions are not involved in the logs. Even a checkpoint also adds certain entries in the logical log. Execute following commands immediately after a checkpoint is completed or force a checkpoint using onmode -c before proceeding.
1. Note down the current log position and %used using onstat -l
2. Using dbaccess run SQL: select rowid from systables where tabid in (select tabid from syscolumns) or to have greater effect one can use any user defined tables having huge rows for sub-queries.
3. Note the %used and calculate the difference.
I have noticed this behaviour using IDS 7.31.UC5 for HP-UX 10.2 and IDS 2000 Version 9.20.UC1 for RedHat Linux 7.2
Regards,
Shriyan
"LIKE A SPRING ALL THINGS BIG STARTS SMALL"