Perms, perms, perms (or deploying BAM activities with cubes when Analysis Services runs as a different service account)

This will be the first of a two part blog post about real-world adventures in BAM deployment.  As time has proven over and over, permissions and environment variables tend to trip even the most careful planners up when deploying artifacts to non-development environments.   I have developed a BAM solution for a customer which has been…

0

The right tool for the right job

Here’s a little gem I discovered today.  I am running down a permissions issue with BAM and SQL Server Analysis Services.  On my local dev box, I wanted to fully emulate the permissions from my full-blown dev environment, so in my Services MMC, I changed the Analysis Services log on account from LocalSystem to the…

0

Minimal security settings for a Analysis Services service account

As an add-on to my previous post about adding Analysis Services to an existing SQL cluster, I thought it might also be helpful to list the various security settings which need to be set to allow SSAS to not only run but accept connections.  Again, in a dev environment, if your “service account” is an…

2

Setting up Analysis Services on an existing SQL cluster

Another infrastructure issue that I ran into while deploying my BAM solution out into the “real” world was that in our post-dev environments SQL is clustered and we would be installing Analysis Services to a cluster which already has SQL Server installed, so I decided to “practice” installing Analysis Services to a SQL cluster in…

5