thanks Lars, we are seeing this when running the calc view from the SQL console as well as when running the stored procedure from the sql console. the same invocation varies drastically as he mentioned those times. do you know if there is any DB configuration that may be causing this? we have run the plan analyzer as well and are unable to see the cause other than it is a stored proc executing it instead of running the view directly. the view as Giri mentioned has 2 required input parameters which are in fact passed to the stored procedure as well.
↧