Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    Hi. Thanks for your reply. I need to set aside some time to watch your vid and take it all in. I have seen the Fast Track DW docs. Ideally id like to work through this methodically, but im thinking that the fastest way out of my quagmire is to refer to the FTDW docs and say "64Gb minimum... because... Microsoft say so". Commented Feb 15, 2016 at 7:14
  • How relevant is caching data in memory if users are hitting the olap cube but not the underling table? As i understand it SSAS will utilise sql server when processing but is caching aggregations in files on disk. So provided users are only hitting aggregated data, there should be little I/O through SQL. Is that correct? Or am i talking hogwash? Commented Feb 16, 2016 at 5:58
  • @Peter - you were talking about performance issues when doing ETL and building the cubes. That data comes from the database, right? If you're changing courses and now you're talking about end-user-facing performance, then correct - but you may want to reword your question then. Commented Feb 16, 2016 at 11:25