04-02-2014 07:10 PM
Firstly, I know why this is required (for the logical partitioning feature) but we have non BSM databases that are over 600GB in our organistation which use Standard version just fine.
We are under preasure to reduce our Enterprise Licenses doe to the massive cost difference, and it it causing us to seriously look at the long term viability of the HP BSM suite and seek alternatives.
If this feature could be disabled and allow us to install Standard Version of SQL that would help.
04-03-2014 06:09 AM
The reason for BSM requirements on using Microsoft SQL enterprise edition is that this edition has Native partitioning which is required for BSM to handle profile database partitioning.
Oracle does use Native partitioning by default and for MS SQL, the Enterprise edition offers this feature.
06-19-2014 02:49 AM
Hi, Do we have any indication on when the non-enterprise sql version will be supported in BSM, I have a customer who sees this as a serious blocker to using the BSM solution over our competitors?
06-19-2014 07:53 PM
This below document might be useful to you for the example of using non-enterprise edition:
We require Enterprise editions of MSSQL or Oracle because BSM uses DB native partitioning. Microsoft and Oracle include this DB partitioning functionality in their Enterprise editions only.
BSM Partition and Purging Manager uses this functionality. If it is not available, the Partition and Purging Manager does not partition or purge data. Failure to partition or purge may result in major performance issues.
If your customer uses MSSQL/Oracle Standard edition and starts experiencing performance issues HP Support won't help them. Also there will be problems with upgrade to future versions of BSM.
We had received request like a customer where the BAC is implemented with SQL standard edition. After the course of implementation after 1 year, the customer is facing problems with data partitioning and purging of profile database. And now need to migrate to enterprise edition.
I hope that helps.