I have got a big bunch of "SQL code" in stored proc., triggers, tables&views, undocumented and full of tricks.
Is there a tool to analyse code and map all this (who calls who, who uses who, and what for...).
This is (of course) for a SQL Server 6.5 database WHO IS NOT TO MIGRATE ANYWHERE SOON...
Furthermore, did someone used T-SQL stored proc. debug from within VB5 dev environnment (sdi.dll, automation and so on) ? I did'nt managed to get it work.
Thank a lot for any help.
Is there a tool to analyse code and map all this (who calls who, who uses who, and what for...).
This is (of course) for a SQL Server 6.5 database WHO IS NOT TO MIGRATE ANYWHERE SOON...
Furthermore, did someone used T-SQL stored proc. debug from within VB5 dev environnment (sdi.dll, automation and so on) ? I did'nt managed to get it work.
Thank a lot for any help.