The feature with SSIS packages to "keep them in the dark" with configurationfiles and the use of variables. How does or does that apply for SSAS projects ?
Since we keep dev, test and production sepperate, the cubes datasource differ according to witch enviroment they are running on. Is there a way to fix this, or what is best practice on this front ?
Whe you talk about "keep them in the dark" are you referring to the following article : http://www.sqlmag.com/Articles/ArticleID/47688/pg/2/2.html ?
I guess this is not widely accepted terminology.
For being able to change some project properties while deploying you can take a look at the Deployment Wizard utility. It gives you abilty to change connection strings during deployment.
No comments:
Post a Comment