My company is planning to implement SAP HR in our organization. We already have the other modules running. We plan to offer ESS/MSS to approximately 200 000 users.
Our current configuration is one machine with a Central Instance and 3 machines with Dialogue Instances. The DB is on the Central Instance machine. Enterprise Portal + DB is running on a separate machine.
We are thinking of separating the HR module onto a separate DB so as to not to kill the other modules with load.
Is this a valid concern? Is there any better way to architect the system?
I was thinking along the lines of separating the DB and Central instance onto two different machines. I've tried searching on SAP market place for any advice on SAP infrastructure architecture without any luck.
I'm not quite sure what is meant by "seperating" ...
I would through out the idea of two seperat SAP systems, one for HR and one (or possibly multiple others) for the rest. Each of these systems can then be sized/secured according to the different requirements (HR system many users, possibly high dialog use; the other system maybe a bit more "batch-oriented").
This would also be suggested by SAP's general strategy with almost every module being on it's own release schedule.
With regards to the DB and the Application server (central instance?) being on different machines .. that is indeed very common and one of the easiest tuning measures. You can mix and match pretty "ruthlessly" with the AppServer on Solaris and the DB on HP-UX.