List of reports used in the SAM Optimization Hub

FlexNet Manager Suite 2022 R2 (On-Premises)

The Microsoft and Linux reports explained below, report on the current license consumption and optimal license:

Microsoft Windows Server Optimization Report

The Microsoft Windows Server Optimization report calculates VM density across both hosts and clusters, and helps you implement best practices for Windows Server licensing. The report evaluates, host by host, the movements of VMs based on history and the 90 day peak of non-exempted Windows Server VMs. Note: Windows Server Standard adheres to the license re-assignment rule and license entitlements cannot be reassigned on a short-term basis (within 90 days of the last assignment). See the Microsoft Windows Server Optimization Report in the online help for more information.

Microsoft SQL Server Optimization Report

The SQL Server Optimization report evaluates, host per host, the optimal option for covering the full host with SQL Server Enterprise or licensing VMs individually with SQL Server Standard and Enterprise. See the Microsoft SQL Server Optimization Report in the online help for more information.

Red Hat Enterprise Linux Optimization Report

The Red Hat Enterprise Linux License Optimization report calculates the optimal subscription for Red Hat Enterprise Linux (RHEL) in virtual environments, on orphaned virtual machines (where the virtual host is unknown), and on free-standing servers. As the subscriptions are renewed annually, you may get a rapid return on improving the mix of your subscriptions for the next renewal. See the Red Hat Enterprise Linux Optimization Report in the online help for more information.

The Oracle and Named User reports explained below, report on the additional savings you can make by optimizing your infrastructure to minimize costs under Oracle rules for soft partitioning, and canceling or downgrading license subscriptions:

Oracle License Optimization on Clusters

The Oracle License Optimization on Clusters report applies to consumption of exclusively Oracle Processor licenses on:
  • Computer clusters where Oracle Processor licenses may be consumed (and therefore currently excluding Kubernetes clusters); with special focus on VMware clusters, and Oracle clusters managed without core affinity, because the Oracle licensing rules for these "soft partitioning" environments allow for substantial savings through cluster optimization
  • Stand-alone ESX hosts (not in a cluster)
  • Other stand-alone virtual hosts.

See the Oracle Processor Licenses: Cluster Optimization Report in the online help for more information.

Oracle Licenses Consumption Details and Optimizations Report

The Oracle License Consumption Details and Optimizations report covers all license types linked to Oracle products, providing sufficient details to explain where and why consumption is occurring. It includes details for chargeback where relevant license costs can be assigned back to enterprise groups that you have linked to the appropriate devices. The report also suggests details for optimizing your infrastructure to minimize costs under Oracle rules for soft partitioning. See the Oracle Licenses: Consumption Details and Optimizations Report in the online help for more information.

Optimum Virtualized Architecture for Oracle Options Report

The Optimum Virtualized Architecture for Oracle Options report tracks licensing of Oracle Database Enterprise and Oracle options in VMware environments, assuming that the soft partitioning rule is applied at the single cluster level. Under this rule, an installation of a licensed option on any VM(s) on any host(s) in the cluster triggers licensing of all cores on all hosts in the cluster. See the Oracle Options: Optimum Virtual Architecture in the online help for more information.

Named User Licenses Consumption and Optimization Report

The Named User Licenses Consumption and Optimization report, allows Software Asset Managers to actively track subscriptions for installed applications, and returns license consumption for all named user licenses. The report provides all cost information (current cost, optimal cost, potential saving for users, total potential saving and so on). Software Asset Managers can subsequently use this data to action subscription(s) downgrades. See the Named User Licenses Consumption and Optimization Report in the online help for more information.

The following Oracle reports explained below, report on the current license consumption for all Oracle Processor licenses and the financial impact of applying them:

Oracle Consumption Summary by Partitioning Rule Report

The Oracle Consumption Summary by Partitioning Rule report lists all Oracle Processor licenses, calculating for each one four distinct current consumption figures and estimated licensing costs, based on four possible partitioning rules that you might agree in negotiation with Oracle. It is focused on VMware vCenter clusters/networking, where Oracle applies its various 'soft partitioning' rules. The comparative figures show the global impact of the various rules that take account of how potential migration of VMs across hosts may be limited (listed here from the smallest scope to the largest):
  • Partition at the ESX host — This concept, where administrators use host affinity and similar rules to restrict a VM to a single server, is not one of Oracle's "soft partitioning" rules, but remains a possibility for negotiation
  • Partition at the cluster — Oracle's original soft partitioning rule that requires all hosts in the cluster to be licensed when a licensable product was installed on any VM(s) within the cluster
    Tip: This position is a common outcome of negotiations, and is the basis for Oracle Processor calculations within management views in FlexNet Manager Suite.
  • Partition at the vCenter — When vCenter 5.1 supported vMotion across multiple clusters that were managed by a single vCenter, the Oracle rule required licensing of all hosts managed by the vCenter
  • Partition around all vCenters — When vCenter 6.0 supported vMotion between vCenters, the Oracle rule required licensing of all hosts in all vCenters within your data center.
  • Partition at the cluster with affinity — This concept, where administrators use host affinity to restrict consumption to hosts within clusters that can be accessed by installed VMs, is not one of Oracle's "soft partitioning" rules, but remains a possibility for negotiation.

See the Oracle Consumption Summary by Partitioning Rule in the online help for more information.

Oracle Partitioning Rule Impacts Report

The Oracle Partitioning Rule Impacts report gives full details of points consumed from Oracle Processor licenses, with special focus on a "what if" comparison of the effects of different partitioning rules (listed here from the smallest scope to the largest):
  • Partition at the ESX host — This concept, where administrators use host affinity and similar rules to restrict a VM to a single server, is not one of Oracle's "soft partitioning" rules, but remains a possibility for negotiation
  • Partition at the cluster — Oracle's original soft partitioning rule that required all hosts in the cluster to be licensed when a licensable product was installed on any VM(s) within the cluster
    Tip: This position is a common outcome of negotiations, and is the basis for Oracle Processor calculations within Management views in FlexNet Manager Suite.
  • Partition at the vCenter — When vCenter 5.1 supported vMotion across multiple clusters that were managed by a single vCenter, the Oracle soft partitioning rule required licensing of all hosts managed by the vCenter
  • Partition around all vCenters — When vCenter 6.0 supported vMotion between vCenters, the Oracle soft partitioning rule required licensing of all hosts in all vCenters within your data center.
  • Partition at the cluster with affinity — This concept, where administrators use host affinity to restrict consumption to hosts within clusters that can be accessed by installed VMs, is not one of Oracle's "soft partitioning" rules, but remains a possibility for negotiation.

See the Oracle Partitioning Rule Impacts Report in the online help for more information.

FlexNet Manager Suite (On-Premises)

2022 R2