cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading to NW 2004s and SIDs - suggestion

Former Member
0 Kudos

All,

we are in the process of upgrading to NW 2004s and on the R/3 side to ECC 6.0

As a part of it we will have a whole new landscape coming up.

We are looking the SIDs for the systems. We have to 2 options:

1. either stay with the same SIDs or

2. Go for new names.

We already had new server names.

One thing is for sure, at the OS level we wont have any problems in preparing the file systems.

I am looking at the SLD issues that may crop-up with the same SIDs in the second landscape. I am not sure what the issues would be.

Can anyone direct me in the correct path.

reg,

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Naveen,

SAP's official position is that SIDs be unique in a landscape. I would stick with this if possible. Underneath the covers though, the real requirement is that logical system names be unique in an environment. Even here there are work arounds but you must respect this rule if you want to have an orderly landscape.

If you are building a duplicate environment with a migration path then I would definitely choose new SIDs. Think about the confusion of migrating from 1 SID to another if they both had the same name.

So if you are merely upgrading then keep the same SID name. But if you are upgrading with a cutover to a new environment, then you should change the SID name.

-jwise