Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
marcosag
Starting Member
1 Post |
 Posted - 2003-04-24 : 09:53:23
|
| In my firm, we have developed a two - level datawarehouse which is composed by a part on mainframe (DB2 database) and another on a departmental server (SQL server 2000 database). Final users inquiry the information stored in both the databases through BO universes. In order to check the use of resources, we have installed a DB2 tool (RLF - Resource Limit Facility) that automatically kill final user query exceeding 30 seconds CPU usage. My question is: Is there a similar tool in SQL Server2000 ? How we can check and administer the resources use on dipartmental server?Thanks for your help |
|
|
dsdeming
479 Posts |
Posted - 2003-04-24 : 10:02:32
|
| Take a look at "query governor cost limit Option" in BOL. I think it will do what you're looking for.HTH |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-04-24 : 10:09:37
|
| Have doubts about that but never tested it.It works on the estimated cost (which may be what you want).Doesn't take into account whether data is in memory, ...You might consider a scheduled task which monitors sysprocesses and kills an process that has exceeded your limit from that application.This may not be what you want either because queries may not die immediately - and a rollback can take a lot longer than the update.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy.Edited by - nr on 04/24/2003 10:12:11 |
|
|
|
|
|
|
Kill heavy queries in SQL Server