Hi Gurus,
I am in the process of implementing the upgrade project and would like to have your valuable inputs to achieve the completion of project.
Technical Details :
Source System : ECC 6 /NW SPS 9 with Kernel 700
OS : Windows 2003 & DB : MSSQL Server 2005
3 System Landscape
Target System : Upgrade to ECC 6 with EHP 7 ( Abap Stack)
New OS : Windows 2012 & New DB : MSSQL Server 2012
I have already gone through Recommended guides & Sap Notes/PAM where it mentions that we need to upgrade the OS /DB to either Windows 2008/2012/2014 and Sql 2008/2012/2014. I am also aware that NW SP patch level is one of the pre-requisite for the DB Upgrade.
In my current scenario , We are going with OS/SQL 2012, and one of the per-requiste as per the note 1651862 , NW Sp should be upgraded to SPS26.
My Approach will be as follows,
I will be using 2 Systems .as POC before stepping up into current landscape.
System A : - Build a system copy using production database same as source system in terms of SPS ,Kernel ,DB etc and perform SPS upgrade and take the patch level to SPS 26 .
System B : - New System will be with Windows 2012. Will perform system copy using system A and then upgrade MS SQL Server 2005 to 2012.
Once done , will go for EHP7 direct Upgrade ( ECC 6 SPS 26 to ECC EHP7 SPS 11)
Please correct me ,if I am wrong with the above approach.
My real question ,
Can I Upgrade directly to EHP7 without NW SPS 26 Upgrade ( All in on single step). Below approach
1.System Copy using old production data on New Windows 2012.
2.Upgrade SQL Server from 2005 to 2012.
3.Direct Upgrade using SUM in one single shot NW SPS 26 , EHP 7 SP 11 & NW 7.4 .I am getting confused because I generated stack file from my solman system and it took all required upgrade stack . Attached screenshot.
If I go with above approach will it work or any issues will come during upgrade.
Please Note as per Sap note 1651862, you should first upgrade sps before upgrading sql server 2012 .
Regards
Asim
Hi Asim,
you cannot directly upgrade to EHP7 without having the intermediate step to SPS26.
As there are some functions/prerequisites delivered with the packages they have to be implemented first. We often had these discussion and asked the development of SQL server and they confirmed that the SPS26 is mandatory before upgrading the database.
So your roadmap should be:
Cheers,
Andreas
You will need to do a system copy as an in-place upgrade of Windows is not supported. You also need a supported OS and DB to update the system to EHP7.
So the solution for you is:
1 - Apply the required SPS
2 - Perform system copy using R3load export/import to the target OS/DB
3 - Plug the new system to Solution Manager and generate the stack file
4 - Upgrade the SAP system to EHP7
There is no need to perform a DB upgrade if you use R3load export import system copy as you can set up the target system with MSSQL 2012. You can also enable compression during this activity.
Hi Asim,
I am in a similar situation like you. I have to upgrade our ECC 6 to ECC 6 EHP7.
I am OK till Sandbox System, but how can we proceed in productive landscape. Do we have to perform same steps in DEV --> QAS --> PROD systems as well.
If you could help and suggest me the best approach to achieve this task successfully, I will be very thankful to you.
Regards
Ahsan
Add a comment