Hi,
I have downloaded and run hte analyzer, but the result I get have lots of
exeption errors that contain the message:

Error while executing the Best Practice Group. See the log file
loadtraced_antodxp_0003_mshfsql_sqlbpa.log. Error message:

the log file cannot be found anywhere on the server or in my pc that I run
it from...
regards,

Dimitris
Based on your other post I'm guessing it is related to the trace files
you're feeding to BPA. Trace files should be files generated by SQL Server
profiler, not .sql files.

Let's try two things to isolate the errors you're seeing:
1) clear any specified Trace Files from the servers registered. Try to run
BPA. I'm guessing things should succeed.
2) Try with a .trc file generated by Profiler.

If this doesn't help, search for LOG folder under BPA installation folder
and post the log files.

- Christian


--
___________________________
Christian Kleinerman
Program Manager, SQL Engine

This posting is provided "AS IS" with no warranties, and confers no rights.

"dimitris" <dimitris (AT) microsoft (DOT) com> wrote

Thanks, it worked!

As you have already noticed I have posted a trace help request, you might be
able to help:
I have created a trace template using Profiler, called locks and have
included only the locks from the events menu (deadlocks, escalation and lock
timeout). I have saved a trace file called traceLocks, but I dont know what
to do with it. Can you help?

Best regards,
Dimitris

"Christian Kleinerman [MS]" <ckleiner (AT) online (DOT) microsoft.com> wrote

Dimitris
BPA will scan statement start and completion as well as batch start and
completion events - for those events, it will lookup the SQL text being
exeuted and will scan it for best practices.
If you only have locking events, I'm not sure you'll be able to do much with
BPA.

If you create a trace file that captures batch/statement events, you can
include the path in PBA (e.g. c:\yourpath\yourtracefile.trc) for a given
server and BPA will perform the scan.

Let me know if you have additional questions.

- Christian



"dimitris" <dimitris (AT) microsoft (DOT) com> wrote