SQL Server and SSAS together in the box

  • I have a server where SSAS and SQL instances are running in the same box. SSAS activity usage seems to be v high. Does it make sense to isolate the SSAS instance to another node so that a combined usage of CPU will go down?
    But what are the challenges to it? Say, if SSAS is moved to a new server will it have a lot of network usage between SQL and SSAS? Or once the cube is generated the process will only connect to SSAS?

    Please provide some guidance,

    Thanks.

  • Everything is again "It Depends" on this one.

    Is it better to isolate, it depends if SSAS is taking to much resource that the other processes on the server are not responding properly.
    Is it better to move SSAS to another node, again depends on what can be done with the existing machine, can you add more CPU, RAM, etc, if not can you look at process affinity, RAM throttling etc.
    Will it cause more network to move it to a new host, again it depends, what mode is the Cube in?  MOLAP / HOLAP / ROLAP?  Depending on each one will depend how much its going to go back to the SQL box and cause network traffic.

    Challenges, more licensing, more recourses, another server to manage, internal politics etc

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply