Looking for a technical explanation about why CA PPM requires a "physical" database server.
The platform administrators here need to justify this decision in terms of I/O per miliseconds requirements or another technical metric.
The release to be installed is CA PPM 15.3.
CA PPM data structure is defined by following Entity Relationship Diagrams(ERD).
I hope it is useful for your investigation.
PPM requires Relational Database to implement above ERD. (Oracle and SQL Server are supported Database currently)
I cannot imagine that PPM does not use Relational Database.
Because if PPM uses flat files, I believe that critical performance issue will occur and it will be very hard to keep data integrity.
Virtual databases are supported only on specific supported platform where we have tested against these platform. Also we have seen with virtual platform the I/O seems to be inconsistent and performance is bad.
We have documented the same in our release notes too Release Notes (On Premise) - CA PPM - 15.3 - CA Technologies Documentation
Oh my gosh!
I misread "physical" database server.
Thank you Suman.
The origin of the confusión came from the Deployment Architecture document. The Release Note explanation is very useful, but still the Deployment Architecture for 1000 users says that Database Tier and DWH Tier do not allow virtualization (VM), unlikely the other Tiers.
Source: CA PPM r15_x Deployment Architecture for 1K users
I will get that corrected but virtualization are allowed in supported stack
Great. Thank you!