Skip to Content

OS DB migration with SAP ECC - EHp4 on SQL server 2008 r2 and Windows 2003

Oct 31, 2016 at 06:52 PM


avatar image

hi all,

We are checking the possible and best possible approaches for migration to new hardware /OS & DB with SAP upgrade to ECC 6.0 EHP7

current landscape:

SAP ECC 6.0 EHP4/NW 7.01 SP5, windows 2003 & SQL 2008 r2

DB size : 5 TB

New landscape:

New Hardware, windows 2012, SQl server 2016, SAP ECC- EHP7.

Option 1:

a)Upgrade on current landscape to ECC-EhP7

b)migrate to new landscape homogenous apprach

option 2:

a)Migrate to new hardware /OS/DB using homogenous approach and

b) Upgrade on new landscape

option 3:

Is it possible for upgrade and migrate in 1 downtime ?

Please suggest.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Matt Fraser
Aug 23, 2017 at 04:38 PM

Hi Gadde,

I realize this is a very old question. Also, note in my moderator comment that I changed the tags on it, as your question is not about the Enterprise Portal. Upgrade and system copy/migration questions belong to Software Logistics.

My advice to you would be your Option 2: migrate to the new hardware on the higher-level Windows and SQL Server platform, then perform the application upgrade. Double-check in the PAM that your start release (EhP4 on NW 7.01) works with SQL 2016 (I haven't checked this myself), but the move to Windows 2012 R2 should not present a problem for NW 7.01.

You do need to confirm in advance via the PAM and SAP Notes that your target OS and DB release are compatible with both your start and target application/netweaver release. If so, then performing the hardware migration first makes sense. If not, check whether your source OS and DB are compatible with your target application release, and that might force you to do things in the other order.

For reference, we recently upgraded from EhP4 / NW 7.01 to EhP8 / NW 7.5 on Windows 2012 R2 / SQL 2012. We did the migration to Windows/SQL 2012 on new hardware a couple years in advance of the application upgrade and had no problems running EhP4 on them.


10 |10000 characters needed characters left characters exceeded