"dwaine" wrote:

> Sorry, don't know if this is the correct forum for this thread, please
> suggest another if not....
>
> In a cube project you have a Data Source that feeds a data source view that
> defines the data objects used to build a cube. 
>
> You want to CHANGE the data source connection string based on where you are
> deploying, e.g. DEV, TEST or PROD.
>
> In my environment, if I change the data source connection in the IDE, the
> change is persisted in the object and can be viewed in the project.dwproj
> file under the appropriate configuration entry.
>
> BUT, when I DEPLOY (or process) the project (or a cube), the data source on
> the target OLAP database is ALWAYS reset to whatever connection string is in
> the project.ds file!
>
> The target OLAP server is changed, so the deployment is going to the correct
> location, but the DATA SOURCE is changed to an incorrect source that you
> can't really even SEE in the development!  To figure out where the heck the
> connection string is even comming from, you have to manually open the
> project.ds file!
>
> This behaviour makes configuration manager almost useless for deploying
> cubes.  What is the point of using a configuration to push to Production if
> BIDS changes the datasource of production to point to your DEVELOPMENT server?
>
> Somebody, please enlighten me....

> Hi Dwaine,
> Good morning!
> Cube deployment and underlying data source are seperated. They are by
> design allowed to be configured to different location. You can configure
> the target server and target database as the deployment destination in
> Project configurations, and configure the data source by double clicking
> the .ds file in BIDS and then you can configure the data source connection
> in the UI. If you want to manually change the data source connection for a
> SSAS project, you need to modify two files, the project file (.dwproj) and
> the data source file (.ds).
>
> From your description, it looked that you would like an automatic way of
> changing the data source connection according to the target server
> configuration on the project level. Unfortunately currently BIDS is not so
> intelligent that there is no such feature provided.
>
> If you wanted to first change, process and test the cube on your
> development environment and then deploy the OLAP database to the remote
> server but keep the data source connection to the remote server, you can
> try the following steps:
> 1. First processed the entire cube with the existing local database
> connection in your dev environment;
> 2. Change the data source connection by double clicking the .ds file in
> BIDS and specifying the remote SQL Server instance name without testing
> connection.
> 3. Right click your project, click Properties, select Deployment, choose
> "Processing Option" to "Do Not Process", specify the remote server and
> database and click OK;
> 4. Right click your project and click Deploy.
>
> I am not sure if I totally understand your meaning. If there is anything
> unclear, please do not hesitate to let me know. I will do my best to help.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =========================================================
> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msd***@microsoft.com.
> =========================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================
>
>