Idea ID: 2701725

BSM /APM Database with SQL Standard Versions.

Status : Declined
over 1 year ago

Brief Description:

We are planning to implement APM 9.50 in our environment. we have verified the support matrix and observed that APM supports only SQL Enterprise edition . Here we want detailed information or tested  results on why we need to go for SQL enterprise edition only . in microfocus support blogs we came to know that database purging and   partitioning is not supported in SQL standard version .We got to know that From SQL 2016 standard SP1  edition onwards supports for database purging and partitioning .  we need test results by using SQL 2016 standard SP1  database to know APM supports or not with database purging and partitioning

Benefits /Values :

If the APM 9.50 supports SQL Standard edition  , which will reduce the cost.


Design details :

We come across the current database support matrix doesn't  fulfill our requirement ,In the current competitive market, Microfocus has to improve the  R&D testing on these type  of requirements for more involvement. we are expecting to have more advanced and cost affective design for APM .


  • The reason for requesting support for STD MS SQL Support is about TCO running APM solution. As I understand the cost of SQL Enterprise versus SQL STD is a factor 3 times.

    For customer to operate the APM solution they would need several SQL Enterprise instances located in different parts of the world like EMEA, APJ etc.

    So, supporting STD SQL would have a big positive operating reduction on cost.

  • I am currently in discussions with Support about this requirement. MF claims that there are performance differences between Standard and Enterprise that could impact supportability.

    They are the same product - functionality is enabled via the license - and yes there are some minor performance enhancements available in Enterprise compared to Standard edition.

    It would seem to me that all that MF needs to do is to run their usual plethora of qualification test cases on APM with an SQL Standard edition to verify the functionality before releasing to production/support. I would assume the test cases include performance testing.