May 18, 2017 at 3:58 am
Hi all
We're trying to deploy cubes to a DEV server (and from there to PROD after testing) but we're having an issue with roles and membership.
I've gone through the deployment wizard and set it to retain roles and members.
Unfortunately, when we deploy, the system seems to ignore that and deploys the roles and members anyway.
This is the contents of the deploymentoptions file:-<DeploymentOptions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl200="http://schemas.microsoft.com/analysisservices/2010/engine/200" xmlns:ddl200_200="http://schemas.microsoft.com/analysisservices/2010/engine/200/200" xmlns:ddl300="http://schemas.microsoft.com/analysisservices/2011/engine/300" xmlns:ddl300_300="http://schemas.microsoft.com/analysisservices/2011/engine/300/300" xmlns:ddl400="http://schemas.microsoft.com/analysisservices/2012/engine/400" xmlns:ddl400_400="http://schemas.microsoft.com/analysisservices/2012/engine/400/400" xmlns:dwd="http://schemas.microsoft.com/DataWarehouse/Designer/1.0">
<TransactionalDeployment>false</TransactionalDeployment>
<PartitionDeployment>DeployPartitions</PartitionDeployment>
<RoleDeployment>DeployRolesRetainMembers</RoleDeployment>
<ProcessingOption>Default</ProcessingOption>
<OutputScript></OutputScript>
<ImpactAnalysisFile></ImpactAnalysisFile>
<ConfigurationSettingsDeployment>Deploy</ConfigurationSettingsDeployment>
<OptimizationSettingsDeployment>Deploy</OptimizationSettingsDeployment>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</DeploymentOptions>
I can see the section for RoleDeployment and I've tried changing it to RetainRolesRetainMembers but it gets overwritten when we deploy.
We're using Visual Studio 2012 to build/process/deploy the cubes from a DEV point of view (and I'm assuming the same behaviour if we deploy to our PROD environment).
I've also generated a script from the deployment wizard but I can't see anywhere in the there about retaining roles/members.
Does anyone know how I can get the roles/members to not be deployed when I deploy the cube?
May 18, 2017 at 12:12 pm
Would creating a 'create database' .xmla script (right click on database in dev and script out create) work? Take the script to your test server and create there. (Delete the OLAP database in test if it already exists with the same name) Be careful to search the create script for the ConnectionString property to update for whatever it should be in test. After create on dev, process the cube, then you should be good to go.
I've done that many times to deploy cube changes between environments. Not sure if it will work in your situation -- just a thought.
Hope this helps,
Rob
May 19, 2017 at 1:48 am
I hadn't thought of that so I'll have a look.
How would that work if we need to make changes to the cube and deploy without changing roles/members?
May 22, 2017 at 5:54 am
richardmgreen1 - Friday, May 19, 2017 1:48 AMI hadn't thought of that so I'll have a look.How would that work if we need to make changes to the cube and deploy without changing roles/members?
Are your roles/membership the same in both environments? If not, then you would have to update those in the create .xmla as well -- I've never had to do this as we've had always had a fairly simple environment where a certain AD role had read rights and another role had admin/processing rights. So it was the same in both dev, test and production.
Good luck,
Rob
May 22, 2017 at 6:29 am
No, we decided against AD groups as it would get complicated.
We've got a few cubes and users have different rights in each one.
There are 6 roles just for one cube (in production) and less in development.
We've got the roles and members in Visual Studio (for source control) and I don't want to start messing around with those.
I also don't want to have to go into Visual Studio to add/remove a role member and the have to deploy the cube all over again for such a minor change.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply