NonStop SQL Strategy and Roadmap - IDG Enterprise

39 Pages·2012·0.97 MB·English

Instant-On Enterprise

Winning with NonStop SQL
©©22001111H Heewwlelettt-tP-Paacckkaardrd D Deevveeloloppmmeennt tC Coommppaannyy, ,L L.P.P. .
TThhee iinnffoorrmmaattiioonn ccoonnttaaiinneedd hheerreeiinn iiss ssuubbjjeecctt ttoo cchhaannggee wwiitthhoouutt nnoottiiccee
LIBERATE
Your infrastructure with

HP NonStop Database Solution
for OLTP and Data Warehouse
database applications

©©22001111 HHeewwlleetttt--PPaacckkaarrdd DDeevveellooppmmeenntt CCoommppaannyy,, LL..PP..
TThhee iinnffoorrmmaattiioonn ccoonnttaaiinneedd hheerreeiinn iiss ssuubbjjeecctt ttoo cchhaannggee wwiitthhoouutt nnoottiiccee
Today’s agenda
NonStop SQL
• Value proposition
• Proof points
• Did you know?
• Looking ahead
• Call to action

3
Value proposition
Overview
Databases are critical to your business
Enterprise
Databases support
database hosts
critical business
business critical
functions
information
DBAs are
Databases control
responsible for the
all touch points of
wellness of
an enterprise
business

5
The Database decision
Customers are looking for a database that
Grows with your
Meets global
business without
business needs
sacrificing
24x7
performance
Provides Avoids complexity
information at of too many
the right time moving parts
Does not cripple IT budgets
6
The HP NonStop database solution
All modern, All standard, All nonstop
All modern All standard
Integrated hardware All NonStop ANSI 2003
and software
24/7 application JDBC 3.0
Out-of-the-box cluster availability
ODBC 3.5
aware Linear scalability
Mixed workload handling
Virtualized data
Online manageability
Parallel query execution

Trusted HP expertise with comprehensive mission-critical services and world-class
partnering
7
Why migrate to NonStop SQL?
Common customer pain points emerging
• Scale
– Reached maximum throughput on a single node
– Adding clustered nodes does not provide proportional throughput gains
– Adding clustered nodes increases user response time
• Availability
– For some applications, the business cost of downtime, even a few minutes, is huge
– Clustered database recovery following failures is complex, error-prone and time-consuming
– Complexity of configurations and database layout makes online operations difficult
• Cost
–Clustered database licensing and support fees are high
–Configuration complexity of clustered databases translates into significant operational costs
Proof Points