It appears that SqlDiag.exe has changed quite a bit from SQL 2000.  I'm
trying to run an instance of SqlDiag (as a task not a service) for a SQL
Express named instance (\BILL).  Here's my command issued from the
\90\tools\binn folder:

sqldiag START /O"c:\Bill" /G

But it doesn't run, I get:
2006/06/06 13:43:21.88 SQLDIAG Invalid command line parameter
2006/06/06 13:43:21.88 SQLDIAG Error parsing command line parameters

Questions:
1. which are my invalid parameters?
2. if there are multiple SQL 2005 (or SQL 2000?) instances on the machine,
how do monitor JUST my one named instance \BILL?

Thanks!

....so to follow-up on my own post... :)

I see the SQLDiag.XML file that you can copy/customize.  Here's a sample
section for SQL Server:
</PerfmonObject>

<PerfmonObject name="\MSSQL$%s:Databases(*)" enabled="true">

<PerfmonCounter name="\*" enabled="true" />

<PerfmonCounter name="\Data File(s) Size (KB)" enabled="true" />

<PerfmonCounter name="\Log File(s) Size (KB)" enabled="true" />


Can I specify the SQL Instance Name that I want in here?  Like replace the
%s with \BILL?  or would I replace the first "\*" with "\BILL"?

I googled and checked MSDN but cannot seem to find any details.  Again, I
only care about one particular SQL Instance on the machine, not all
instances.

Also, if I'm using SQL Security (not Windows integrated), how do I
encapsulate/supply the 'sa' and password credentials?

Show quoteHide quote

Transact Log truncate
Edit/Modify Stored Procedure in Management Console 2005
Using Query Analyzer with SQL 2005
database log truncated, transaction log backup job failed
SQL 2005 Database Engine Tuning Advisor