Windows OS and SQL DB upgrade with EHP 8 upgrade

[former_member459345]

Hello Experts,

Need guidance in upgrading my EHP4 for SAP ERP 6.0 (EHP1 FOR SAP NETWEAVER 7.0) to EHP8 for SAP ERP 6.0 with OS and DB upgrade.Current OS and DB is on Windows 2008 R2 and MS SQL 2008 respectively which is been planned to upgrade to Windows 2016 LTSB and MS SQL 2017.Below is my plan:

1) Update SAP SPS level to 18 from SPS 6(As per snote minimum sps required to migrate to windows 2016 and ms sql 2017)

2) Install new server with windows 2016 ltsb and ms sql 2017

3) Move old DB 2008 to new DB 2017(detach/attach)

4) Install target system (distributed landscape)

5) Start EHP8 upgrade

My question here is can i use detach/attach method to copy my sql 2008 to sql 2017 ( can this be done? )and then start target system installation with system copy option for DB installation.I will be installing distributed landscape sap application and DB on other system.

Can anyone guide me if detach/attach will work and what other steps required to complete this.

Regards

Akif Shaikh

[Matt_Fraser]

akifshaikh1980 and db8ac33b71d34a778adf273b064c4883

With regard to the notifications, you aren't getting them because they go to the sender of the "parent" item you are replying to. So, an "Answer" will notify Akif, because these are directly in reply to the question itself. If you want to notify someone who provided an answer, you have to reply as a "Comment" in reply to the "Answer," rather than a new Answer to the Question. You've both been replying with new Answers, when really you should be having a threaded conversation in Comments. This would solve your notification issue, and keep the thread more clearly related to a single Answer, in case someone else provides a new Answer to spawn its own thread.

I can convert your various replies to Comments if you wish -- you let me know, as I don't want to confuse the issue -- or leave it as-is for now.

Cheers,
Matt

[Matt_Fraser · Accepted solution]

Akif (and db8ac33b71d34a778adf273b064c4883 ),

I'm not sure you need to actually upgrade your SQL Server installation at all. The requirement of at least SP3 for SQL 2008 R2 is for an in-place upgrade, and that's not what you're doing. You're installing a fresh instance of SQL 2017 onto a fresh instance of Windows 2016 on fresh hardware, and then either doing a backup/restore or a detach/attach to move the existing database onto the new server. This should work just fine, although as mentioned in the Microsoft article Bartosz linked, in the section about upgrading from SQL 2005, you may need to run ALTER DATABASE to change the compatibility level after the restore or attach (see https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-u....

After restoring the database onto the new server, you would then just run SWPM to install SAP, using the "System Copy" options for target installation. This is what you are doing, after all, a system copy. If it's an ABAP system, there is no need for export/import, nor would I recommend going that route (totally unnecessary for SQL Server, unless it's a Java system).

You do need to ensure that your SAP system is on the right SP stack to support the new Windows and SQL versions before you backup/detach the source database, so you're right that your first step is a Support Package Stack update.

You could potentially reduce the business impact -- and the risk -- by splitting this project into three phases, each with their own mini-GoLive:

1. Support Package Stack update on source system
2. System Copy to newly-installed system with new Windows/SQL versions
3. SAP upgrade on new system

During the System Copy phase, just make sure you have the right kernel release and patch level to support the new OS/DB versions. You should be able to double-check that between Notes and the PAM.

Overall, I agree that you have a sound plan. I've done this myself a few times in the past.

Cheers,
Matt

[BJarkowski · Accepted solution]

Are you sure you can restore the database from SQL 2008 to the latest revision? I remember I had some issues with it before. To be honest I thought there is a limit of two releases you can go up (yeah, it sounds strange for me as well).

But my source database was very old... probably SQL 2005 or even SQL 2000.

EDIT: I found this which confirms that you're correct:

https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-a-database-to-a-new...

My database had to be older. Sorry akifshaikh1980 for the confusion!

[Matt_Fraser · Accepted solution]

db8ac33b71d34a778adf273b064c4883 ,

I see you already answered it, but yes, I was reasonably certain. In any case, Akif said he was going to sandbox it first, so he will know for sure before he commits to a strategy.

I do recall that there were restrictions on importing databases that were exported from pre-2005 installations. In that scenario, I believe it was necessary to do an in-place upgrade of SQL Server first, perhaps to an intermediate release level, and then do an export.

Cheers, and thanks for all the help and advice you provide to so many here!

[BJarkowski · Accepted solution]

Yeah, I overlooked it. Even in the document I linked there is an info you can detach\attach database even from 2005 🙂

We all learn new things here, that's the cool thing about SAP Community!

[former_member459345]

Hi Matt,

Thanks for detailed comment making my queries answered.Now i can go ahead with no more doubts.I will check snotes for compatible kernel.

Thanks Matt and Bartosz.

[BJarkowski]

The system is small, so each option (detach\attach or export\import) will be fairly quick. I'd go with detach\attach as I see less problems with it. You're doing a big change in the system by combining two SQL upgrades, two SAP upgrades and the migration on top, so ensure the system i properly tested.

If your target environment is one of the cloud platforms (like Microsoft Azure) you can scale the hardware up for the upgrade. It should save you some time 🙂

Good luck with the upgrade and migration! Maybe you could write a short blog afterwards with some lessons learned?

[former_member459345]

Hi Bartosz,

I would be starting with sandbox system first and then others.Also to add DB size is around 185 GB. So downtime is no issue now but for production i will have to plan short one.Also to add we will be having new landscape where we have to move our DB with new OS and DB.

Regards

Akif

[BJarkowski]

Sorry for late reply, I didn't get notification about your answer.

I think I'd go with the upgrade of SQL Server during the same time. Export / Import is also a good option, but probably it will take more time (not sure how much downtime you can afford).

[former_member459345]

Hi Bartosz,

Thanks for replying and sharing the important blogs.I check the first blog as per that MSSQL 2008 R2 SP3 and above is required to move to SQL 2017. Whereas we are on Microsoft SQL Server 2008 R2 (SP1) - 10.50.2861.0 (X64). So what all options are there for me to go ahead?

1) Update SP level to 3? ( will it have any major impact on current working DB if we update SP1 to SP3)

2) SAPINST Export/import method?

Please suggest.

Regards

Akif Shaikh

[BJarkowski]

Hello Akif,

in general the plan looks OK. My few concerns:
1) Verify your SQL upgrade path is supported (it may happen that you won't be able to attach the DB):
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-u...

2) Check the SAP database upgrade guide:

https://help.sap.com/viewer/upgrade_sql2017/0d0117252b4b45de97d7daa7c62ad970.html

3) I think there is an additional step in the SWPM to be executed after the database upgrade. Check the following SAP Note:

683447 - SAP Tools for MS SQL Server