Friday, March 9, 2012

OLE DB timeout processing AS Cube

When doing a full process of the Analysis Services Cube with several partitioned measure groups. We receive: "OLE DB error: OLE DB or ODBC error: Query timeout expired HYT00" or "OLE DB error: OLE DB or ODBC error: Query timeout expired HY008". There are 410 million rows in one base table and 80 million rows in another base table. The other measure groups process fine. It has abended at 61 minutes the last 3 times. I can individually process each measure group successfully.

Any help is greatly appreciated, Edwina Derrick

Simular problem for me. Have a huge database to be queried and can't pass the 60 minutes query time despite having made sure that ALL!! timeout values are suposed to be eternal (zero in most cases). This seems like a bug to me. I used the developer release version of the SQL2005. Would appriciate the Microsoft development team to test this problem and to suply information of when and how to bypass this 1 hour timeout limitation.

|||Try increasing ExternalCommandTimeout Analysis Server advanced property.

Being in situation when Analysis Server needs to wait for an hour for some data to come from SQL Server is very unusual. Such situation ususally means that SQL server needs to perform some heavy operation before it can start sending data out. Try optimizing your SQL Server database.
Edward Melomed (MSFT)


This posting is provided "AS IS" with no warranties, and confers no rights.|||

WTF....

isn't there a way to set the timeout?

If I was able to "Optimize my SQL Server database".....

I have five fact tables (All of them are required) and each table has it's own Dimensions.

since I am unable to create a cube on a left join relationship I need to work with views ("SQL server needs to perform some heavy operation before it can start sending data out").

No comments:

Post a Comment