Viewing 4 posts - 16 through 19 (of 19 total)
I'd recommend looking at the SqlCommandBuilder.DeriveParameters method in .Net. That should give you a collection of named, typed params that you can just assign or read values to/from.
Easy!!
May 17, 2005 at 2:51 am
A simple QA approach - set QA to 'Results in text' mode and then run:-
SELECT SC.TEXT FROM SYSCOMMENTS SC INNER JOIN SYSOBJECTS SO ON SC.ID = SO.ID
WHERE SO.NAME LIKE 'proc%'...
April 28, 2005 at 3:44 am
Do you have return values from each stored proc that you can test within the job steps?
You could write to a debug table or OS file dependant on the return...
April 21, 2005 at 10:25 am
I came across a post somewhere else (http://www.sqlservercentral.com/columnists/RDyess/obtainingqueryexecutionplansthroughsqlprofilertrac.asp)
that talks about tracing procedures without using profiler.
It gets a bit complicated though, but may be worth trying if the performance impact...
April 20, 2005 at 6:24 am
Viewing 4 posts - 16 through 19 (of 19 total)