![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am working with a cube with 10 million rows. A drill through on the Cube fails due to a Timeout. I have set the timeout on the AS properties to 240 seconds, i.e. 5 mins, the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion\MaxOLEDBTimeout value is also seen to be 240 seconds. I am using MSAS SP3. Please suggest a way to fix this problem? The storage type of the Cube is MOLAP, and the fact table is on the same windows server, on SQL Server 2000. Thanks, Geeta |
#3
| |||
| |||
|
|
-----Original Message----- Geeta: Is the error being initiated by AS or SQL Server? If SQL Server: As the DRILLTHROUGH actually executes a SQL query on the underlying data structures (in this case SQL Server, if I read correctly), then the remote query timeout property (set either through sp_configure or in the EM through Server Properties, Connections, Remote Server Connections) is probably not set to 0 (unlimited). If this is not the issue (i.e., the SQL Server timeout is not 0), then you might want to look at KB 304213. This article also gives some detail on how to change the DSO timeout in AS. MTI "Geeta" <geeta_pajjuri (AT) hotmail (DOT) com> wrote in message news:00d101c3aec3$a7d9cb30$a401280a (AT) phx (DOT) gbl... I am working with a cube with 10 million rows. A drill through on the Cube fails due to a Timeout. I have set the timeout on the AS properties to 240 seconds, i.e. 5 mins, the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion\MaxOLEDBTimeout value is also seen to be 240 seconds. I am using MSAS SP3. Please suggest a way to fix this problem? The storage type of the Cube is MOLAP, and the fact table is on the same windows server, on SQL Server 2000. Thanks, Geeta . |
![]() |
| Thread Tools | |
| Display Modes | |
| |