What is our primary use case?
From day one, I was allocated to a project where this technology, Essbase and Hyperion Planning, is used. This is an enterprise performance management tool. You can do analysis and forecasting with it, like current budget and long-range forecasts. You can do all those things with this database and the front end.
What is most valuable?
It is very fast compared to other normal databases, like SQL and MySQL. It doesn't store data in tables in the back end. To load data into Essbase, we need to prepare it in a table format. When we find the data in the table, we need to verify it. This way, you can rate the data. But Essbase stores multidimensional data. We have dimensions, which means the data belongs to some company or some time period.
For example, if you work for three years, your salary should be something. In this way, we prepare top-level members called dimensions. The dimension defines your position, the year, and the section you were working in the company.
We get an intersection of all these dimensions for certain data, and fetching that data is very fast in Essbase compared to normal SQL. If you store this data in a normal SQL table, you need to prepare a row with your company name, employee name, employee ID, joining date, and everything, and then you need to push it into a SQL table.
You can search it using your query, but here, that thing is different. Here, you can collect data using forms, reports, and we use a Microsoft tool, which is an add-in called Smart View. Using that, you would just take that data. Here, you need to just create an integration of all these dimensions, and then only you can find the data.
What needs improvement?
The reporting tool needs improvement.
The built-in reporting tool, Reporting Studio, is not up to par compared to Essbase. We use third-party products for reporting. The reporting tool should be upgraded to improve the fetch of the data because it could take time to fetch huge amounts of data. The fetch time could be smaller in its reporting tool.
It can also upgrade its interface, but it's already upgraded to the cloud. We can use the cloud version now; we have PBCS, the cloud version of the database on-premise version.
For how long have I used the solution?
I have been using it for two years and eight months now.
What do I think about the stability of the solution?
For the on-premise version, we need to build our own setup. We need to buy or rent a PC. In that setup, we actually use on-premise, so our client uses their own PC. In that case, everything is in our hands.
When you up your system, when you down your system, what are the business hours of your system, when you run the job - everything is in the administrator's hands.
In the other case, if you take the cloud version, nothing is in your hands. You can just run the job, but the system up and down is not in your control. It'll break down either way, like with internet issues. But if it is on-premise, in my two years and eight months of experience, I have never seen a system breakdown.
What do I think about the scalability of the solution?
There are many end users in my company using this solution.
How are customer service and support?
We need to contact Oracle many times. For example, we are facing one issue in reporting that I just updated you on. We have a volume limit of 2.5 million cells that we need to refresh at a time in a report.
In one dimension, we have many members, maybe 1000 or 10,000 members, or more than that. If you were to drill down on the member, choosing the top-level member and drilling to the bottom level, and each intersection has data, the report will increase dramatically. In just a fraction of a second, it reaches 2.5 million and gives you an error. We didn't know this earlier, so we gave a snapshot of that error to Oracle. They told us that this is a product requirement and that they cannot give us more than 2.5 million cells of data. There are many things like this.
We have patching quarterly, so they upgrade the security of this product, and that way, we might face some issues. So, we need to reach out to them to resolve those issues and get to the root of them. Even in Smart View, sometimes we get issues because Smart View is compatible with the EPM Add-in.
We use the Oracle product, and there, we can fix that data. Sometimes, we get a replacement issue in Smart View because of a version issue. At that time, we need to upgrade Smart View. This way, we need to reach out to Oracle several time. They are very supportive.
How would you rate customer service and support?
How was the initial setup?
The initial setup is time-consuming. It will take around two to three months. First, we need to deploy it and gather the business requirements, like what they need and how many users there are.
Essbase is preferred for 300 to 1000 users on the front end. If we have more than that, then Essbase is not preferable because it will take more time to fetch data.
In that case, we would prefer the cloud version for larger volumes of data. We have a PBCS for that. From my perspective, it is for more than a hundred thousand users.
Other than that, we need to check all the business requirements and all the avenues where we can apply it. So we need to think first, and then we can decide whether to use it or not.
What's my experience with pricing, setup cost, and licensing?
What other advice do I have?
Before using it, I recommend you check with an expert. We have some EPM administrators who can analyze your requirements and tell you which product is suitable for you. Essbase is the database used in the backend, and in the front end, we have several options like Workspace, Planning, and Enterprise Performance Management reporting tools.
The experts can comment on which tools are suitable for you. But if you are looking for some performance management tools, then go for Essbase. There are other competitive tools, like SAP, which can also work.
Moreover, the interface is very easy. So, it is easy for a beginner to learn to use Oracle Essabase. Within one or one and a half months, any user familiar with company figures can learn it and implement their forms and everything.
Overall, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises