Mem to Leave...

Are there any tools or documentation available anywhere that describes how
one can monitor the usage/fragmentation of the mem to leave area used by SQL
Server? (SQL2K on W2K3 2 Node Cluster)One tool is VMStat. You can download it with the psslabs2004
download. You can download it from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=aec18337-887f-4ec6-a858-81f84de8082f&DisplayLang=en
-Sue
On Mon, 23 Jan 2006 12:25:02 -0800, "Cyberstorme"
<Cyberstorme@.discussions.microsoft.com> wrote:
>Are there any tools or documentation available anywhere that describes how
>one can monitor the usage/fragmentation of the mem to leave area used by SQL
>Server? (SQL2K on W2K3 2 Node Cluster)sql

Mem to Leave...

Are there any tools or documentation available anywhere that describes how
one can monitor the usage/fragmentation of the mem to leave area used by SQL
Server? (SQL2K on W2K3 2 Node Cluster)
One tool is VMStat. You can download it with the psslabs2004
download. You can download it from:
http://www.microsoft.com/downloads/d...DisplayLang=en
-Sue
On Mon, 23 Jan 2006 12:25:02 -0800, "Cyberstorme"
<Cyberstorme@.discussions.microsoft.com> wrote:

>Are there any tools or documentation available anywhere that describes how
>one can monitor the usage/fragmentation of the mem to leave area used by SQL
>Server? (SQL2K on W2K3 2 Node Cluster)

Mem to Leave...

Are there any tools or documentation available anywhere that describes how
one can monitor the usage/fragmentation of the mem to leave area used by SQL
Server? (SQL2K on W2K3 2 Node Cluster)One tool is VMStat. You can download it with the psslabs2004
download. You can download it from:
1f84de8082f&DisplayLang=en" target="_blank">http://www.microsoft.com/downloads/...&DisplayLang=en
-Sue
On Mon, 23 Jan 2006 12:25:02 -0800, "Cyberstorme"
<Cyberstorme@.discussions.microsoft.com> wrote:

>Are there any tools or documentation available anywhere that describes how
>one can monitor the usage/fragmentation of the mem to leave area used by SQ
L
>Server? (SQL2K on W2K3 2 Node Cluster)

MDX Query Governor ?

Hi,

There are 2 problematic cases that would require some kind of MDX Query Governor or time out:

- User leave an endless query running forever

- User cancel an endless query on the client and it does not get cancelled on the server

I looked into the server properties and saw a couple items like Admin Time out, External Connection Time out etc.

Which one of these properties should I use to get the SSAS server kill run-away queries that where either let go or canceled on the client side but still run and eat the CPU on the server? My take is that any Client issued MDX lasting over 30 minutes should be automatically cancelled on the server.

Right now I restart the server when it get too bad but it is not a solution, one cannot work with a server that need restart every single day.

It is also unpracticable to have anyone spending valuable time chasing down useless connections/queries and cancelling them manually.

Thanks,

Philippe

For one I suggest you take a look at the ActivityViewer sample application to see long running queries. You can also use it to cancel user sessions and connections to free up server resources.

Governing resources is not a simple problem to solve. We are working on it and hope that in the next version your will see greater responcivencess of Cancel and you will see better ways to detect and cancel runaway queries.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.