Time-outs and Arithmetic overflow errors

Feb 16, 2010 at 11:14 AM

I tried the tool (very useful!) but experienced some issues querying our large tracking database (prod system). I eventually had to download the code and make a few modifications to get it to work.


The SqlOrchTrackingShapeMetrics.txt file

  To avoid the Artithmetic errors: change AVG(cast(Duration) to  cast(AVG(cast(Duration as bigint)) as int)

GetCoverageShapeInfo method

  Add/change the sqlcommand timeout setting: cmd.CommandTimeout = 300;

Hopefully you can apply these fixes to the codebase.

Mar 19, 2010 at 11:16 AM

Hi Rudolf,

Thanks for pointing out the problem areas. We came across the timeout issues and i fixed them in a similar way. Didnt have the arithmetic overflow, but will incorporate that too. I have a release planned now (possibly a week or 2 max) and should have all this available.




Apr 1, 2010 at 1:10 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Apr 1, 2010 at 1:10 PM

Just a follow up . v1.2 does not have the CAST shown above. I will incorporate ASAP.