title: SSAS Connection String when deploying across multiple environments?
body: <p>I have three different environments; Development, Test, and Production.</p>
  
  <p>These three SSAS environments connect to three different SQL Server instances.</p>
  
  <p>The server, though, is hard coded in the SSAS data source so when you deploy, the instance is broken because it points to the wrong, inaccessible, SQL server.</p>
  
  <p>How can you configure the SSAS data source connection string so that its not overwritten when you deploy, OR, how can you make it variable so that it looks up the correct value for the environment its been deployed to?</p>
  
  <p>I've been manually editing the .asdatabase file before deployment to each environment, but this is an unacceptable violation of change control procedures, so I've got to get a more suitable mechanism in place. Maybe there is a very easy solution to this, but if so, I haven't figured it out yet.</p>