![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, We have a web front end through which users will submit requests. Some of our dimensions are large (About 1.7 Million members). Users can stack up to 3 dimensions on each axis. Most of the requests complete in less than 5 to 10 minutes from MOLAP MSAS 2005 cubes. But there are few requests that ran for more than 2 hours. And recently we had 5 such requests that ran about the same time and it brought the server down. I would like to have a facility (kind of DB2 Governor) where it stops long running MDX statements say 90 minutes and save them in a log. This way at least the server would not go down. Obviously, we will monitor the log and improve the quality of the MDX statements? I am not sure if there is such server side facility available on the MSAS 2005 server or a server side MSAS 2005 setting that can a set up a threshold in terms of minutes? Thanks for your help, Prasad. |
#3
| |||
| |||
|
|
You can set a server timeout to try to cancel queries that take too long. You will need to set two timeout properties ServerTimeout and AdminTimeout in the file msmdsrv.ini. Make sure you set AdminTimeout to a very large value -- it controls the timeout for administrative operations. Also, there is a sample application that is available called Activity Viewer -- you can use this to try and view and cancel long-running commands. But be aware that not all queries will cancel very responsively... Thanks, Akshai -- Try out the MSDN Forums for Analysis Services at: http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1 This posting is provided "AS IS" with no warranties, and confers no rights Please do not send email directly to this alias. This alias is for newsgroup purposes only. "Prasad" <Prasad (AT) discussions (DOT) microsoft.com> wrote in message news:6E3EA7F0-79E2-4EEC-B3C2-5645D491D9F3 (AT) microsoft (DOT) com... Hi, We have a web front end through which users will submit requests. Some of our dimensions are large (About 1.7 Million members). Users can stack up to 3 dimensions on each axis. Most of the requests complete in less than 5 to 10 minutes from MOLAP MSAS 2005 cubes. But there are few requests that ran for more than 2 hours. And recently we had 5 such requests that ran about the same time and it brought the server down. I would like to have a facility (kind of DB2 Governor) where it stops long running MDX statements say 90 minutes and save them in a log. This way at least the server would not go down. Obviously, we will monitor the log and improve the quality of the MDX statements? I am not sure if there is such server side facility available on the MSAS 2005 server or a server side MSAS 2005 setting that can a set up a threshold in terms of minutes? Thanks for your help, Prasad. |
#4
| |||
| |||
|
|
Hi, Thanks for the reply. Where can i downaload a copy of the Activity Viewer? Also can i run it on my desktop and connect to the MSAS 2005 server? or do i have to install on the MSAS 2005 server itself? Please let me know. Prasad. "Akshai Mirchandani [MS]" wrote: You can set a server timeout to try to cancel queries that take too long. You will need to set two timeout properties ServerTimeout and AdminTimeout in the file msmdsrv.ini. Make sure you set AdminTimeout to a very large value -- it controls the timeout for administrative operations. Also, there is a sample application that is available called Activity Viewer -- you can use this to try and view and cancel long-running commands. But be aware that not all queries will cancel very responsively... Thanks, Akshai -- Try out the MSDN Forums for Analysis Services at: http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1 This posting is provided "AS IS" with no warranties, and confers no rights Please do not send email directly to this alias. This alias is for newsgroup purposes only. "Prasad" <Prasad (AT) discussions (DOT) microsoft.com> wrote in message news:6E3EA7F0-79E2-4EEC-B3C2-5645D491D9F3 (AT) microsoft (DOT) com... Hi, We have a web front end through which users will submit requests. Some of our dimensions are large (About 1.7 Million members). Users can stack up to 3 dimensions on each axis. Most of the requests complete in less than 5 to 10 minutes from MOLAP MSAS 2005 cubes. But there are few requests that ran for more than 2 hours. And recently we had 5 such requests that ran about the same time and it brought the server down. I would like to have a facility (kind of DB2 Governor) where it stops long running MDX statements say 90 minutes and save them in a log. This way at least the server would not go down. Obviously, we will monitor the log and improve the quality of the MDX statements? I am not sure if there is such server side facility available on the MSAS 2005 server or a server side MSAS 2005 setting that can a set up a threshold in terms of minutes? Thanks for your help, Prasad. |
![]() |
| Thread Tools | |
| Display Modes | |
| |