Diskperf on Windows Server 2003 Standard Edition.

Hello,
I'm using Windows Server 2003 Standard Edition which has multiple instances
of SQL Server 2005 standard edition. Am running a few tests that require the
switching on/off of the physical & logical disk counters.
Diskperf on Windows Server 2003 Standard Edition does not allow me to do this.
Either both (Logical & Physical) are enabled or both are disabled.
How can I turn them on/off individually?
Cheers!
SqlcatzThe implementation of this changed on Windows 2003. Both
logical and physical are automatically enabled "on demand"
under Win 2003.
-Sue
On Mon, 9 Oct 2006 03:51:02 -0700, SQLCatz
<SQLCatz@.discussions.microsoft.com> wrote:
>Hello,
>I'm using Windows Server 2003 Standard Edition which has multiple instances
>of SQL Server 2005 standard edition. Am running a few tests that require the
>switching on/off of the physical & logical disk counters.
>Diskperf on Windows Server 2003 Standard Edition does not allow me to do this.
>Either both (Logical & Physical) are enabled or both are disabled.
>How can I turn them on/off individually?
>Cheers!
>Sqlcatz|||Hello Sue,
Thank you for the reply.
Yes. They are automatically enabled - I came across that from an article.
But I'm not able to find anything that will allow me to disable them
(individually).
I'm executing certain tests for an application one of which requires that
these counters be disabled.
Is there any specific reason for Windows Server 2003 Standard Edition to
prevent the enabling/disabling of these counters? Can you point me to some
literature regarding this. I can accept the fact that this kind of behaviour
is not allowed - but need to know why - so that I provide a technical/logical
reason.
Cheers!
sqlcatz|||The are enabled when an application calls them - it's
automatic and built into the OS.
Previously, there were problems when you would have a
production performance issue and needed to monitor disks. If
the performance counters weren't enabled, you had to run
diskperf and reboot - not good for a production server.
You can run diskperf /help from the command line and read
the comments. That's one area of "documentation" on it - for
whatever that's worth. But the output is along the lines of:
NOTE: Disk performance counters are permanently enabled on
systems beyond Windows 2000.
-Sue
On Tue, 10 Oct 2006 22:13:01 -0700, SQLCatz
<SQLCatz@.discussions.microsoft.com> wrote:
>Hello Sue,
>Thank you for the reply.
>Yes. They are automatically enabled - I came across that from an article.
>But I'm not able to find anything that will allow me to disable them
>(individually).
>I'm executing certain tests for an application one of which requires that
>these counters be disabled.
>Is there any specific reason for Windows Server 2003 Standard Edition to
>prevent the enabling/disabling of these counters? Can you point me to some
>literature regarding this. I can accept the fact that this kind of behaviour
>is not allowed - but need to know why - so that I provide a technical/logical
>reason.
>Cheers!
>sqlcatz|||Thank you Sue!
sqlcatz

Disk Defragmenter & SQL Svr

I'm looking for info on running Windows 2000 disk
defragmenter on a W2k server running 2 instances on SQL
Server 2000. Does anyone know of issues or problems
running disk defrag while the SQL Server(s) are up and
running? Please reply with any info on this subject.
Thanks.while it is possible to defragment the sql server data
files while the service is running, it is very strongly
not recommended, as per andrew's advice
i do it on my development system, but production is
another matter
2nd) within a sql server data, there is no guarantee a
given table occupies contiguous space
3rd) sql server has a very clever scatter gather
capability that hides any negative consequences of a
fragmented file, along with providing other benefits
>--Original Message--
>I'm looking for info on running Windows 2000 disk
>defragmenter on a W2k server running 2 instances on SQL
>Server 2000. Does anyone know of issues or problems
>running disk defrag while the SQL Server(s) are up and
>running? Please reply with any info on this subject.
>Thanks.
>.
>|||Hello Andrew. on this point about running a defrag while
SQL Server is started... say you detached the databases
first, but SQL Server was still running (and not touching
any files on a drive you are defragging), would this still
be a case when you shouldn't defrag that drive? Is there
any place you can point me to that references this issue
of defragging while SQL is started? THanks, Bruce
>--Original Message--
>You should never run a defragmentor while sql server is
in use. Why do you
>think you need to defrag it?
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"B Wood" <brad.wood@.stclair.org> wrote in message
>news:2cb601c373c1$eba3f8a0$a401280a@.phx.gbl...
>> I'm looking for info on running Windows 2000 disk
>> defragmenter on a W2k server running 2 instances on SQL
>> Server 2000. Does anyone know of issues or problems
>> running disk defrag while the SQL Server(s) are up and
>> running? Please reply with any info on this subject.
>> Thanks.
>
>.
>|||Bruce,
I don't know if there are any actual articles per say. It's mostly just
good practice or common sense approach. If you defragging a drive that
doesn't have any sql server files on it then I guess you shouldn't have to
worry about it damaging sql server files then. But hopefully you don't
actually have users attempting to do anything on the server (otherwise why
keep sql running?) as a defrag utility usually monopolizes the cpu's and
hard drives.
--
Andrew J. Kelly
SQL Server MVP
"Bruce de Freitas" <bruce@.defreitas.com> wrote in message
news:3d5801c37622$ec1ff9b0$a101280a@.phx.gbl...
> Hello Andrew. on this point about running a defrag while
> SQL Server is started... say you detached the databases
> first, but SQL Server was still running (and not touching
> any files on a drive you are defragging), would this still
> be a case when you shouldn't defrag that drive? Is there
> any place you can point me to that references this issue
> of defragging while SQL is started? THanks, Bruce
>
>
> >--Original Message--
> >You should never run a defragmentor while sql server is
> in use. Why do you
> >think you need to defrag it?
> >
> >--
> >
> >Andrew J. Kelly
> >SQL Server MVP
> >
> >
> >"B Wood" <brad.wood@.stclair.org> wrote in message
> >news:2cb601c373c1$eba3f8a0$a401280a@.phx.gbl...
> >> I'm looking for info on running Windows 2000 disk
> >> defragmenter on a W2k server running 2 instances on SQL
> >> Server 2000. Does anyone know of issues or problems
> >> running disk defrag while the SQL Server(s) are up and
> >> running? Please reply with any info on this subject.
> >> Thanks.
> >
> >
> >.
> >|||Good article on this topic...
http://www.sql-server-performance.com/sql_fragmentation.asp
Use at your own risk...

Discovery of instances not correct with SCOM DBCreateWizard.exe

I have a 2 node cluster active/passive 2003 SP2 cluster.
I have 4 instances
SQLSRVISPS1\SQLSRV1
SQLSRVISPS2\SQLSRV2
SQLSRVIMGMT\SQLMGMT
SQLSRVIISA\SQLISA
When I use the DBCreateWizard.Exe to create the databases for SCOM, the
instances are wrongly discovered as :
SQLSRVISPS2\SQLSRV1
SQLSRVISPS2\SQLSRV2
SQLSRVISPS2\SQLMGMT
SQLSRVISPS2\SQLISA
Has anyone an idea how I can resolve this ?
Thanks
Carla
Since that's a Microsoft application, I would just talk to the MS support to
get a fix (if it's indeed a problem).
Linchi
"Carla" wrote:

> I have a 2 node cluster active/passive 2003 SP2 cluster.
> I have 4 instances
> SQLSRVISPS1\SQLSRV1
> SQLSRVISPS2\SQLSRV2
> SQLSRVIMGMT\SQLMGMT
> SQLSRVIISA\SQLISA
> When I use the DBCreateWizard.Exe to create the databases for SCOM, the
> instances are wrongly discovered as :
> SQLSRVISPS2\SQLSRV1
> SQLSRVISPS2\SQLSRV2
> SQLSRVISPS2\SQLMGMT
> SQLSRVISPS2\SQLISA
> Has anyone an idea how I can resolve this ?
> Thanks
> --
> Carla