Re: long running queries

From: Dave Wickert [MSFT] (dwickert_at_online.microsoft.com)
Date: 01/27/05


Date: Thu, 27 Jan 2005 14:55:54 -0800

I talk about it a bit in the AS Operations Guide.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
See the section titled: "Monitoring User Access"
Mark is right -- you don't have much of an option with SQL Server 2000.

However, there will be some stuff coming in SQL Server 2005 to help. And we
hope to have a utility coming the Beta3 resource kit that will address this.

-- 
Dave Wickert [MSFT]
dwickert@online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Hill" <mark@mark[dash]hill.com> wrote in message
news:2xcKd.235278$f47.45891@news.easynews.com...
>
> <rinkijain@gmail.com> wrote in message
> news:1106855807.092586.38510@c13g2000cwb.googlegroups.com...
> > Hi
> >
> > Is there a way to detect and stop long running queries either in MS
> > Analysis services or through Proclarity (cube browser)? For example if
> > users try to put large dimensions on rows and columns with drill down
> > that would result in a large data set and complex query, we would like
> > to stop them.
> >
> > Rinki Jain
> >
>
> In a word NO, this is a subject very close to my heart because of my own
> experiences.
>
> I don't know if you are using XMLA, if you are then there are some ways to
> manage your user community, give me a shout offline if you want some more
> info on that.
>
> Some of the client tools will warn you if the query looks like its going
to
> return a lot of data , intelligent apps being one of those. I do not think
> Proclarity does this.
>
> I have spoken to MS in depth about this, and there appears to be no
reliable
> way of doing this in AS 2000 once the query has been submitted.
>
> One other approach we did try was closing TCP connections on the server
when
> a certain amount of traffic had been sent down the wire, this is pretty
> crude and IMHO causes more problems than its worth.
>
> Mark
>
>


Relevant Pages

  • Re: Transaction handling - Read Committed
    ... Yes this behavior is due to the Read Committed Isolation level requirements ... and has nothing really to do with SQL Server. ... As Mark pointed out you can ... >>> This query does not return with results till query 1 completes. ...
    (microsoft.public.sqlserver.programming)
  • Re: Query Analyzer
    ... However the data set is only 200 rows and about 10 columns. ... query that takes 2 seconds on the server can take pushing 10 mins. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.sqlserver.tools)
  • Re: Write SQL query into Xml
    ... If you are using SQL Server 2005, check out the FOR XML syntax for your ... It will allow the results to be returned as XML. ... you can use to read XML from the query. ... then call the WriteXml method to write the data set to a stream in XML ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Pulling Data into One Query Fomr Two DatabasesTables
    ... UNION ALL ... >> Need SQL Server Examples check out my website at ... >>> I am looking for the proper statement so I call query the data from ... I need to display the data set for both tables in ...
    (microsoft.public.sqlserver.programming)
  • Re: Pulling Data into One Query Fomr Two DatabasesTables
    ... The Union statement works perfectly within the query Analyzer But, in a view there is an error when I attempt to compile the Statement... ... > tables that are in two databases on the same SQL server? ... I need to display the data set for both tables in one ...
    (microsoft.public.sqlserver.programming)