Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Analysis SSAS 2008-64 bit

Analysis SSAS 2008-64 bit

Analysis SSAS 2008-64 bit

Can someone please provide me some articles or recommendations about SSAS configurations for optimal performances.

Good Luck.

RE: Analysis SSAS 2008-64 bit

Well the general answer would be. Lots of memory, lots of CPU power (64bit) lots of drives.

Like everything else it depends on a number of other factors.

1) How many other apps will be running on the server?
2) Will it co-exist with the underlying RDBMS?
3) Number of Olap Databases?
4) Number of Cubes?
5) Number of concurrent users?
6) Size of Cubes
7) Size of underlying data?
8) Data Load Method.
9) Data Refresh Frequency?

These are just the things that I thought of while replying if I sit down I could probabaly double or triple the number of things to consider.

The main thing to understand is that SSAS will use everything you give it.  A small cube on a server with lots of memory could in theory exist completely in memory after enough queries.  This is pretty much the goal when it comes to SSAS you want enough memory for SSAS to easily build the cube aggregates, and have enough memory to cache as many results as possible.  You want enough drives, not storage, so that sufficient IO exists to read data from disk for values not in cache.

Like configuring a MS SQL Server system you need to know specifics to optimize your system.   

RE: Analysis SSAS 2008-64 bit

64-bit hardware, multiple CPUs and Enterprise editions of Windows Server and SQL Server are the way to go for anything bigger than a small-medium implementation, particularly anything involving data warehousing or is likely to have a large number of users.

OLAP Performance is also heavily dependant on a good dimensional model design and cube design - even a powerful server will struggle with a badly designed cube. Some cube design best practices here:


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close