SIZING strategy for O/S and DB migration
We're about to begin a O/S and DB migration project for our R/3 (ECC 6.0 Unicode) system which has been running for 10+ years on the current platform to MS Windows and MS SQL Server 2005 DB platform .
A couple of months ago, we went live with new deployments of EP 7.0; PI 7.0; BI 7.0 and put those on MS Windows with MS SQL Server 2005 DB.
For sizing the new solution for our currently running ECC 6.0 application, would you take the "SAPS" rating of your "from" O/S DB platform and then purchase the same "SAPS" rating hardware for the new solution?
Seems that this approach would make sense vs. attempting to enter quicksizer data? Would be a good starting point.
Thank you in advance