Collecting data with profiler

I'm running profiler and collect data which I'll use later for index tuning
wizard.
I'm collecting eventClass,SPID and text Data in profiler. Because
application use procedures, text data in profiler looks like:
exec e_prikazNarIzdelka 'I0202','HRK'
exec e_prikazIzdPoNar 'I0202','EEK',NULL
and so on.
Is it usefull for index tuning wizard?
Or text data should be actual select, insert, or update statements which are
inside procedures?
If so, how can I collect that statements in profiler instead of executing
stored procedures statements?
Thank you,
SimonTheres is an option where you can tell that SQL Server will use the traces
for further use, should should use that, because additional metadata is
stored then. Furtheron you should trace the STMT Event, Transaction, Scans
and further on. A list of useful data can be found here:
http://blog.transactsql.com/2005_01_01_archive.html
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"simon" wrote:

> I'm running profiler and collect data which I'll use later for index tunin
g
> wizard.
> I'm collecting eventClass,SPID and text Data in profiler. Because
> application use procedures, text data in profiler looks like:
> exec e_prikazNarIzdelka 'I0202','HRK'
> exec e_prikazIzdPoNar 'I0202','EEK',NULL
> and so on.
> Is it usefull for index tuning wizard?
> Or text data should be actual select, insert, or update statements which a
re
> inside procedures?
> If so, how can I collect that statements in profiler instead of executing
> stored procedures statements?
> Thank you,
> Simon
>
>|||Hi Jens,
thank you for your answer.
So, that means that "exec e_prikazNarIzdelka 'I0202','HRK'" is not usefull
for index tuning wizard?
It will not go into procedure e_prikazNarIzdelka and look, which
select,update and insert statements are inside that procedure?
I read somewhere that eventClass and text Data should be enough for index
tuning wizard.
Statement was:" Don't capture more in your profiler trace than you need. The
only events and data columns required by the index tuning wizard include the
SQL:BatchCompleted and the RPC:completed events in the TSQL category and
the eventClass and Text data columns."
So I put only that into my profiler trace.
Regards,
Simon
"Jens Smeyer" <JensSmeyer@.discussions.microsoft.com> wrote in message
news:4A526DCC-3167-4150-A349-CA8D3AE59367@.microsoft.com...
> Theres is an option where you can tell that SQL Server will use the traces
> for further use, should should use that, because additional metadata is
> stored then. Furtheron you should trace the STMT Event, Transaction, Scans
> and further on. A list of useful data can be found here:
> http://blog.transactsql.com/2005_01_01_archive.html
>
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "simon" wrote:
>