Sisense

Sisense Review
The rapid development of the product is good, but it has limited inner join functionality of the cubes. ‚Äč


Valuable Features:

The ability to combine multiple data sources in a cube environment is essential. The speed has been very good as well.

Improvements to My Organization:

We are now able to increase our visibility into our business beyond the canned reports available in our ERP (NetSuite) and provide actionable, timely insight to our leadership.

Room for Improvement:

The document is definitely a sore spot as well as the limited inner join functionality of the cubes.

Use of Solution:

We have been using this product for approximately two months now and are close to our final implementation.

Deployment Issues:

Only trying to understand some of the functionality and our internal business rules.

Stability Issues:

No issues with stability have been encountered yet.

Scalability Issues:

We are very early in our project but do not see any major limits yet.

Customer Service:

Customer service has been excellent.

Technical Support:

Technical support is very good. The rapid development of the product has some features that are new even to the tech support staff.

Previous Solutions:

No previous solution was in place.

Initial Setup:

The connections to the SQL data were straightforward.

Implementation Team:

We utilized the Sisense staff for implementation along with our internal BI group. They are very helpful, knowledgeable and responsive.

ROI:

Unknown at this time.

Other Solutions Considered:

  • Tableau
  • PowerPivot/PowerBI
  • Birst
  • Sisense

Other Advice:

Understand your business hierarchies intimately. Create flattened data files for roll-ups.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
4 visitors found this review helpful
Add aazariaAnonymous avatar x30Anonymous avatar x30Anonymous avatar x30

3 Comments

Anonymous avatar x30

This review is insightful.

Like (0)30 June 15
Anonymous avatar x30

What is the data scale you are working with?

Like (0)30 June 15
Anonymous avatar x30

Hi there,

As Director of Product Management of Sisense I would love to shed some light on the inner join issue you mentioned. In general I will say that there are two ways to address it:

1. You can still always create an inner join with the custom SQL feature, if it's absolutely necessary.

2. It's true that the ElastiCube Manager (visual data modeling environment) doesn't show inner joins as a configuration option. However, it's quite possible that if you find yourself looking to do inner joins, you're not utilizing the full power of the product:

Most solutions rely heavily on joins in the data prep phase to create a single view.
What's unique about Sisense is that you don't *need* to flatten the data during the data preparation stage. Sisense only performs joins when it needs to answer a query, such as when a new visualization is created. The joins are performed ad-hoc and the system automatically detects which type of join is most effective for that particular data scenario. So 99% of the time, you shouldn't be dealing with these join headaches in the first place.

Like (2)08 July 15
Anonymous avatar x30
Guest

Have A Question About Sisense?

Our experts can help. 213,655 professionals have used our research on 5,586 solutions.
Why do you like it?

Sign Up with Email