Archives of the TeradataForum

Message Posted: Tue, 26 Aug 2003 @ 21:34:36 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Craig,

Can only suggest the following:

1. Server Timeout Setting - Make sure this is set to no timeout: Right Click on your Analysis Server >> Properties >> Processing Tab >> Server Timeout checkbox (should be unchecked - also should be set to 0 = unlimited. If you have any number here other than zero, than MSAS is timing out.

2. Process your Dimensions separately from processing the cube.

3. I'm not aware of Query Timeout Settings on either the OLEDB Provider or ODBC Driver Properties (only Connection Timeouts). I think this is an application parameter (could be wrong here).

4. As Clay mentioned, if you are using Teradata OLEDB Provider, you may want to try OLEDB for ODBC + Teradata ODBC Driver. Recommend you use ODBC 3.2.0.5 or above. Also, make sure you are using the very latest Teradata OLEDB Provider. Verify latest SSAS Service Packs too. Won't hurt to stop the MSAS Service and Restart it as well.

5. Capture and test the SQL generated by MSAS and paste into Queryman (Teradata SQL Assistant) or BTEQ and see if the problem is replicated there. If so, log an incident with Teradata Support.

6. Connection Timeout Settings are set through either the OLEDB Provider and/or ODBC Driver (if you are using OLEDB for ODBC + Teradata ODBC Driver). However, it doesn't sound like Connection Timeouts are your problem. You seem to have a Query Timeout issue.

7. Visit the Microsoft Newsgroup Site: MICROSOFT.PUBLIC.SQLSERVER.OLAP. I am told that is a monitored site and you should get a response.

God Luck.

Steve Greenberg

Teradata Partner Engineering
San Diego, California 92127

	<Prev	Next>		<<First	<Prev	Next>	Last>>