If i execute a query that take a long time how can i tell which part of the
query is causing the problem ?

Is there anyway to step a query ?

Profiler just shows execution start & stop.

If i have a complex script to deploy for example, it would ful to know
which part its on ... or using queries with queries.

I guess the obvious answer is to break it up into different scripts.

Thanks for any info.
Scott

A while ago I wrote an addition to sp_who2 called sp_who3 which does
just this. When sp_who3 is run with a spid it will spid on a lot of
information including the current command within the batch which is
being run.

More info can be found here
http://itknowledgeexchange.techtarge...alled-sp_who3/

Denny

On Thu, 17 Jul 2008 16:20:00 +0100, "Scott" <scott_lotus@yahoo.co.uk>
wrote:

>If i execute a query that take a long time how can i tell which part of the
>query is causing the problem ?
>
>Is there anyway to step a query ?
>
>Profiler just shows execution start & stop.
>
>If i have a complex script to deploy for example, it would ful to know
>which part its on ... or using queries with queries.
>
>I guess the obvious answer is to break it up into different scripts.
>
>Thanks for any info.
>Scott
>

thank you.

Scott
See an execution plan of the query.



"Scott" <scott_lotus@yahoo.co.uk> wrote in message
news:ujhFWCC6IHA.1420@TK2MSFTNGP06.phx.gbl...
> If i execute a query that take a long time how can i tell which part of
> the query is causing the problem ?
>
> Is there anyway to step a query ?
>
> Profiler just shows execution start & stop.
>
> If i have a complex script to deploy for example, it would ful to know
> which part its on ... or using queries with queries.
>
> I guess the obvious answer is to break it up into different scripts.
>
> Thanks for any info.
> Scott
>