Determin whether port number assigned dynamically or hardcoded

I undstand that if you choose to dynamically assign a port number to an
instance this is a once only operation performed the first time that instance
is started and from then on it always attepts to use that port number.
Having just started with a new company I'm trying to work out if instance
port numbers were assigned dynamically or hardcoded during install as this
affect the client connection properties for connections (if hardcoded each
client needs to be configured with the port number rather than allowing an
instance to be resolved to a port).
Is there a regkey or anything that says how ports were assigned?
Steve
Steve Morgan
MCDBA
Snr Production DBA
If you are looking for a registry key to determine if SQL
Server is listening on the default port, it's located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNetLib\Tcp
That will give you the listening port.
You can also get the information from the SQL Server log.
You can also get the information using various network
commands, tools.
-Sue
On Tue, 30 Nov 2004 08:55:09 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:

>I undstand that if you choose to dynamically assign a port number to an
>instance this is a once only operation performed the first time that instance
>is started and from then on it always attepts to use that port number.
>Having just started with a new company I'm trying to work out if instance
>port numbers were assigned dynamically or hardcoded during install as this
>affect the client connection properties for connections (if hardcoded each
>client needs to be configured with the port number rather than allowing an
>instance to be resolved to a port).
>Is there a regkey or anything that says how ports were assigned?
>Steve
|||Hi Sue
Thnx for the reply but thats not my question - I know how to check the port
numbers currently being used.
What I need to work out is whether during the install the option to
dynamically assign instance port numbers was choosen or if they were
pre-choosen & hardcoded.
According to a technet article on connectivity problems this decision
affects whether on the client machine you can use the <server>\<instance
name> in your connection string or whether you have to use <server>\<port
number>
I'm having intermittent connection problems usine <server>\<instance name>
and want to know if the install port decision could be the root cause.
Steve
"Sue Hoegemeier" wrote:

> If you are looking for a registry key to determine if SQL
> Server is listening on the default port, it's located at:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNetLib\Tcp
> That will give you the listening port.
> You can also get the information from the SQL Server log.
> You can also get the information using various network
> commands, tools.
> -Sue
> On Tue, 30 Nov 2004 08:55:09 -0800, Steve Morgan
> <SteveMorgan@.discussions.microsoft.com> wrote:
>
>
|||Check the same area in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<IYournstanceName>\MSSQLServer\SuperSocketN etLib\Tcp
The combination of the values for TCPDynamicPorts and
TCPPort will help you determine the setting. You can find
them outlined in the following article:
http://support.microsoft.com/?id=823938
-Sue
On Wed, 1 Dec 2004 02:11:02 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Sue
>Thnx for the reply but thats not my question - I know how to check the port
>numbers currently being used.
>What I need to work out is whether during the install the option to
>dynamically assign instance port numbers was choosen or if they were
>pre-choosen & hardcoded.
>According to a technet article on connectivity problems this decision
>affects whether on the client machine you can use the <server>\<instance
>name> in your connection string or whether you have to use <server>\<port
>number>
>I'm having intermittent connection problems usine <server>\<instance name>
>and want to know if the install port decision could be the root cause.
>Steve
>
>"Sue Hoegemeier" wrote:

Determin whether port number assigned dynamically or hardcoded

I undstand that if you choose to dynamically assign a port number to an
instance this is a once only operation performed the first time that instanc
e
is started and from then on it always attepts to use that port number.
Having just started with a new company I'm trying to work out if instance
port numbers were assigned dynamically or hardcoded during install as this
affect the client connection properties for connections (if hardcoded each
client needs to be configured with the port number rather than allowing an
instance to be resolved to a port).
Is there a regkey or anything that says how ports were assigned?
Steve
Steve Morgan
MCDBA
Snr Production DBAIf you are looking for a registry key to determine if SQL
Server is listening on the default port, it's located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketNet
Lib\Tcp
That will give you the listening port.
You can also get the information from the SQL Server log.
You can also get the information using various network
commands, tools.
-Sue
On Tue, 30 Nov 2004 08:55:09 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:

>I undstand that if you choose to dynamically assign a port number to an
>instance this is a once only operation performed the first time that instan
ce
>is started and from then on it always attepts to use that port number.
>Having just started with a new company I'm trying to work out if instance
>port numbers were assigned dynamically or hardcoded during install as this
>affect the client connection properties for connections (if hardcoded each
>client needs to be configured with the port number rather than allowing an
>instance to be resolved to a port).
>Is there a regkey or anything that says how ports were assigned?
>Steve|||Hi Sue
Thnx for the reply but thats not my question - I know how to check the port
numbers currently being used.
What I need to work out is whether during the install the option to
dynamically assign instance port numbers was choosen or if they were
pre-choosen & hardcoded.
According to a technet article on connectivity problems this decision
affects whether on the client machine you can use the <server>\<instance
name> in your connection string or whether you have to use <server>\<port
number>
I'm having intermittent connection problems usine <server>\<instance name>
and want to know if the install port decision could be the root cause.
Steve
"Sue Hoegemeier" wrote:

> If you are looking for a registry key to determine if SQL
> Server is listening on the default port, it's located at:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\SuperSocketN
etLib\Tcp
> That will give you the listening port.
> You can also get the information from the SQL Server log.
> You can also get the information using various network
> commands, tools.
> -Sue
> On Tue, 30 Nov 2004 08:55:09 -0800, Steve Morgan
> <SteveMorgan@.discussions.microsoft.com> wrote:
>
>|||Check the same area in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL
Server\<IYournstanceName>\MSSQLServer\SuperSocketNetLib\Tcp
The combination of the values for TCPDynamicPorts and
TCPPort will help you determine the setting. You can find
them outlined in the following article:
http://support.microsoft.com/?id=823938
-Sue
On Wed, 1 Dec 2004 02:11:02 -0800, Steve Morgan
<SteveMorgan@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Sue
>Thnx for the reply but thats not my question - I know how to check the port
>numbers currently being used.
>What I need to work out is whether during the install the option to
>dynamically assign instance port numbers was choosen or if they were
>pre-choosen & hardcoded.
>According to a technet article on connectivity problems this decision
>affects whether on the client machine you can use the <server>\<instance
>name> in your connection string or whether you have to use <server>\<port
>number>
>I'm having intermittent connection problems usine <server>\<instance name>
>and want to know if the install port decision could be the root cause.
>Steve
>
>"Sue Hoegemeier" wrote:
>

Detaching & Attaching Database

Hello Group.
I have the following problem using SQL Server 2000 on WinXP machine.
I detached a SQL database and then performed a windows copy of the database
to another folder on the system.
I then renamed the database and tried to attach the renamed database to SQL.
SQL sees the old name and says there is already a database with that name
attached.
How can I solve this problem?
How can I get SQL to see the new name given to the MDF and LDF files?
Thanks,
Terry"Terry" <tgwillett@.cox.net> wrote in message
news:Trhwf.51529$ih5.12670@.dukeread11...
> Hello Group.
> I have the following problem using SQL Server 2000 on WinXP machine.
> I detached a SQL database and then performed a windows copy of the
> database to another folder on the system.
> I then renamed the database and tried to attach the renamed database to
> SQL.
> SQL sees the old name and says there is already a database with that name
> attached.
> How can I solve this problem?
> How can I get SQL to see the new name given to the MDF and LDF files?
> Thanks,
> Terry
>
Renaming the MDF / LDF files has nothing to do with renaming the database.
The name for the database when it is attached is specified by the first
parameter of sp_attach_db. Example:
EXEC sp_attach_db 'new_db_name',
'd:\mssql\data\db_file_name.mdf',
'd:\mssql\data\db_file_name.ldf'
David Portas
SQL Server MVP
--|||Hi Terry
The name of the database does not have to have anything to do with the names
of the database files. So when you say you renamed 'the database' do you
mean you renamed the files you moved, or renamed the database on the server?
The original name of the database is stored with the files, however, even if
you change the name of the files. If you want to attach some database files
and give the database contained on those files another name than the one it
originally had, you have to specify that when you do the attach.
I suggest you use the command sp_attach_db, following the examples in the
Books Online. This will allow you to specify the name of the database you
are attaching, and the physical names of all the files you want to attach.
If you still are unsuccessful, you can then post the exact command you are
using and the exact error message you get back.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Terry" <tgwillett@.cox.net> wrote in message
news:Trhwf.51529$ih5.12670@.dukeread11...
> Hello Group.
> I have the following problem using SQL Server 2000 on WinXP machine.
> I detached a SQL database and then performed a windows copy of the
> database to another folder on the system.
> I then renamed the database and tried to attach the renamed database to
> SQL.
> SQL sees the old name and says there is already a database with that name
> attached.
> How can I solve this problem?
> How can I get SQL to see the new name given to the MDF and LDF files?
> Thanks,
> Terry
>|||Okay, but how do I accomplish this with enterprise manager?
In the dialog box that appears when you go to attach the database, it gives
you the orginal database name.
In the box "attach as" I give it the new name and get the error that it
already exits.
What am I missing here?
Thanks, for your quick response.
Terry
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uClxr8KFGHA.2064@.TK2MSFTNGP09.phx.gbl...
> "Terry" <tgwillett@.cox.net> wrote in message
> news:Trhwf.51529$ih5.12670@.dukeread11...
> Renaming the MDF / LDF files has nothing to do with renaming the database.
> The name for the database when it is attached is specified by the first
> parameter of sp_attach_db. Example:
> EXEC sp_attach_db 'new_db_name',
> 'd:\mssql\data\db_file_name.mdf',
> 'd:\mssql\data\db_file_name.ldf'
> --
> David Portas
> SQL Server MVP
> --
>|||Okay, your statement
"The original name of the database is stored with the files" explains what I
was missing.
Now I understand. I did not know this.
Thanks,
Kalen
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%23Edin%23KFGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi Terry
> The name of the database does not have to have anything to do with the
> names of the database files. So when you say you renamed 'the database' do
> you mean you renamed the files you moved, or renamed the database on the
> server?
> The original name of the database is stored with the files, however, even
> if you change the name of the files. If you want to attach some database
> files and give the database contained on those files another name than the
> one it originally had, you have to specify that when you do the attach.
> I suggest you use the command sp_attach_db, following the examples in the
> Books Online. This will allow you to specify the name of the database you
> are attaching, and the physical names of all the files you want to attach.
> If you still are unsuccessful, you can then post the exact command you are
> using and the exact error message you get back.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Terry" <tgwillett@.cox.net> wrote in message
> news:Trhwf.51529$ih5.12670@.dukeread11...
>
>|||"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uClxr8KFGHA.2064@.TK2MSFTNGP09.phx.gbl...
> "Terry" <tgwillett@.cox.net> wrote in message
> news:Trhwf.51529$ih5.12670@.dukeread11...
I don't know about accomplishing this in Enterprise Manager because I rarely
use EM that way. In my opinion it would be much easier to type the
sp_attach_db command in Query Analyzer.
David Portas
SQL Server MVP
--|||Okay,
Thanks for your help.
Much appreciated.
Terry
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:eEqu3XLFGHA.1288@.TK2MSFTNGP09.phx.gbl...
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:uClxr8KFGHA.2064@.TK2MSFTNGP09.phx.gbl...
> I don't know about accomplishing this in Enterprise Manager because I
> rarely use EM that way. In my opinion it would be much easier to type the
> sp_attach_db command in Query Analyzer.
> --
> David Portas
> SQL Server MVP
> --
>

Detach/Attach database

I need to move the ".ldf" log file from my 'w' drive to my 'l' drive. I
performed the following:
1> detach database
2> moved the .ldf file to the 'l' drive(deleted from the w drive)
3> attched the database
4> received a RED 'x'on the ldf file >> retyped the new location of the file
and hit OK . The attach failed with the following error.
error 5105:devide activation error: The physical file name '....' may be
incorrect
cannot create '....' because it already exists.Hi
Rather use T-SQL. Open up query analyser and use the following code. Change
the Db names, files and paths as appropriate:
EXEC sp_attach_db @.dbname = N'pubs',
@.filename1 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf',
@.filename2 = N'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\pubs_log.ldf'
"Joe" wrote:
> I need to move the ".ldf" log file from my 'w' drive to my 'l' drive. I
> performed the following:
> 1> detach database
> 2> moved the .ldf file to the 'l' drive(deleted from the w drive)
> 3> attched the database
> 4> received a RED 'x'on the ldf file >> retyped the new location of the file
> and hit OK . The attach failed with the following error.
> error 5105:devide activation error: The physical file name '....' may be
> incorrect
> cannot create '....' because it already exists.
>
>
>
>|||I got the same results.--see below:
EXEC sp_attach_db @.dbname = N'MessageEngine',
@.filename1 = N'w:\Program Files\Microsoft SQL
Server\MSSQL\Data\MessageEngine.mdf',
@.filename2 = N'l:\SQLLOGS\MessageEngine_log.LDF'
>>>
Server: Msg 5105, Level 16, State 4, Line 1
Device activation error. The physical file name
'l:\SQLLOGS\MessageEngine_log.LDF' may be incorrect.
Server: Msg 5170, Level 16, State 1, Line 1
Cannot create file 'L:\SQLLOGS\\MessageEngine_log.LDF' because it already
exists.
Server: Msg 1813, Level 16, State 1, Line 1
Could not open new database 'MessageEngine'. CREATE DATABASE is aborted.
Device activation error. The physical file name
'l:\SQLLOGS\MessageEngine_log.LDF' may be incorrect.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Rather use T-SQL. Open up query analyser and use the following code. Change
> the Db names, files and paths as appropriate:
> EXEC sp_attach_db @.dbname = N'pubs',
> @.filename1 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf',
> @.filename2 = N'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\pubs_log.ldf'
>
> "Joe" wrote:
> > I need to move the ".ldf" log file from my 'w' drive to my 'l' drive. I
> > performed the following:
> > 1> detach database
> > 2> moved the .ldf file to the 'l' drive(deleted from the w drive)
> > 3> attched the database
> > 4> received a RED 'x'on the ldf file >> retyped the new location of the file
> > and hit OK . The attach failed with the following error.
> >
> > error 5105:devide activation error: The physical file name '....' may be
> > incorrect
> > cannot create '....' because it already exists.
> >
> >
> >
> >
> >
> >
> >|||Hi
From the command prompt, do a DIR l:\SQLLOGS\MessageEngine_log.LDF
Alos, check the the SQL Server Service account has permissions in the
directory and file.
Regards
Mike
"Joe" wrote:
> I got the same results.--see below:
> EXEC sp_attach_db @.dbname = N'MessageEngine',
> @.filename1 = N'w:\Program Files\Microsoft SQL
> Server\MSSQL\Data\MessageEngine.mdf',
> @.filename2 = N'l:\SQLLOGS\MessageEngine_log.LDF'
> >>>
> Server: Msg 5105, Level 16, State 4, Line 1
> Device activation error. The physical file name
> 'l:\SQLLOGS\MessageEngine_log.LDF' may be incorrect.
> Server: Msg 5170, Level 16, State 1, Line 1
> Cannot create file 'L:\SQLLOGS\\MessageEngine_log.LDF' because it already
> exists.
> Server: Msg 1813, Level 16, State 1, Line 1
> Could not open new database 'MessageEngine'. CREATE DATABASE is aborted.
> Device activation error. The physical file name
> 'l:\SQLLOGS\MessageEngine_log.LDF' may be incorrect.
> "Mike Epprecht (SQL MVP)" wrote:
> > Hi
> >
> > Rather use T-SQL. Open up query analyser and use the following code. Change
> > the Db names, files and paths as appropriate:
> >
> > EXEC sp_attach_db @.dbname = N'pubs',
> > @.filename1 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf',
> > @.filename2 = N'c:\Program Files\Microsoft SQL
> > Server\MSSQL\Data\pubs_log.ldf'
> >
> >
> >
> > "Joe" wrote:
> >
> > > I need to move the ".ldf" log file from my 'w' drive to my 'l' drive. I
> > > performed the following:
> > > 1> detach database
> > > 2> moved the .ldf file to the 'l' drive(deleted from the w drive)
> > > 3> attched the database
> > > 4> received a RED 'x'on the ldf file >> retyped the new location of the file
> > > and hit OK . The attach failed with the following error.
> > >
> > > error 5105:devide activation error: The physical file name '....' may be
> > > incorrect
> > > cannot create '....' because it already exists.
> > >
> > >
> > >
> > >
> > >
> > >
> > >|||Make sure you move the old MessageEngine_log.LDF file to L:\SQLLOGS\
directory before you run sp_attach_db.
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:94AF06C2-E3A1-4089-9620-7315F6EE9CD0@.microsoft.com...
>I got the same results.--see below:
> EXEC sp_attach_db @.dbname = N'MessageEngine',
> @.filename1 = N'w:\Program Files\Microsoft SQL
> Server\MSSQL\Data\MessageEngine.mdf',
> @.filename2 = N'l:\SQLLOGS\MessageEngine_log.LDF'
>>>>
> Server: Msg 5105, Level 16, State 4, Line 1
> Device activation error. The physical file name
> 'l:\SQLLOGS\MessageEngine_log.LDF' may be incorrect.
> Server: Msg 5170, Level 16, State 1, Line 1
> Cannot create file 'L:\SQLLOGS\\MessageEngine_log.LDF' because it already
> exists.
> Server: Msg 1813, Level 16, State 1, Line 1
> Could not open new database 'MessageEngine'. CREATE DATABASE is aborted.
> Device activation error. The physical file name
> 'l:\SQLLOGS\MessageEngine_log.LDF' may be incorrect.
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Rather use T-SQL. Open up query analyser and use the following code.
>> Change
>> the Db names, files and paths as appropriate:
>> EXEC sp_attach_db @.dbname = N'pubs',
>> @.filename1 = N'c:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\pubs.mdf',
>> @.filename2 = N'c:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\pubs_log.ldf'
>>
>> "Joe" wrote:
>> > I need to move the ".ldf" log file from my 'w' drive to my 'l' drive. I
>> > performed the following:
>> > 1> detach database
>> > 2> moved the .ldf file to the 'l' drive(deleted from the w drive)
>> > 3> attched the database
>> > 4> received a RED 'x'on the ldf file >> retyped the new location of the
>> > file
>> > and hit OK . The attach failed with the following error.
>> >
>> > error 5105:devide activation error: The physical file name '....' may
>> > be
>> > incorrect
>> > cannot create '....' because it already exists.
>> >
>> >
>> >
>> >
>> >
>> >
>> >

Desperate! - Need simple MSSQL server monitoring scripts, ideas, etc that can be performed

Does anyone have any basic, simple scripts of sp's that I can give my
computer operators to use to monitor for serious conditions on our sql
servers? We are new in the ms-sql arena, a small shop and we cant
really purchase any tools to monitor these servers, but we need some
basic checks that we can use to make sure a server is performing in a
reasonable fashion, no blocks, cpu<xx%, memory not pegged, IO working,
etc...and we need to be able to do this without bugging our
programmers every time we are wondering why things are slowwnig down.

We are a split shop between as400s and sql servers, and our operations
staff has no problem performing this type of duty on the 400s. I think
since the sql servers are so easy to deploy into production, the idea
of how to monitor these things health got lost in the shuffle and
allowing the programmers to do it just serves to destabilize our
environment.

Please help! Our shop has turned to chaos since we went live with
MSSQL centric applications and everytime one programmer "resolves an
issue" some other programmers application starts to act up.I think that if you have AS400's, you should have the funds for a monitoring
tool.
Look at a product called "Spotlight on SQL Server" from Quest Software
www.quest.com . This 1 screen interface looks like the helm of the Starship
Enterprise.
Just by observing the screen, your operators can see if anything is wrong.
It has built in alarms that you can customize with your own thresholds (ie,
CPU > xx%, memory low, Cache hit ratio less than 90%, etc).

Oscar...

"freakyfreak" <emebohw2@.netscape.net> wrote in message
news:70f72e5f.0410071044.22a331d2@.posting.google.c om...
> Does anyone have any basic, simple scripts of sp's that I can give my
> computer operators to use to monitor for serious conditions on our sql
> servers? We are new in the ms-sql arena, a small shop and we cant
> really purchase any tools to monitor these servers, but we need some
> basic checks that we can use to make sure a server is performing in a
> reasonable fashion, no blocks, cpu<xx%, memory not pegged, IO working,
> etc...and we need to be able to do this without bugging our
> programmers every time we are wondering why things are slowwnig down.
> We are a split shop between as400s and sql servers, and our operations
> staff has no problem performing this type of duty on the 400s. I think
> since the sql servers are so easy to deploy into production, the idea
> of how to monitor these things health got lost in the shuffle and
> allowing the programmers to do it just serves to destabilize our
> environment.
> Please help! Our shop has turned to chaos since we went live with
> MSSQL centric applications and everytime one programmer "resolves an
> issue" some other programmers application starts to act up.|||Are you aware that from your own desktop you can run Windows PERFMON and set
the source for the data to your database server?

PERFMON will show you MANY SQL Server performance counters that you can
monitor either graphically or do a capture for later analysis.

"freakyfreak" <emebohw2@.netscape.net> wrote in message
news:70f72e5f.0410071044.22a331d2@.posting.google.c om...
> Does anyone have any basic, simple scripts of sp's that I can give my
> computer operators to use to monitor for serious conditions on our sql
> servers? We are new in the ms-sql arena, a small shop and we cant
> really purchase any tools to monitor these servers, but we need some
> basic checks that we can use to make sure a server is performing in a
> reasonable fashion, no blocks, cpu<xx%, memory not pegged, IO working,
> etc...and we need to be able to do this without bugging our
> programmers every time we are wondering why things are slowwnig down.
> We are a split shop between as400s and sql servers, and our operations
> staff has no problem performing this type of duty on the 400s. I think
> since the sql servers are so easy to deploy into production, the idea
> of how to monitor these things health got lost in the shuffle and
> allowing the programmers to do it just serves to destabilize our
> environment.
> Please help! Our shop has turned to chaos since we went live with
> MSSQL centric applications and everytime one programmer "resolves an
> issue" some other programmers application starts to act up.|||Thanks DHatheway, this is kind of cool. one question though, I cant
figure out how to connect perfmon to my server...runs fins at my pc
for my pc.|||Hi

If your SQL Server counters are missing check out:
http://support.microsoft.com/defaul...kb;en-us;227662

If it is to the run the application then either type in permon.msc /s from
the run command or a command prompt or use the option on the administrator
menu.

I would not recommend running this over the network, but you can change the
computer being monitored when you add your counter (Select counters from
computer).

John

"freakyfreak" <emebohw2@.netscape.net> wrote in message
news:70f72e5f.0410081324.50c6607c@.posting.google.c om...
> Thanks DHatheway, this is kind of cool. one question though, I cant
> figure out how to connect perfmon to my server...runs fins at my pc
> for my pc.|||...useful (sarcasm implied)|||- Fire up PERFMON (start | run - then enter PERFMON in the RUN dialog box)
- It should pop up with a chart window populated by nothing. If not, click
"system monitor" from the tree on the left side.
- If you have a chart with entries, click on each line description in the
bottom right and delete each one (delete key).
- Then, right-click anywhere on the chart. This gets you a context menu
that includes "add counters..." Pick that option.
- Now you're looking at a dialog box that includes radio button options for
"use local computer" and "select counters from computer".
- Click on the "select counters from computer" and put the name of the
computer you want to monitor in the text box below (may have to use
double-slashes - e.g.: \\mydbserver)
- Click on the "Performance Counters" listbox. It will refresh with a list
of performance counters available on the remote computer (if it's a database
server, it should include a number of SQL Server performance counter
categories.
- Start selecting the ones you think relevant.

If you don't see counters for SQL Server listed for your database server,
John Bell's post of 10/9 5:05am points you to a resource to help you with
that problem.

There are also options for logging PERMON information. It's not what I'd
call intuitive but, once you get going this far, I think you'll be able to
figure it out.

Another option you have for PERFMON is to use Windows Terminal Server to run
a session on your database server and run PERFMON there. PERFMON running in
a WTS session on your database server will default to that server. I prefer
not to use WTS sessions on my database servers but it is a reasonable thing
to do for some management tasks. I'd strongly advise against doing anything
that would reduce security, like install or use Office or Internet Explorer,
etc. I keep my database servers "clean."

"freakyfreak" <emebohw2@.netscape.net> wrote in message
news:70f72e5f.0410081324.50c6607c@.posting.google.c om...
> Thanks DHatheway, this is kind of cool. one question though, I cant
> figure out how to connect perfmon to my server...runs fins at my pc
> for my pc.