Real-time Data Distribution: When Tomorrow is Too Late
 

Like this? Share it with your network

Share

Real-time Data Distribution: When Tomorrow is Too Late

on

  • 690 views

The Briefing Room with Robin Bloor and Sybase, and SAP company ...

The Briefing Room with Robin Bloor and Sybase, and SAP company
Slides from the Live Webcast on Sept. 4, 2012

The rising tide of analytical demands puts pressure on data managers to deliver information within ever-tightening windows. For many use cases, waiting a day for a data warehouse to refresh is not fast enough. This is the realm of real-time data distribution: replicating key sets of data to feed analysts and business users in far-flung corners of the enterprise.

Check out this episode of The Briefing Room to hear veteran Analyst Robin Bloor explain how data flows are changing rapidly these days, due to a number of technological advances, but also because of a growing awareness of efficient information architectures. Bloor will be briefed by Bill Zhang of SAP Sybase, who will tout his company's time-tested Replication Server, which now features multi-path replication. This new feature enables sophisticated management of data flows, including prioritization for certain paths and uses.

For more information visit: http://www.insideanalysis.com

Statistics

Views

Total Views
690
Views on SlideShare
690
Embed Views
0

Actions

Likes
0
Downloads
9
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Real-time Data Distribution: When Tomorrow is Too Late Presentation Transcript

  • 1. Eric.kavanagh@bloorgroup.comTwitter Tag: #briefr 9/4/12
  • 2. !   Reveal the essential characteristics of enterprise software, good and bad !   Provide a forum for detailed analysis of today s innovative technologies !   Give vendors a chance to explain their product to savvy analysts !   Allow audience members to pose serious questions... and get answers!Twitter Tag: #briefr
  • 3. !  September: Integration !  October: Database !  November: Cloud !  December: Innovators !  January: ArchitectureTwitter Tag: #briefr
  • 4. !  Data integration involves combining heterogeneous data sources and providing one unified view of said data. !  It is a necessity for all IT sites, increasingly becoming a problem area in the era of remorseless data growth (average about 55% per year) which is swiftly becoming an era of Big Data. !  Data integration involves many competing technologies, each with its nuances, upside and downside. But which is best for you? !  The costs of data integration are high and rising. This calls for strategy and effective technology.Twitter Tag: #briefr
  • 5. Robin Bloor is Chief Analyst at The Bloor Group. Robin.Bloor@Bloorgroup.comTwitter Tag: #briefr
  • 6. !   Sybase, an SAP company, provides enterprise and mobile infrastructure, development and integration solutions. !   It offers a suite of database management technologies designed to increase performance and time to insight. !   Its Replication Server product allows for real-time reporting with minimal performance impacts across heterogeneous database environments.Twitter Tag: #briefr
  • 7. Bill Zhang is a veteran at Sybase, an SAP Company. As Director of product management, Mr. Zhang is responsible for the complete product strategy for Replication Server. He interacts with strategic customers and partners as well as industry analysts to formulate product strategies. He defines product roadmaps for engineering groups. Prior to his current role, Mr. Zhang held several customer-facing positions at Sybase in Sales and Professional Services. Mr. Zhang has an MBA degree from the Leonard N. Stern School of Business, New York University, a master s degree in electrical engineering from Columbia University, and a bachelor s degree in electrical engineering from the University of Rhode Island. Tom Traubitz is a Director of Analytics Product Marketing with SAP/Sybase s Data Management and Tools Group, specializing in enterprise-class transaction processing and data analytics. He has spent the past 25 years designing, engineering, testing, and marketing large scale, networked information management systems for a wealth of clients throughout the United States and the world.Twitter Tag: #briefr
  • 8. SAP Sybase Replication ServerAugust 2012
  • 9. Replication Server: WHAT DOES IT DO? Disaster Recovery High Data Replication Availability Assurance Server Real-Time Business Data Reporting Integration Load Balancing This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 10 infringement
  • 10. Sybase Replication ServerUse Case Scenarios Data distribution and migration §  Distribute: move centralized data to operational applications §  Share: share data between operational applications §  Synchronize: maintain consistency in overlapping data values §  Migrate: move from older version of database platform to newer one Real-time Decision Support §  Create ODS (copy of OLTP production systems for daily reporting) §  Real-time loading of data warehouses (Sybase IQ, ASE, Oracle, Microsoft, IBM), aka, Change Data Capture High availability/disaster recovery §  Enable business continuity in event of site-wide disaster §  Maintain application availability during planned/unplanned downtime This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 11 infringement
  • 11. Sybase ReplicationHigh Availability • Minimize/eliminate user impact Philadelphia Operations • Protect against unplanned outages OFF Replication LINE Ÿ Software, hardware, application ASE Server failure Ÿ Unforeseen circumstances like data corruption • Protect against planned outages PRIMARY DATACENTER Ÿ Software, hardware, application upgrades Denver Operations Ÿ Enable ops to perform Replication maintenance activities ASE Server • Recover from natural disaster Ÿ Without geographic restrictions SECONDARY DATACENTER Warm Standby This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 12 infringement
  • 12. Sybase ReplicationReplication and Live Decision Support Ÿ Maintain a complete copy of the primary OLTP database Ÿ Run operational reports and queries against this copy (ODS) Ÿ Preserve transactional system processing performance Ÿ Enable more robust and responsive reporting environment Ÿ Sources can be ASE, Oracle, Microsoft, and IBM Ÿ Targets can be ASE, Oracle, Microsoft, IBM, and Sybase IQ Ÿ HA/DR warm standby can also be ODS OLTP DSS DB Rep Server Rep Server DB This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 13 infringement
  • 13. Sybase ReplicationData DistributionOne example, many permutations New York (sales department)San Francisco (order processing) WAN Rep Option Sales Support for Microsoft Application Order Entry ASE Rep Server Application LAN San Francisco (finance department)§  Continuous replication of changed data§  One source to many targets Rep Option Financial WAN for Oracle Reporting Application§  Guaranteed delivery. Publish and subscribe architecture§  Propagate order info to related Dallas (manufacturing department) downstream applications§  Can also have bi-directional scenarios Rep Option Manufacturing§  Can also have many – one and for IBM Planning Application many – many topologies This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 14 infringement
  • 14. Replication Server – In a Nutshell Replication Server (RS) Primary DB Secondary DBReplication Server•  Replicates “transactions” from primary to secondary site(s), non-intrusively•  Near real time, bi-directional data movement•  Guaranteed delivery with store and forward mechanism•  Flexible filtering / transformation of data•  DML, Schema (DDL) changes, Stored Procedures replication•  Database Integrity is guaranteed and protects against corruptions This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 15 infringement
  • 15. Flexible Replication landscape Data movement across heterogeneous databasesØ  Multiple Database vendorsØ  Many to one, one to many, any to any Message Bus –Ø  Geographically dispersed MQ, Tibco, JMS, RepConnector Sybase IQ Staging Sybase ASE Database Replication Server Sybase ASE Oracle, MS SQL, IBM UDB Oracle   MS SQL Replication Agent Express Connect & IBM UDB ECDA Sybase IQ This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is ©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 16 infringement
  • 16. New Feature Highlight: Multi-Path Replication Single  DSI  connec$on   Single  RepAgent  per  PDB   to  RDB   Single  Route  between   Single-Path PRS  &  RRS   Mul$ple  RepAgent   Mul$ple  RS  from   Dedicated  Route   Same  Source   Mul$ple  DSI   Senders     Paths  Multi-Path This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is ©  2012 SAP AG. All rights reserved. provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- 17 infringement
  • 17. Twitter Tag: #briefr
  • 18. The Orchestration of Replication
  • 19. We need to duplicate data. We have no choice. So the question is not whether we do it, but how best to do it.Twitter Tag: #briefr
  • 20. !   Database Logging !   We duplicate for the sake of recovery !   Database Back-ups/Snapshots !   We duplicate for the sake of a recovery start-point !   Data Warehouse !   We duplicate for the sake of data consolidation !   Data Staging !   We duplicate for the sake of data flow !   Database Subsetting (Data Marts) !   We duplicate for the sake of performance !   Operational Data Store !   We duplicate for the sake of timelinessTwitter Tag: #briefr
  • 21. Twitter Tag: #briefr
  • 22. !   Of course, it isn t just performance, but performance is the major driver for the way we build the data layer. !   Because we cannot have a single coherent distributed data store, we have no option but to think in terms of data flows. !   This means database plus middleware. !   Middleware is a lousy word with many meanings: ETL, ESB, data governance, data virtualization, etc. !   The truth is that data flow service levels and database service levels are strongly interrelated. One hand washes the other (and both hands wash the face). !   Database replication is a critical capability in this primarily because of its performance characteristics.Twitter Tag: #briefr
  • 23. !   Disaster Recovery (An extreme service level and often an expensive one) !   High Availability (A service level thing) !   Real-time Business Reporting (A data flow and service level thing) !   Load Balancing (A service level thing) !   Data Integration (A data flow and service level thing) !   Data Assurance (A security thing)Twitter Tag: #briefr
  • 24. !   What are the costs likely to be in situations where replication replaces other data flow strategies? Does it reduce storage costs or increase them? !   Where is there a performance advantage when replication replaces other data flow strategies? !   Is the replication server used for software modernization rather than just to build new data flows? Can you provide use cases? !   How frequently is it used in that way (roughly)? !   Can you please provide a description of the most extensive use of this capability by one of your customers?Twitter Tag: #briefr
  • 25. !   How difficult is it to use? In other words, what are the labor overheads compared to alternative approaches? !   What situations (in respect of data flow) do you think it does not apply to (i.e., where not to use it)? !   What do you think it competes with? Which other products do you actually meet in competition? !   Does it play well with others (i.e., other databases, other data flow tools)? !   Where does it sit in the spectrum of strategy --> tactics?Twitter Tag: #briefr
  • 26. Twitter Tag: #briefr
  • 27. !  September: Integration !  October: Database !  November: Cloud !  December: Innovators !  January: ArchitectureTwitter Tag: #briefr
  • 28. Twitter Tag: #briefr