Microsoft SQL Server Best Practices Analyzer

Should this tool be installed and run in a production server?
MM
barney@.newsgroups.nospam
Martin,
If you are concerned about installing this tool on production server, you
can install this tool on a remote machine and you could analyze a production
server from a remote machine (as long as you can connect to target SQL
Server from remote machine)
SQL Best Practices Analyzer relies on the BPA Repository database, which is
a SQL Server database created during SQL BPA installation. You can have this
BPA repository database created on local SQL Server or a remote SQL Server.
SQL Best Practices Analyzer requires the following components to be
installed on the machine
.. Microsoft Internet Explorer 6.0 or later
.. Microsoft .Net Framework 1.1
Reference:
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Sethu
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Martin Millar" <barney@.newsgroups.nospam> wrote in message
news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
> Should this tool be installed and run in a production server?
> --
> MM
> barney@.newsgroups.nospam
|||Thanks for this. perhaps I should have been a bit more precise. I am a
developer and I'm having a beef with my DBA who has installed this on the
live production server. My argument is that this should be installed and run
on a test system as there is no need to test the performance of the hardware
on which the DB runs on.
If it's OK on Test then it gets ported to live. I believe that anything that
does not need to be installed on a production server should not be on there
as there is a danger that something else running on the box may result in a
loss of service or may intoduce a risk of virus or attack. This tool requires
the dot.net framework and I am a strong fan of this being an asp.net
developer. But until this (dot.net) becomes a core part of the OS (i.e. when
it's installed by default on XP, win2003 etc) I categorise this as a
development add-on and has an attached if installed.
If MS release a security patch for dot.net then I need to schedule downtime
on the production server to apply this.
So back to my original question, which is in itself is about best practises,
should it be best practise to install the BPA on a production server?
Thanks in advance
"Sethu Srinivasan [MSFT]" wrote:

> Martin,
> If you are concerned about installing this tool on production server, you
> can install this tool on a remote machine and you could analyze a production
> server from a remote machine (as long as you can connect to target SQL
> Server from remote machine)
> SQL Best Practices Analyzer relies on the BPA Repository database, which is
> a SQL Server database created during SQL BPA installation. You can have this
> BPA repository database created on local SQL Server or a remote SQL Server.
> SQL Best Practices Analyzer requires the following components to be
> installed on the machine
> .. Microsoft Internet Explorer 6.0 or later
> .. Microsoft .Net Framework 1.1
> Reference:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Thanks
> Sethu
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
>
> "Martin Millar" <barney@.newsgroups.nospam> wrote in message
> news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
>
>