Hi Dwaine,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.

Thank you!

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: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

using version 9.00.4035.00

Your suggestion is not the answer. Changing the connection in step 2 has no
effect, as I described. A different servername is pushed to the OLAP
database.

Unfortunately, the issue is intermittent and I have NOT been able to
determine under what conditions the correct DataSource connection is deployed.

I've simply had to standardize on ALWAYS double checking after deployment
what the resulting target is.

Very sad this isn't bulletproof. Reliable deployment to TEST and PRODUCTION
are, IMHO, very important.

""Charles Wang [MSFT]"" wrote:

Dear Dawine,
Thank you for your response.

Regarding the issue you encountered, since it was intermittent and hardly
reproduced at my side, in this case, I recommend that you further observe
this issue at your side to see if you can find more clues on reproducing
this issue and then let us know. Appreciate your understanding that without
reproducing this issue, it is hard for us to perform dedicatedly research
and resolve it in an elegant way.

Considering the environment specific, I think that currently standardizing
your verification steps should be a good practice in your environment.

You may also give us your feedback on the product at
https://connect.microsoft.com/sql. This is a very good channel for
reporting customers experiences and concerns on using SQL Server to our
product team.

Thank you!


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: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subs.../aa948874.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======