Prev: runstats on a table partitions
Next: Does DB2 keep checksums for data?
From: JTP PR on 4 May 2010 07:45
Yellowfin is set to redefine what BI users and IT Departments will
expect from Business Intelligence vendors

Leading Business Intelligence software provider, Yellowfin, today
announced it would be launching its milestone release on May 5th,
2010.

Yellowfin 5.0 is set to redefine what BI users and IT Departments will
expect from BI vendors. With faster deployment and faster analytics,
Yellowfin 5.0 is set to establish new BI standards, all the extra
functionality is integrated and three simple steps are all it takes
for users to connect map and visualize their data.

Glen Rabie, CEO of Yellowfin says, “This is a quantum leap in BI
performance. With Yellowfin 5.0 there is no need for the complex and
expensive processes of developing ETL scripts and data warehouses. It
really is a simple process that our beta customers have been delighted
by. Yellowfin enables users to see and know their business in new
ways and interactively explore data without limits”.

“Yellowfin 5.0 was the result of understanding how our customers
wanted to work within the BI environment. The typical scenario was
that deployment got bogged down due to query performance and the need
to build data marts or data warehouses that would address these
performance issues. As a result, business users had to wait for this
tedious non-value added step to be completed before they could even
write a single report, leading to frustration. So Yellowfin developed
an in-memory database to address this need,” says Rabie.

Successful BI projects are measured by two core criteria: the speed of
delivery and the speed of analysis. Traditionally there was a trade-
off between the two. To achieve the analysis speeds required -
complex project steps are required. However,
Yellowfin 5.0 has two major features that deliver a significant speed
enhancement over traditional BI tools. These are:

1. An embedded in-memory database
2. A fully integrated user interface for all development steps

“What this means is that with Yellowfin users can rapidly develop and
publish reports and dashboards since the number and complexity of the
steps required for delivering a reporting project is significantly
reduced (minimizing project costs and risks) without the need to
compromise on the speed and efficiency of the reporting and analysis.
And that thrills the business user,” says Rabie

Fast analysis, better insight and rapid deployment with minimal IT
involvement —these are the leading benefits of in-memory analytics.
With Yellowfin 5.0, In-memory analytics delivers decision insight with
the agility that businesses demand. It’s a win for business users, who
gain self-service analysis capabilities, and for IT departments, which
can spend far less time on query analysis, cube building, aggregate
table design, and other time- consuming performance-tuning tasks.

Ends

Download publications

In-Memory Brochure
http://yellowfin.com.au/Document.i4?DocumentId=104877

In-Memory Whitepaper
http://yellowfin.com.au/Document.i4?DocumentId=104879

eSite Case Study
http://www.yellowfin.com.au/Document.i4?DocumentId=10352

Location Intelligence Whitepaper
http://yellowfin.bi/Document.i4?DocumentId=102780

Demo Video - Dashboard
http://www.youtube.com/watch?v=DSDvmD3xeUg&feature=channel

About Yellowfin

Yellowfin is passionate about making Business Intelligence easy.
Recently recognized among 25 rising companies that CIOs must know
about, Yellowfin is a leading web-based BI solution that can be easily
integrated into any third-party application or delivered as a stand-
alone enterprise platform. Yellowfin is an innovative, fast and
flexible solution for reporting and analytics, providing a full range
of data access, presentation and information delivery capabilities.
www.yellowfin.bi

For further information / interviews please contact:
Catriona McGauchie
Marketing & Communications Manager, Yellowfin
Direct line: +61 3 9090 0454 Mobile: +61 (0)428 368 371 Email:
catriona.mcgauchie(a)yellowfin.bi
 | 
Pages: 1
Prev: runstats on a table partitions
Next: Does DB2 keep checksums for data?