January 13, 2014 at 4:20 am
Hello all,
This is my first post and I think this is a challenge.
Our current SQL server is running at 2008 r2 and we want to migrate to a new server, which is running 2012.
The migration from 2008 r2 to 2012 isn't the challenge.
The challenge lies in the fact that all the Excel connections to SSAS should be able to continue te work after the migration.
The new server receives a new name, that is consistent with the naming convention in our new datacenter.
So, the challenge; How can we migrate and at the same time keep all the Excel SSAS connection working and therefore spare the users a lot of work in changing thousands of Excel sheets?
==Details==
Let's give the servers some names:
- Old server; OldX
- New server; NewY
Example of a current connection definition;
- Connection string
Provider=MSOLAP.5;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=Company Cubes;Data Source=OldX;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error
- Command Text
Company Enterprise Cube
The old server will be shut down after the migration and therefore no configurations can be made there.
The domain is currently running at 2008 r2 level. The DNS servers are running at the same OS.
Unfortunately the connection files have been saved in the Excel workbooks.
Many thanks in advance! 😀
January 13, 2014 at 4:38 am
The connections inside the Excel sheets should not be saved inside the Excel workbook itself, but in an external connection file. If this is the case, you can just modify the connection file.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 13, 2014 at 5:21 am
Thanks Koen!
Unfortunately the connection files have been saved in the Excel workbooks.
To confirm by example; A user can send an Excel sheet to another user and the 2nd user can refresh the pivot, without creating any connections or an existing connection being used that is stored on the computer.
January 13, 2014 at 5:23 am
That's too bad.
If you'd store the connection files on a shared drive, you'd be able to update the connection string once and every Excel workbook would pick up the changes.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply