Teradata unity

  • 720 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
720
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This is the pictorial view of the Teradata Analytical Ecosystem. It provides the foundation to host and analyze all the businesses data. Most customers will not have everything portrayed in this graphic, but may have a subsets as appropriate for their business. Data starts from the source or transactional systems such as sales, inventory, and customer information. The data is then loaded into the primary production integrated data warehouse (EDW) using commercial Extraction and Transformation Tools (ETL) along with Teradata bundled utilities. Backup, Archival, and Retrieval (BAR) is used for backup/archival purposes as well as for restoring systems in case of a system loss. Customers may chose to create Data Labs within the production data warehouse for special purpose applications, testing, or proof of concepts. Customers may also chose to stay in this type of environment for a period of time without the need to add any additional appliances. But overtime customers will add other appliance class systems to complement their integrated data warehouse environment or they may automatically inherit other data warehouses due to consolidations or acquisitions: Test or development appliance (Data Mart Appliance) Special purpose applications on a dedicated dependent data mart (Data Warehouse Appliance) Teradata appliance to support large data volumes (Extreme Data Appliance) Entry level data warehouse (Data Warehouse Appliance) High performance pure solid-state devices (SSD) (Extreme Performance Appliance) Data will be synchronized between the Data Warehouse and the Appliances in a variety of ways and we will discuss the synchronization options later. As customers employ these special purpose systems for their distinct workloads, we call these architectures “dual systems for workload optimization”, which in essence means that the right workload is put on the best platform to achieve the price/performance/value required for that application. Finally, as the business requirements increase demand for high availability, customers will not only increase single system availability, but will choose to employ a dual systems strategy for high availability and disaster recovery. We call these architectures “dual systems for availability”. The most common availability architecture is Dual Active, where two systems are configured in an Active/Active configuration. Another common availability architecture is Active/Standby, followed by an environment which only delivers disaster recovery where the primary production system is coupled with a disaster recovery system at a remote location that is only used in a true disaster. NOTE – although BAR is only shown on two systems in this diagram, BAR should be on all production systems and may be a dedicated or shared infrastructure. BAR was left off the other systems just to keep the slide from getting too busy. Business users access the analytical applications such as CRM and SCM as well as BI solutions which complete the ecosystem by providing subject-based analytics with familiar user interfaces such as dashboards and scorecards and also direct access to the analytical data Finally, the database administrators (DBA’s) and system administrators get a single operational view to the entire Analytical Ecosystem for systems management, alerts, and resource optimization. The resulting Teradata Analytical Ecosystem is a very flexible environment which enables enterprise analytics.
  • Questions & Answers Now, we welcome your questions. Please state your name and medium or blog, then ask your question. Please use the microphones – just signal Dan and Mike and they’ll bring a mike to you. First question?   [After last question] The buffet lunch is set up just outside this room. Please make your selections and come back in. Scott and I will be joining you. And please join us tomorrow right here, 12:15 PM, for a briefing featuring Oliver Ratzesberger of eBay and the Teradata Petabyte Power Players. Thank you for joining us today.

Transcript

  • 1. Teradata Unity Imad Birouty, Program Marketing Manager 7/19/2011
  • 2. Purpose of Briefing
    • Introduce you to Teradata Unity
    • Feedback on product, positioning, and message
  • 3. Teradata Analytical Ecosystem Overview
    • Flexible, Integrated Analytics
    DATA SOURCES BAR DEEP HISTORY BAR INTEGRATED DATA WAREHOUSE DUAL SYSTEMS DATA LAB INDEPENDENT DATA MART ANALYTIC PLATFORM DATA MARTS TEST/ DEV MULTI STRUCTURED DATA HADOOP STRUCTURED STRUCTURED
  • 4. Teradata Unity Enables the Analytical Ecosystem
    • Key features that turn a multi-system
    • environment into an orchestrated
    • Analytical Ecosystem
    • Query Management
      • Controlled routing of user sessions for high availability and failover
      • Intelligent and automatic query routing for workload optimization
    • Multi-System Synchronization
      • Enables database (object) synchronization across participating systems to maintain consistent data models with minimal effort
      • Provides data synchronization for transactional updates across participating systems to maintain a single version of the truth
    • Auto Resubmit
      • Protects users and applications against database restarts
      • No need to re-submit queries
  • 5. Teradata Unity Provides Query Management
    • Two methods for query management
      • User session routing
      • Individual query routing
    User Session Routing Great for session and workload control across systems, especially when high availability failover is required Individual Query Routing Great when systems contain different data and/or for fast setup where session control isn’t required
  • 6. Multi-System Synchronization Database Synchronization
    • Architectural Flexibility
    • All Platform Family supported
    • Any number of systems can participate
    • Databases objects don’t have to be identical (tables, users, view, macros,…)
    Data Synchronization John 123 82.50 Bill 858 12.50 Jill 545 72.12 Tom 684 64.29 Joe 367 97.24 Bob 826 55.19 John 123 82.50 Bill 858 12.50 Jill 545 72.12 Tom 684 64.29 Joe 367 97.24 Bob 826 55.19 Tom 684 64.29 Joe 367 97.24 Bob 826 55.19
    • Data Flexibility
    • Not all tables have to be on all systems
    • Updates sent to all participating systems
    • Data updates applied in the order received
  • 7. SQL Multicast
    • SQL Multicast is a Teradata Unity feature that simultaneously sends SQL updates to multiple Teradata systems and routes queries to the least busy system which can satisfy the query
      • One-to-many, many-to-one, and one-to-one communication between Unity and Teradata systems
      • It keeps a copy of the data dictionary participating Teradata systems and routes SQL accordingly
    • Benefits
    • Same effort as managing one system
      • Administrator submits SQL one time
      • Unity efficiently sends SQL statements to all participating
    • Ensures data and database integrity
      • SQL on each system executed in the order received
      • SQL held on Teradata Unity system until processed successfully on all participating systems
  • 8. SQL Multicast
    • SQL Multicast used in two ways
      • Synchronization
      • Queries
    Synchronization Queries
    • Systems kept in sync
    • Data and database updates sent to all participating systems
    • Not all systems have to be the same
    • Updates can come from users, applications, or SQL-based utilities (TPump or TPT Streams)
    • Intelligent query routing
    • Unity determines which systems can satisfy the query and sends to the one with the shortest update queue
    • Read-only queries sent to only one system (not query federation)
  • 9. Auto Resubmit
    • Teradata Unity will resubmit in-flight queries following a database restart to an alternate Teradata system which can satisfy the query
      • Automatic feature
        • No changes required for applications or queries
        • Removes the burden from application developers
        • Improves user experience
      • Auto Resubmit only available through Teradata Unity
  • 10. Teradata Dual System Solution Architecture
    • Teradata Unity 13.10
    E D C Unity Teradata System B Teradata System A Query Routing Schema/Data Synchronization
    • Queries
    • DDL changes
    • SQL data updates
    • Read
    • Apply
    Sequencer Data Dictionary Parser Monitoring/Control Data Synchronization SQL Multicast Data Loads * Replication * Data Mover * Status * This method of data sync can coexist with Unity, but needs to be managed and coordinated outside Unity Users/ Applications/ SQL Utilities Users/ Applications/ SQL Utilities Users/ Applications/ SQL Utilities Teradata Multi-System Manager Monitoring Administration Operational Control
  • 11. Teradata Unity Benefits
    • Key features that turn a multi-system
    • environment into an orchestrated
    • Analytical Ecosystem
    • Query Management
      • Controlled routing of user sessions for high availability and failover
      • Intelligent and automatic query routing for workload optimization
    • Multi-System Synchronization
      • Enables database (object) synchronization across participating systems to maintain consistent data models with minimal effort
      • Provides data synchronization for transactional updates across participating systems to maintain data consistency
    • Auto Resubmit
      • Protects users and applications against database restarts
      • No need to re-submit queries
    • Enables a robust Teradata Analytical Ecosystem
  • 12. Companies Who Will Benefit from Unity
    • Customers moving towards a Teradata Analytical Ecosystem and planning to employ Dual Systems for Availability or Workload Optimization
    • Customers who have these characteristics:
      • Need to route user sessions/queries between systems
        • Including upgrade/migration path for existing Query Director customers
      • Have dual systems which are kept in sync
        • With same data and data model for the subset of objects kept in sync
      • Have SQL-based transactional updates in a multi-system environment
      • Cannot tolerate the system resource penalty of Data Mover or Replication Services
    Companies moving towards a Teradata Analytical Ecosystem and planning to employ Dual Systems for Availability or Workload Optimization
  • 13. Dual System Capabilities Aligned to Products Teradata Multi-System Manager Teradata Unity Teradata Data Mover Teradata Rep Services Dual Load Monitoring/Control Component / Process health ● Application readiness ● SLA management ● Query Routing Session-based routing ● Query-based routing ● Data Synchronization SQL-based transactional updates ● ● Data model/schema updates ● ● (limited) Use of Load Utilities ● ● ● Large batch, low latency ● Large batch, mid/high latency ● Mini-batch, low latency ● ● Mini-batch, mid/high latency ● ● Professional Services ● ● ● ● ● Customer Services ● ● ● ● ●
  • 14. Questions and Answers