Perrormance Monitor

Using Windows performance monitor, I noticed that the
Output Queue Length under my Network Interface is showing
a very high number of 4294967291. I read somewhere that
if this is longer than 2, then delays are being
experienced and a bottle neck exists. This is a Win2K
server running MS SQL 2000. What can do to determine the
source of this bottleneck and correct it?
EmmaThat would indeed be a high number. However, PerfMon counters sometimes get
messed up and I don't believe that's really the number...
Do you have the ability to reboot the box?
--
Brian
"Emma" <eeemore@.hotmail.com> wrote in message
news:025301c3aad7$2213a830$a101280a@.phx.gbl...
> Using Windows performance monitor, I noticed that the
> Output Queue Length under my Network Interface is showing
> a very high number of 4294967291. I read somewhere that
> if this is longer than 2, then delays are being
> experienced and a bottle neck exists. This is a Win2K
> server running MS SQL 2000. What can do to determine the
> source of this bottleneck and correct it?
> Emma|||I can reboot the box after business hours. I will do that
and check the number again.
Thanks
>--Original Message--
>That would indeed be a high number. However, PerfMon
counters sometimes get
>messed up and I don't believe that's really the
number...
>Do you have the ability to reboot the box?
>--
>Brian
>
>"Emma" <eeemore@.hotmail.com> wrote in message
>news:025301c3aad7$2213a830$a101280a@.phx.gbl...
>> Using Windows performance monitor, I noticed that the
>> Output Queue Length under my Network Interface is
showing
>> a very high number of 4294967291. I read somewhere that
>> if this is longer than 2, then delays are being
>> experienced and a bottle neck exists. This is a Win2K
>> server running MS SQL 2000. What can do to determine
the
>> source of this bottleneck and correct it?
>> Emma
>
>.
>|||Emma,
How did you resolve your problem with the OUTPUT QUEUE LENGTH- as I am having the same issues on my ISA servers Rebooting the server does not seem to help as it shoots right up again. this does appear to be an ISA specific issue but it would be helpful to know why.
regards,
Ade
-- Emma wrote: --
I can reboot the box after business hours. I will do that
and check the number again.
Thanks
>--Original Message--
>That would indeed be a high number. However, PerfMon
counters sometimes get
>messed up and I don't believe that's really the
number...
>>Do you have the ability to reboot the box?
>>--
>>Brian
>>"Emma" <eeemore@.hotmail.com> wrote in message
>news:025301c3aad7$2213a830$a101280a@.phx.gbl...
>> Using Windows performance monitor, I noticed that the
>> Output Queue Length under my Network Interface is
showing
>> a very high number of 4294967291. I read somewhere that
>> if this is longer than 2, then delays are being
>> experienced and a bottle neck exists. This is a Win2K
>> server running MS SQL 2000. What can do to determine
the
>> source of this bottleneck and correct it?
>> Emma
>>.
>

Permissions in SQL Server 2005 to allow users to view the Management Activity monitor?

For SQL Server 2000 we have a user login mapped to msdb with database role membership of db_datareader and public checked. This seems to allow the developers to view the Management Activity monitor. For SQL Server 2005 the same mapping is in place but the developers cannot view the Management Activity monitor. Developers are NOT granted the sysadmin role, and should not have that role.

What permissions need to be set for SQL Server 2005 to allow users to view the Management Activity monitor? They should not be allowed to take actions on the activities.

The Active Monitor tool requires VIEW SERVER STATE permission; this permission is required to select from DMVs such as sys.sysprocesses.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thank you so much! This did the trick.

Barb

|||

Does Management Studio Express support the Activity Monitor?

I've enabled VIEW SERVER STATE for admin and still can't find the Activity Monitor in the GUI.

Thanks

|||

Unfortunately I am not familiar with the different GUI tools available for SQL Express. I would recommend asking this question on the SQL Express forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1) instead.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Where do you set this: To view the Activity Monitor the user needs VIEW SERVER STATE permission on a SQL Server 2005 server.

|||

The easiest way is to just open a connection (i.e. using sqlcmd or Management Studio) using your sysadmin credentials and issue the following statement:

GRANTVIEWSERVER STATETO <<login name>>

This will grant <<login_name>> VIEW ANY STATE permission.

-Raul Garcia

SDE/T

SQL Server Engine

Permissions in SQL Server 2005 to allow users to view the Management Activity monitor?

For SQL Server 2000 we have a user login mapped to msdb with database role membership of db_datareader and public checked. This seems to allow the developers to view the Management Activity monitor. For SQL Server 2005 the same mapping is in place but the developers cannot view the Management Activity monitor. Developers are NOT granted the sysadmin role, and should not have that role.

What permissions need to be set for SQL Server 2005 to allow users to view the Management Activity monitor? They should not be allowed to take actions on the activities.

The Active Monitor tool requires VIEW SERVER STATE permission; this permission is required to select from DMVs such as sys.sysprocesses.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thank you so much! This did the trick.

Barb

|||

Does Management Studio Express support the Activity Monitor?

I've enabled VIEW SERVER STATE for admin and still can't find the Activity Monitor in the GUI.

Thanks

|||

Unfortunately I am not familiar with the different GUI tools available for SQL Express. I would recommend asking this question on the SQL Express forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1) instead.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Where do you set this: To view the Activity Monitor the user needs VIEW SERVER STATE permission on a SQL Server 2005 server.

|||

The easiest way is to just open a connection (i.e. using sqlcmd or Management Studio) using your sysadmin credentials and issue the following statement:

GRANT VIEW SERVER STATE TO <<login name>>

This will grant <<login_name>> VIEW ANY STATE permission.

-Raul Garcia

SDE/T

SQL Server Engine

Permissions in SQL Server 2005 to allow users to view the Management Activity monitor?

For SQL Server 2000 we have a user login mapped to msdb with database role membership of db_datareader and public checked. This seems to allow the developers to view the Management Activity monitor. For SQL Server 2005 the same mapping is in place but the developers cannot view the Management Activity monitor. Developers are NOT granted the sysadmin role, and should not have that role.

What permissions need to be set for SQL Server 2005 to allow users to view the Management Activity monitor? They should not be allowed to take actions on the activities.

The Active Monitor tool requires VIEW SERVER STATE permission; this permission is required to select from DMVs such as sys.sysprocesses.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thank you so much! This did the trick.

Barb

|||

Does Management Studio Express support the Activity Monitor?

I've enabled VIEW SERVER STATE for admin and still can't find the Activity Monitor in the GUI.

Thanks

|||

Unfortunately I am not familiar with the different GUI tools available for SQL Express. I would recommend asking this question on the SQL Express forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=385&SiteID=1) instead.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Where do you set this: To view the Activity Monitor the user needs VIEW SERVER STATE permission on a SQL Server 2005 server.

|||

The easiest way is to just open a connection (i.e. using sqlcmd or Management Studio) using your sysadmin credentials and issue the following statement:

GRANT VIEW SERVER STATE TO <<login name>>

This will grant <<login_name>> VIEW ANY STATE permission.

-Raul Garcia

SDE/T

SQL Server Engine