Hi,
RGDT Vs. Dynamic SQL ?
In case Dynamic SQL exists in a SP, no dependency trace can be generated unless all the possible combinations (so far at table level) are explicitly written in a never reachable part of the code.
What about a special section (marked by standard and special comment characters) to include these statements?
e.g.: /*RGDTxyz Select aaa from aaa_table RGDTxyz*/
CRUD (Create/Read/Update/Delete)
sysdepends helps in determining if a table is "read" and/or "updated", but not truncated or altered or SP is not part of the DB
RGDT is already capturing tables used by DML/DDL commands within SP; would it be possible to provide this commands in the UI and in the XML output?
(and extend it to columns when column level will be added...?)
Thanks
LF
RGDT Vs. Dynamic SQL ?
In case Dynamic SQL exists in a SP, no dependency trace can be generated unless all the possible combinations (so far at table level) are explicitly written in a never reachable part of the code.
What about a special section (marked by standard and special comment characters) to include these statements?
e.g.: /*RGDTxyz Select aaa from aaa_table RGDTxyz*/
CRUD (Create/Read/Update/Delete)
sysdepends helps in determining if a table is "read" and/or "updated", but not truncated or altered or SP is not part of the DB
RGDT is already capturing tables used by DML/DDL commands within SP; would it be possible to provide this commands in the UI and in the XML output?
(and extend it to columns when column level will be added...?)
Thanks
LF