Oracle Bi Publisher Licensing Costs
System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition Version 10. Rev. O 3 Contents. In my previous Industry Insight, I outlined certain important points to consider when defining a cloud business intelligence BI strategy. In summary, this came down. IKLFlRlY/R1R_PhOIOJI/AAAAAAAAC6s/wFyusSJ9Bwo/s1600-R/bip_report_example.jpg' alt='Oracle Bi Publisher Licensing Costs' title='Oracle Bi Publisher Licensing Costs' />The Power BI Premium Pricing Model The Good, The Bad and the Ugly. On May 3, Microsoft announced sweeping changes to the pricing of Power BI by introducing a new Power BI Premium SKU. The announcement itself can be found here, and there a number of other related resources worth that I am listing here for convenience Distribute to large audiences with Power BI apps. Changes to Power BI embedded. Power BI Premium White Paper. Power BI Pricing. Premium pricing calculator. Introducing Power BI Report Server. Power BI Premium is intended to address deficiencies in the current pricing model primarily with respect to sharing content. In my opinion, the new model succeeds in this goal for the most part, but it leaves a significant number of customers behind, and it also leaves many unanswered questions. These problems need to be addressed for Power BI to succeed in its goal of bringing BI to the masses. Overall, I like what Microsoft is trying to do with this new pricing model, and with a few tweaks, I think that it can resonate. Artificial Satellites Ppt. First, we need to understand the new model, and to do that, we need to understand the former model and the need for Premium. Given that the former model consisting of free and Pro licenses has not been replaced although it is changing significantly, we will refer to it as the original model, and when Premium is added to it, we will refer to that as the Premium model. The original model is still completely relevant moving forward. The original model and the need for change. The original model is relatively simple, and relatively unique to the industry. Power BI users are licensed for either free or Pro features. If a report contains any Pro capabilities, any consuming user requires a Pro license. A free user can create a report that uses Pro features, but that same user will not be able to consume that report in the free service. This is a very important distinction to understand. Oracle Bi Publisher Licensing Costs' title='Oracle Bi Publisher Licensing Costs' />The author of a report using Power BI Desktop could be a free user, use a Pro feature, and after deploying the report to the service, be unable to use it in the service. Difference between free and Pro from a feature standpoint is no longer as of this writing available on the Power BI pricing page, however, prior to June 1, 2. Therefore, if a report is configured to be refreshed more than once per day, or even if the time of day is specified, or if the report uses on premises data, then all users accessing that report require a Pro license. Given that Power BI is all about bringing Business Intelligence to the masses, when each one of those masses needs to pay 1. Report sharing is also relatively limited. Reports can be shared anonymously, which is insecure. Dashboards and their constituent reports can be shared either internally or externally, but they are read only. Finally, both dashboards and reports can be shared through Group workspaces now app workspaces. Currently, Group workspaces do not allow for external sharing, but they are the preferred means of sharing. However, they too require Pro licenses, which constrains adoption. For the free user, anonymous and dashboard sharing are the only real options. Oracle Bi Publisher Licensing Costs' title='Oracle Bi Publisher Licensing Costs' />New model. The introduction of Power BI Premium aims to solve some of the sharing issues listed above, and therefore to help drive adoption. Premium capacity is an add on to a Power BI tenant organization, and is different that free or Pro licenses which are assigned to users. An organization can purchase Premium capacity, and then a Pro user this is restricted to Pro can move or publish content to the Premium capacity. Once the content is in Premium storage, all users can utilize all the features in the dashboards and reports. Premium effectively removes all feature barriers from the reports. Premium storage also brings many performance enhancements, such as the ability to refresh data up to 4. Without Premium, there are also several changes to the original licensing model. According to the May 3 Announcement FAQ on the Power BI community site Beginning June 1, the free service will have capabilities equivalent to Power BI Pro. This includes the same 1 GB workbook size limit, up to 8 daily scheduled refreshes for datasets, and maximum 1 million rowshour streaming data rate. Were also providing access to all data sources, including those available through the on premises data gateway. Peer to peer dashboard sharing, group workspaces now called app workspaces, export to Power. Point, export to CSVExcel, and analyze in Excel with Power BI apps are capabilities limited to Power BI Pro. Therefore, after June 1, 2. Pro features are effectively an addition to the free features, and the feature differences should be as below From the May 3, 2. Going forward, we will improve the free service to have the same functionality as Power BI Pro, but will limit sharing and collaboration features to only Power BI Pro users. The only features that Pro will have that free will not are those that are related to sharing. The above feature list reflects that. Power BI Embedded. Power BI Embedded is the way that developers can embed Power BI in their applications. Using Power BI Embedded, until now, developers build reports, deploy them to their Azure instance, and call them from their applications. End users do not need any sort of Power BI licenses, and the developers are charged per report render session. This charging model has been one of the criticisms of Power BI embedded in that it is very difficult to predict costs. ISVs are at the mercy of the end users viewing reports, and any measure that is put into place to curb these render sessions is by definition a disincentive to adoption. The fact that Embedded runs in a different namespace than the core Power BI service is another, leading to differences between the capabilities of Power BI Embedded and the core Power BI service. For example, the current iteration of Power BI Embedded cannot use the On Premises Data Gateway, which can be quite restrictive. Power BI Embedded is changing to use the new Premium capacity model. ISVs will purchase Premium capacity, and serve reports to their end users from that space. There will only be a single namespace for all Power BI content. Whats Good. Power BI Premium solves to sharing problem for organizations that want to distribute their BI assets across the organization. If organizations would be accessing on premises data, a key feature of Power BI for enterprises, the Pro license requirement has discouraged adoption. With Premium capacity, an report publisher can share content with as many users as necessary without worrying about licensing the target users. Even better, those target users can be external, further extending the reach of that content. For large enterprises, this has the potential to turn Power BI from a niche solution to something that is used by everyone. The changes to the original model also makes things clearer for report designers and publishers. These publishers can work with the full range of Power BI features while the report is being built, and while they are themselves using it. When it comes time to share the report to a wider audience, they can publish it to Premium capacity where anyone can access it. If the organization has not purchased Premium, then the original model applies, and all recipients will still require a Pro license. On the Power BI Embedded side, switching to Premium capacity completely eliminates the unpredictability of the current model. Save money by understanding the Oracle licensing model. Oracle and licenses. The general feeling most of the time is that you pay too much for the use of the Oracle products, and its not always sure if you are compliant, because of the complexity of the rules. This hopefully clarifying blog is part of a small series and is an updated blogpost of one I wrote a few years ago. Since then the Oracle world has changed a bit, felt the need to update, and I will try to give some clarity about the licensing model which will hopefully help you to save money by utilizing your Oracle Environment. Ill start with the basics part I and then I will treat topics like virtualizing, engineered systems, SE2, Unlimited License Agreements, Cloud and so on. The information in this post is not intended to be used as legal statements or sources for negotiations with Oracle. I will be referring to some other documents and blogposts which can and should be used. The information is not exhaustive but will hopefully give the reader a guide how to cope with the model of Oracle at this moment 2. Subjects in this part 1 Scope Full Use Hosting. Development and testing environment. Prices and contract. Databases species. Types of licenses. Processor NUP Employee based. Support Scope Full Use Hosting. The following models are to be recognized Full Use end user license, suitable for running tailor made applications. The legal entity of the firm is owner of the full use license. Application Specific Full Use ASFU Example SAP. You can only use the Oracle software for that particular purpose. Not even allowed to use Enterprise Manager Packs. Embedded Software License ESL. Only to be used for specific to be used applications, and the database schema is not accessible to the end user but only to the application runtime. Hosting licenses more detail in a coming post. Generic Hosting. Third party or multi application hosting. Multiple customers. Propriarty Application Hosting PAH. Single application, multiple customers. Specified End Users. Hosting Environment dedicated to a single end user. For the Hosting licenses approval is needed by Oracle Scope in this post Full Use model, in a post later on I will talk about the different Hosting licenses which is different from Cloud credits Development and test licenses. You may use the Oracle software free for generally 3. This period may sometimes be extended to generally 9. Oracle, and is used for proof of concepts and that kind of stuff. Development and test environments for an application must be licensed, with at least one rare exception. The exception and the rules around development and testing I described in this blog. Prices and contracts, what are you paying for. First years costs can be calculated as purchase purchase discount support costs 2. Support costs are calculated of the purchase minus the discount. You get support as long as you pay the yearly support costs. Oracle has the right to increase the support amount with a few percent a year. So when you are a local customer for a decade or so, the support costs may be substantial higher, and may not be in proportion anymore with the discount you got at the beginning. Licenses without support of perpetual licenses is possible first year support is mandatory, but then you have got no access to Metalink support, patches and upgrades. Be aware, theres a huge difference between stopping the support, and eliminate the license. When just stopping the support, you will still be the owner in the case of perpetual license When you made a mistake, and want to get into support again after a period of time, youll have to pay a so called re instatement fee. This is all explained in the Oracle Software Support policies. Purchase is also possible for a period of 1, 2, 3, 4 or 5 years Term Licenses, purchase support is mandatory which isbased on the price of the perpetual licenses More on support later on. On www. oracle. com are the so called list prices in dollars. These are the prices with no purchase discount at all. This discount depends greatly on the volume you buy, and there are some fixed staggered discounts you can agree on with Oracle. By the way the discount is based on the sum of the purchases. When you decide over time to end a part of the purchase, this will lead to a recalculation, and could be influencing your yearly costs, because of stumbling into a lower staggered discount. Prices will be adjusted on a regular basis. Changes will occur within June, see also this blog. For Europe, changes will also depend on the rate of the dollar. Oracle has also a so called Matching Service Level Policy sometimes it does not matter what you are using, but it does matter what you bought in the past. Example you purchased database licenses for 3 servers together with 3 diagnostic and tuning pack licenses. Termination or stopping the support of the diagnostic and tuning pack licenses is not allowed. Those management packs are linked one on one to the databases, consequence is that you have to terminate or stop the support of the databases as well. Oracle does not pro actively monitor this at this time. So it helps sometimes to act low profile. Species of databases. Enterprise Edition. Most expensive, complete database. Standard Edition 2. Less functionalities, e. But includes RAC. A lot of questions are answered by this blog. Personal Edition single user databaseOracle Express edition. Differences in functionality you can see here. Enterprise Edition is required with the following configurations When the server has got more than 2 sockets or. You are using Oracle Enterprise Manager Packs, like Tuning pack or. You are using Database Options e. PartitioningYou have to pay for the Database Options, besides the default Enterprise Edition database licenses, e. Real Application Clusters. Partitioning. Advanced Security. Database Vault. Advanced Compression. Active Data Guard. Real Application Testing. Label Security. Total Recall. Spatial. In Memory Database Cache. Data Mining. OLAPMedia Pack. No licenses necessary Apex Oracle Application Express, included in Standard nd Enterprise Edition. Oracle Express edition. Types of licenses. With Full Use licenses you can choose from 3 types of licenses Processor based ProcNamed User Plus NUPEmployee EMP license. Processor based ProcYou pay per processor, but a processor according to the definition of Oracle. As the processors become increasingly powerful and have multiple cores, Oracle has created a core element. For Intel and AMD dual core CPU typically a factor of 0. Oracle will count this processor as 1 Oracle processor 2 cores x 0. This is no different from the number of CPUs in this case. But customers also uses servers with 2 quad core cpus. Suppose this has also a factor of 0. Oracle will count this as four processors 2 CPUs x 4 cores 8 cores. Oracle processors. The core factor table Oracle uses is to be found here. Thus, if a database on a server is installed on two quad core processors running as previous example, 4 processor licenses must be paid for. On that server you are free to install multiple databases, regardless of the version The processor based license is paid per server and not per database. Another example Oracle is not supporting virtual servers, except their own Oracle.