InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 20:42:02 GMT20http://www.sqlservercentral.com/Forums/Topic1407512-17-1.aspx[quote][b]blom0344 (1/16/2013)[/b][hr]Did the T-sql take 5 seconds on the first execution? If not , then results may still be in the memory cache. The MDX may not have that advantage.[/quote]SSAS holds caches for MDX as well.[url=http://msdn.microsoft.com/en-us/library/hh230974.aspx]Clear the Analysis Services Caches[/url]Wed, 16 Jan 2013 14:32:18 GMTKoen Verbeeckhttp://www.sqlservercentral.com/Forums/Topic1407512-17-1.aspxDid the T-sql take 5 seconds on the first execution? If not , then results may still be in the memory cache. The MDX may not have that advantage.Wed, 16 Jan 2013 08:37:29 GMTblom0344http://www.sqlservercentral.com/Forums/Topic1407512-17-1.aspxHard to tell without knowing the exact structures of the database and cube, but I do know SSAS is strong in showing aggregated data, not really in showing data dumps.Wed, 16 Jan 2013 01:06:45 GMTKoen Verbeeckhttp://www.sqlservercentral.com/Forums/Topic1407512-17-1.aspxCan anyone tell me why this simple MDX query takes 9 seconds and TSQL takes 5 seconds?-------------------- MDX ------------------------------- select null on 0, {[Dim Geographic].[STATECODE].children * [Dim Geographic].[COUNTYNAME].children *[Dim Geographic].[CITY].children *[Dim Geographic].[POSTALCODE].children} on 1 from Cube;------------------TSQL----------------------------------select distinct STATEABBRV, COUNTYNAME, CITY, POSTALCODE from DimGeographicorder by STATEABBRV, COUNTYNAME, CITY, POSTALCODETue, 15 Jan 2013 15:52:02 GMTWood Chuck