I thing DB2 can do it

I know that DB2 has something called the “Query Patroller” that can be u
seed
to proactively and dynamically control the flow of queries against your DB2
database in the following key ways:
a. Define separate query classes for queries of different sizes to better
share system resources among queries and to prevent smaller queries from
getting stuck behind larger ones
b. Give queries submitted by certain users high priority so that these
queries run sooner
c. Automatically put large queries on hold so that they can be cancelled or
scheduled to run during off-peak hours
d. Track and cancel runaway queries
The purpose of this is to allow you to regulate your database's query
workload so that small queries and high-priority queries can run promptly an
d
your system resources are used efficiently.
I don’t thing these thing are unreasonable requirements for a database
server in the enterprise. I’m surprised the this seems so hard to do on Sq
l
server.
Have anyone looked into the features on the Sql server 2005? Any
improvements there?
Are there any of you guys that has been struggling with the same problems
and found a solution or a workaround?
"pehuan" wrote:

> When you run a process on you Windows machine, you can set the process
> priority to 'low', if you don't want the process to take resources away fo
rm
> other processes running in the same timeframe.
> Does anyone know of a similar technique for long running queries on Sql
> server 2000 or 2005?
> I have a series on long running analytical queries, where the query
> execution time is not important, and I don’t want them to take any resou
rces
> away form other queries running in the same timeframe.
> I would like a way to tell the Sql server – “run this, but if anything
else
> happens, give that the first priority!”
> Any suggestions?
>
>Read up this article
http://www.databasejournal.com/feat...cle.php/3427581
"pehuan" <pehuan@.discussions.microsoft.com> wrote in message
news:66FFBDA0-98CA-44F3-A4ED-A3B43958C546@.microsoft.com...
> I know that DB2 has something called the Query Patroller that can be
useed
> to proactively and dynamically control the flow of queries against your
DB2
> database in the following key ways:
> a. Define separate query classes for queries of different sizes to better
> share system resources among queries and to prevent smaller queries from
> getting stuck behind larger ones
> b. Give queries submitted by certain users high priority so that these
> queries run sooner
> c. Automatically put large queries on hold so that they can be cancelled
or
> scheduled to run during off-peak hours
> d. Track and cancel runaway queries
> The purpose of this is to allow you to regulate your database's query
> workload so that small queries and high-priority queries can run promptly
and
> your system resources are used efficiently.
> I dont thing these thing are unreasonable requirements for a database
> server in the enterprise. Im surprised the this seems so hard to do on
Sql
> server.
> Have anyone looked into the features on the Sql server 2005? Any
> improvements there?
> Are there any of you guys that has been struggling with the same
problems [vbcol=seagreen]
> and found a solution or a workaround?
>
> "pehuan" wrote:
>
form[vbcol=seagreen]
resources[vbcol=seagreen]
else[vbcol=seagreen]