S
Smartin
This might seem a bit absurd in the context of SQL, but I'm wondering if
anyone has felt the need to "step through [running SQL] code" in a
manner similar to that which is available in some HLL development
environments?
Sometimes I think it would be enormously helpful if I could examine a
query's response as it walks through the data sets, one row at a time,
setting breakpoints, watches, or what have you, in order to isolate bugs.
Unlike VB/VBA/.Net, SQL is an "all or nothing" proposition. Either it
runs or it doesn't; if it runs it may or may not return the desired
results. In the end I am left with rewriting the code or running
isolated cases to debug issues.
FWIW I have tried Jet's SHOWPLAN.OUT functionality but have not found
any value in it. It is entirely likely I don't know what to look for in
this, but this method requires a functioning query in the first place
anyway.
Any thoughts on this?
anyone has felt the need to "step through [running SQL] code" in a
manner similar to that which is available in some HLL development
environments?
Sometimes I think it would be enormously helpful if I could examine a
query's response as it walks through the data sets, one row at a time,
setting breakpoints, watches, or what have you, in order to isolate bugs.
Unlike VB/VBA/.Net, SQL is an "all or nothing" proposition. Either it
runs or it doesn't; if it runs it may or may not return the desired
results. In the end I am left with rewriting the code or running
isolated cases to debug issues.
FWIW I have tried Jet's SHOWPLAN.OUT functionality but have not found
any value in it. It is entirely likely I don't know what to look for in
this, but this method requires a functioning query in the first place
anyway.
Any thoughts on this?