Select Page

Top 10 Reasons to Migrate Integration Services to Essbase Studio

Christian Screen | | November 20, 2009

Sometimes I feel like I am the only evangelist out there for Essbase Studio and I wonder why that is since Essbase Studio is such a great tool.  This is especially true when you look at its ability to connect to a myriad of data source such as OBIEE, Teradata, MySQL, EPMA Dimension Server, netezza, etc.  Below is the top 10 list of why an organization should migrate their existing Essbase Integration Services models to Essbase Studio.  If your team is not an early adopter, run it in parallel.  If your team is scared of change, have them read “Who Moved My Cheese?“.  Otherwise, let’s make it happen.  Get with the program and enjoy the fruits of this fantastic toolset made for those who believe analytics are always evolving for the better.

Top 10 List

10. It has a familiar feel to EIS but its actually intuitive and user friendly.

9. It integrates with the new features of Essbase Server 11x.  Has EIS been touched since System 9x?

8. Introspection

7. There is a step-by-step tutorial on Essbase Studio Server made just for you (here).

6. Security provisioning and roles can be assigned in Shared Services.  Delineate data modelers from administrators.

5. Essbase Integration Services is about to get sunset and Oracle Support will go bye-bye.

4. It connects to EPMA Dimension Server out-of-the-box. Ever heard of Master Data Management?

3. Essbase Studio Models are deployable with native MaXL Scripting.  Have you tried to automate an EIS deployment?

2. Essbase Studio comes with an Integration Services Catalog Migration Wizard. (hint, hint)

1. Larry Ellison wants you to.  Seriously, Oracle’s BI roadmap is taking Studio to the next frontier, not EIS.  It’s a good train…get on it.

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Oracle EPM Cloud Vs. On-Premises: What’s the Difference?

EPM applications help measure the business performance. This post will help you choose the best EPM solutions for your organization’s needs and objectives.

Bobby Ellis | April 10, 2018

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.

CONTACT US

Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.

EXPLORE JOBS