cancel
Showing results for 
Search instead for 
Did you mean: 

Using MS-SQL Replication for Phased Upgrade from 7.5 to 10.0 MS

former_member187113
Participant
0 Kudos

Hi,

We are looking to upgrade SAP BPC 7.5 (MS) to SAP BPC 10.0 (MS) on separate servers. The application is large with a lot of schedules and reports, written in EVDRE/EVGET, etc. As is, some of these may work in BPC 10.0 straight-off, most may not.

There is one AppSet / Environment.

Since a big bang approach (migrating ALL Models to EPM 10.0) in one shot is going to take a lot of time and could be risky in terms of timing, user adoption and the like, the thinking is to have the various Models migrate at different times. To keep the FACT data in sync across the servers, I am thinking of using MS-SQL Replication (Pub / Sub) on the FACT tables to push from the 7.5 server to the 10.0 server.

As an example, assume there are 4 Models, A, B, C, D. Once A is migrated to 10.0, users would use EPM (connecting to the new server) to access 10.0 schedules and reports, while for B, C, D, they would use 7.5 (which will still be connected to the old server).

The SAP BPC 10.0 server would be the subscriber (recipient). (Not sure if I need bi-directional replication)

Maybe someone has done something like this before ... Any ideas? A good idea? Bad idea?

Kind Regards

Nick

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

If you will allow in this scenario appset A to be updated and used simultaneously in both BPC 7.5 and 10 that will cause you some serious trouble. If you enforce one of the BPC deployments (the BPC 7.5 for example) to be read-only for appset A - that is no data loads, no input schedules or no journals to be sent - then you should be fine.

former_member187113
Participant
0 Kudos

Thanks, Stefan

At the moment there is no journal usage at all, all the cube data is load or inputs.


There are four Applications (Models). The most important one is the Management Reporting one, since it drives the other models (for example, the Statutory Model refers a lot to the Management Reporting Model).


My thinking was to migrate the Statutory Model first, with inputs (loads and manual inputs) going into the BPC 7.5 system and then being replicated to the BPC 10.0 system (just the FACT data). Inputs made in the Statutory system in the 10.0 model remaining there.


After that the Management Model migrates across.


Then the other two. (They are self contained in that data is copied across application)

There probably is something I am not thinking of and it will cause a lot of serious hassle later on. I guess it just means a Big Bang approach to deploying the 10.0 system.

Thanks, again.

Nick

Answers (0)