Hi Scott, I'm not sure whether I captured your question exactly. Say, if you want two fields to be taken at the same time to compose a key field, it can be done by combine the two fields into one "virtual" field then use it as the key field. For example
SELECT HQ_ORG_CODE||'|'||ORDER_PROJ_CODE||'|'||FORM_DATE As OID,* FROM tableX WHERE FORM_DATE >= ?
In this SQL, we concatenated the three fields with the splitter "|" into one "virtual" filed OID, then we can directly use OID as the key field because it will exist in the result set. Also, we can use SQL function to concatenate the fields, as below
SELECT STRING(HQ_ORG_CODE,ORDER_PROJ_CODE,FORM_DATE) As OID,* FROM tableX
Hope that helps
Indeed, we've talked with our client. We agreed that temporarily open audit log is OK for trouble shooting, while we will need to make audit/cleaning process a more formal process as part of their data quality control solution.
I'll refer to the example above for them in the solution we are working on. Thanks a lot .
Thanks guys. We are using audit log now to trace the deletions.
Both truncate table statement and delete statement are logged as SQL DELETE Statement in table %SYS.Audit. Of cause, after the audit of XDBCStatement was enabled, the size of Audit Database increased rapidly (I.E 300MB for 100000 insertions in a table of only 5 fields ).
Developers who want to trace SQL execution need to be aware of much more disk space consumption and prepare that in advance.
To leave a comment or answer to post please log in
Please log in
To leave a post please log in