DOCSLIB.ORG

SAP Sybase IQ 16 Product Overview What Was the Motivation for SAP Sybase IQ 16?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SAP Sybase IQ 16 Product Overview What Was the Motivation for SAP Sybase IQ 16? SAP Sybase IQ 16 Product Overview What was the motivation for SAP Sybase IQ 16? Marketplace Business Challenges SAP Sybase IQ 16… Lost revenues due to lack Cost-effective petabyte-scale EDW of insight platform Exploding Data Volumes Quickly handles and shares all the Slow Performance data in your world The need for Speed High performance and efficiency for user-driven analytics workloads High Costs & Complexities Rising IT Costs and Secure Complexity Data Management Challenges Ensures your data is always available, day or night © 2013 SAP AG. All rights reserved. Public 2 SAP Sybase IQ 16 SAP Sybase IQ transforms the way companies compete and win through actionable intelligence delivered at the speed of business to more people and processes. © 2013 SAP AG. All rights reserved. Public 3 Value of SAP Sybase IQ 16 1 Exploits the value of Big Data 2 Transforms businesses through deeper insights 3 Extends the power of analytics across the entire enterprise © 2013 SAP AG. All rights reserved. Public 4 SAP Sybase IQ 16 Path to Actionable Intelligence 2009 2009 2010 2011 2011 1H 2013 XLDB Analytics MapReduce API PlexQ MPP Foundation Full text search; Web 2.0 API In-database analytics Very large database (VLDB) platform foundation © 2013 SAP AG. All rights reserved. Public 5 SAP Sybase IQ 16 What’s New! SAP Sybase IQ 16 Engine Comprehensive web- Web-enabled analytics Web based administration and monitoring and administration based Web based monitoring and administration Communications and security Resilient Multiplex grid Resilient Information lifecycle management lifecycle Information withstands network Role-based access control interrupts and server LDAP authentication failures Enterprise-grade RBAC authorization and LDAP Query engine authentication Aggressive scale out architecture grid Multiplex Loading engine Hash partitioned tables Aggressively scaled out and data affinity High performance, fully query engine Fully parallel bulk loading parallel Text search In-database analytics Intelligent query engine New indexing technology for with data affinity for “shared increased compression and Column indexing N-bit and nothing” performance on a fast, incremental batch loads subsystem tiered indexing flexible “shared everything” Column store architecture New Generation Re-engineered column PETABYTE SCALE store store for extreme data Low latency, write optimized store Low latency, concurrent volumes write optimized delta store Storage area network © 2013 SAP AG. All rights reserved. Public 6 SAP Sybase IQ A comprehensive analytics platform Sybase Bradmark, SAS, SPSS, PowerDesigner, Symantec, KXEN, Fuzzy BMMSoft, Sybase Replication Whitesands, Logix, Zementis, SOLIX, and PBS Server, Quest, and and Visual SAP and Panopticon ZEND Numerics Optimized BI and Development and Packaged ILM EIM to model and Predictive analytics Ecosystem administration tools applications replicate Application services Hadoop DBMS and R Comprehensive In-database analytics Built-in full- Web 2.0 Big Data open ANSI SQL with with MapReduce and text search APIs source APIs OLAP simulator Most mature Comprehensive MPP queries, virtual High-speed Structured and column store lifecycle tiering marts, and user scaling loads unstructured store © 2013 SAP AG. All rights reserved. Public 7 SAP Sybase IQ is a Key Component in the SAP Real-Time Data Platform Unified open software platform for real-time business SAP Real-time Data Platform SAP Real-Time Data Platform foundations Common programming ● Cross-paradigm data access for new APIs models of value discovery. SAP Sybase Sybase SAP ● Hyper-performance on all classes of SAP Sybase ASE SAP Sybase IQ application and usage scenarios transactions EDW ● Price-Performance value across all use Control cases In-memory/real-time C Benefits odeling SAP HANA enter enter m ● Execute, record, analyze, and optimize without system limitations m SAP Sybase ESP SAP Sybase SQL onitoring Hadoop ● Embrace and extend across variations of streams SAP Sybase PowerDesigner Sybase SAP Big Data Anywhere data forms and processing models mobile and embedded ● Common modeling, integrated development environment, shared SAP Data Services / SAP Information Steward systems management infrastructure, and information management deployment-independent solutions ● Trusted and unified data environment © 2013 SAP AG. All rights reserved. Public 8 SAP Sybase IQ 16 Architectural Details SAP Sybase IQ 16 Innovations for extremely large databases (XLDB) Storage Architecture Loading Engine • New generation column store • Fully parallel bulk loading • New partitioning and compression • Real-time loading into delta store SAP Sybase IQ Petabytes XLDB Real-time Analytics System Reliability Query Processing • Grid resiliency • Data affinity • LDAP and role-based security • Aggressively parallel and distributed © 2013 SAP AG. All rights reserved. Public 10 SAP Sybase IQ 16 Architecture © 2013 SAP AG. All rights reserved. Public 11 SAP SYBASE IQ 16 NEW COLUMN STORE ARCHITECTURE Before … Value proposition Logical Enhanced compression page of fixed sized Storage savings cells Improved I/O bandwidth Architectural considerations offset = ((rowID – start rowID ) – 1 / Support variable number of cells per page cellsPerPage Support various page formats within a column High performance access paths NOW… Even with variable length data, insert/update/delete Logical cell values efficiently into an existing page page of Richer metadata variable sized cells directory © 2013 SAP AG. All rights reserved. Public 12 SAP SYBASE IQ 16 N-BIT DICTIONARY COMPRESSION Value proposition Reduced memory footprint Raw Data = 400 MB; 1 Billion 4-byte integer values fn (N) Improved effective I/O rates N Token Size Savings More efficient table scans 2 (1B * 2 ) / 8 = 250MB 93.75% 3 (1B * 3 ) / 8 = 375MB 90.6% Reduced disk space 4 (1B * 4 ) / 8 = 500MB 87.5% ……. 24 (1B * 24 ) / 8 = 3000MB 25% Architectural considerations N-bit FP, instead of 1, 2 and 3-byte FPs Different data pages for same column can have different values of “N” for N-bit No more requirement to rollover FP format for all column data 2->3 Column is N-bit by default, unless otherwise specified to be flat 3->4 4->5 5->6 Options provided to set threshold for rollover to flat (to prevent large dictionaries) 6->8 8->10 Options provided to prevent rollover to flat (to prevent long rollover time) 10->12 12->16 16->21 Compatibility mode allows the database to mimic IQ 15 rollover behavior 21->24 © 2013 SAP AG. All rights reserved. Public 13 SAP SYBASE IQ 16 SMALL BATCH LOAD PERFORMANCE Value proposition Improved performance of frequent, small batch loads Predictable performance of small batch loads: performance is proportional to the size of the data being loaded, not the table being updated Small tree Periodic component Merge Architectural considerations Btree- Inserting into a large High Group (HG) b-tree Trickle based index is costly insert index HG index will have a tiered structure with a small tree component and a large tree component Small, batch loads into the HG index are written to the small tree component quickly and synchronously The small tree component is periodically merged into the large tree component as a background task © 2013 SAP AG. All rights reserved. Public 14 SAP SYBASE IQ 16 FULLY PARALLEL BULK LOAD Before… Value proposition Serial and parallel two phase load process Raw data and bitmapped indexes – partly parallel: mixture of horizontal Improved performance and vertical processing Maximize use of existing cores on the machine B-Tree based indexes (HG, TEXT. WD) – fully parallel Dynamic load balancing Numerous bottlenecks: Architectural considerations • Complex thread scheduling Load an index/column concurrently with multiple threads • Expensive synchronization points Remove all bottlenecks which contribute to • Steps that are executed too infrequently to keep threads busy inefficient use of CPU and storage Dynamically scale up and down degree of parallelism depending on the workload NOW … Fully parallel two phase load process Raw data– fully parallel All secondary indexes – fully parallel © 2013 SAP AG. All rights reserved. Public 15 SAP SYBASE IQ 16 HIGH VELOCITY DATA LOADING Value proposition Continuous analytics over operational data Hybrid Table High velocity, concurrent data modifications Storage Insert/Update/Delete IQ DML Write ahead/commit Exploit large memory and core footprints engine In- RLV log on Architectural considerations memory shared RLV rows RLV Store store Write optimized in-memory In-memory RLV (Row- Lock Manager View Consistent periodic merge level versioned) store global row space Row level locking, and statement snapshot IQ query isolation engine IQ main on main rows shared store Low latency micro operations In-memory RLV store has reduced compression, no sorting, no indexing Transaction Consistent View Version Manager Fully recoverable with dedicated transaction log Manager Manager Asynchronous data transfer from In-memory RLV store to IQ main store Users choose which tables are In-memory RLV tables © 2013 SAP AG. All rights reserved. Public 16 SAP SYBASE IQ 16 QUERY SCALE OUT – HASH PARTITIONING Value proposition Gives best of both worlds of shared everything and shared nothing Decreases hardware needs and localizes processing Architectural considerations Data is automatically partitioned during loading with built- in hash algorithms Data is divided into persistent subsets Reduces results sharing More efficient CPU usage Reduces instantaneous temp usage Optimizer will use hash partitions
Load more

Recommended publications
  • Oracle Database VLDB and Partitioning Guide, 11G Release 2 (11.2) E25523-01
    Oracle® Database VLDB and Partitioning Guide 11g Release 2 (11.2) E25523-01 September 2011 Oracle Database VLDB and Partitioning Guide, 11g Release 2 (11.2) E25523-01 Copyright © 2008, 2011, Oracle and/or its affiliates. All rights reserved. Contributors: Hermann Baer, Eric Belden, Jean-Pierre Dijcks, Steve Fogel, Lilian Hobbs, Paul Lane, Sue K. Lee, Diana Lorentz, Valarie Moore, Tony Morales, Mark Van de Wiel This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Data Warehouse Fundamentals for Storage Professionals – What You Need to Know EMC Proven Professional Knowledge Sharing 2011
    Data Warehouse Fundamentals for Storage Professionals – What You Need To Know EMC Proven Professional Knowledge Sharing 2011 Bruce Yellin Advisory Technology Consultant EMC Corporation [email protected] Table of Contents Introduction ................................................................................................................................ 3 Data Warehouse Background .................................................................................................... 4 What Is a Data Warehouse? ................................................................................................... 4 Data Mart Defined .................................................................................................................. 8 Schemas and Data Models ..................................................................................................... 9 Data Warehouse Design – Top Down or Bottom Up? ............................................................10 Extract, Transformation and Loading (ETL) ...........................................................................11 Why You Build a Data Warehouse: Business Intelligence .....................................................13 Technology to the Rescue?.......................................................................................................19 RASP - Reliability, Availability, Scalability and Performance ..................................................20 Data Warehouse Backups .....................................................................................................26
    [Show full text]
  • Study Material for B.Sc.Cs Dataware Housing and Mining Semester - Vi, Academic Year 2020-21
    STUDY MATERIAL FOR B.SC.CS DATAWARE HOUSING AND MINING SEMESTER - VI, ACADEMIC YEAR 2020-21 UNIT CONTENT PAGE Nr I DATA WARE HOUSING 03 II BUSINESS ANALYSIS 10 III DATA MINING 18 IV ASSOCIATION RULE MINING AND CLASSIFICATION 35 V CLUSTER ANALYSIS 53 Page 1 of 66 STUDY MATERIAL FOR B.SC.CS DATAWARE HOUSING AND MINING SEMESTER - VI, ACADEMIC YEAR 2020-21 UNIT I: DATA WAREHOUSING Data warehousing Components: ->Overall Architecture Data warehouse architecture is Based on a relational database management system server that functions as the central repository (a central location in which data is stored and managed) for informational data In the data warehouse architecture, operational data and processing is separate and data warehouse processing is separate. Central information repository is surrounded by a number of key components. These key components are designed to make the entire environment- (i) functional, (ii) manageable and (iii) accessible by both the operational systems that source data into warehouse by end-user query and analysis tools. Page 2 of 66 STUDY MATERIAL FOR B.SC.CS DATAWARE HOUSING AND MINING SEMESTER - VI, ACADEMIC YEAR 2020-21 The source data for the warehouse comes from the operational applications As data enters the data warehouse, it is transformed into an integrated structure and format The transformation process may involve conversion, summarization, filtering, and condensation of data Because data within the data warehouse contains a large historical component the data warehouse must b capable of holding and managing large volumes of data and different data structures for the same database over time. ->Data Warehouse Database Central data warehouse database is a foundation for data warehousing environment.
    [Show full text]
  • Public 1 Agenda
    © 2013 SAP AG. All rights reserved. Public 1 Agenda Welcome Agenda • Introduction to Dobler Consulting • SAP IQ Roadmap – What to Expect • Q&A Presenters • Courtney Claussen - SAP IQ Product Management • Peter Dobler - CEO Dobler Consulting Closing © 2013 SAP AG. All rights reserved. Public 2 Introduction to Dobler Consulting Dobler Consulting is a leading information technology and database services company, offering a broad spectrum of services to their clients; acting as your Trusted Adviser, Provide License Sales, Architectural Review and Design Consulting, Optimization Services, High Availability review and enablement, Training and Cross Training, and lastly ongoing support and preventative maintenance. Founded in 2000, the Tampa consulting firm specializes in SAP/Sybase, Microsoft SQL Server, and Oracle. Visit us online at www.doblerconsulting.com, or contact us at 813 322 3240, or [email protected]. © 2013 SAP AG. All rights reserved. Public 3 Your Data is Your DNA, Dobler Consulting Focus Areas Strategic Database Consulting SAP VAR D&T DBA Database Managed Training Services Programs Cross-Platform Expertise SAP Sybase® SQL Server® Oracle® © 2013 SAP AG. All rights reserved. Public 4 What’s Ahead ISUG-TECH Annual Conference April 14-17, Atlanta • Register at http://my.isug.com/conference/registration • Early Bird ending 2/28/14 (free hotel room with registration) SAPPHIRENOW Annual Conference June 3-5, Orlando • Come visit our kiosk in the exhibition hall © 2013 SAP AG. All rights reserved. Public 5 SAP IQ Roadmap Dobler Events Webinar Courtney Claussen / SAP IQ Product Management February 27, 2014 Disclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision.
    [Show full text]
  • Database Machines in Support of Very Large Databases
    Rochester Institute of Technology RIT Scholar Works Theses 1-1-1988 Database machines in support of very large databases Mary Ann Kuntz Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Kuntz, Mary Ann, "Database machines in support of very large databases" (1988). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Rochester Institute of Technology School of Computer Science Database Machines in Support of Very large Databases by Mary Ann Kuntz A thesis. submitted to The Faculty of the School of Computer Science. in partial fulfillment of the requirements for the degree of Master of Science in Computer Systems Management Approved by: Professor Henry A. Etlinger Professor Peter G. Anderson A thesis. submitted to The Faculty of the School of Computer Science. in partial fulfillment of the requirements for the degree of Master of Science in Computer Systems Management Approved by: Professor Henry A. Etlinger Professor Peter G. Anderson Professor Jeffrey Lasky Title of Thesis: Database Machines In Support of Very Large Databases I Mary Ann Kuntz hereby deny permission to reproduce my thesis in whole or in part. Date: October 14, 1988 Mary Ann Kuntz Abstract Software database management systems were developed in response to the needs of early data processing applications. Database machine research developed as a result of certain performance deficiencies of these software systems.
    [Show full text]
  • Requirements for XML Document Database Systems Airi Salminen Frank Wm
    Requirements for XML Document Database Systems Airi Salminen Frank Wm. Tompa Dept. of Computer Science and Information Systems Department of Computer Science University of Jyväskylä University of Waterloo Jyväskylä, Finland Waterloo, ON, Canada +358-14-2603031 +1-519-888-4567 ext. 4675 [email protected] [email protected] ABSTRACT On the other hand, XML will also be used in ways SGML and The shift from SGML to XML has created new demands for HTML were not, most notably as the data exchange format managing structured documents. Many XML documents will be between different applications. As was the situation with transient representations for the purpose of data exchange dynamically created HTML documents, in the new areas there is between different types of applications, but there will also be a not necessarily a need for persistent storage of XML documents. need for effective means to manage persistent XML data as a Often, however, document storage and the capability to present database. In this paper we explore requirements for an XML documents to a human reader as they are or were transmitted is database management system. The purpose of the paper is not to important to preserve the communications among different parties suggest a single type of system covering all necessary features. in the form understood and agreed to by them. Instead the purpose is to initiate discussion of the requirements Effective means for the management of persistent XML data as a arising from document collections, to offer a context in which to database are needed. We define an XML document database (or evaluate current and future solutions, and to encourage the more generally an XML database, since every XML database development of proper models and systems for XML database must manage documents) to be a collection of XML documents management.
    [Show full text]
  • A Methodology for Evaluating Relational and Nosql Databases for Small-Scale Storage and Retrieval
    Air Force Institute of Technology AFIT Scholar Theses and Dissertations Student Graduate Works 9-1-2018 A Methodology for Evaluating Relational and NoSQL Databases for Small-Scale Storage and Retrieval Ryan D. Engle Follow this and additional works at: https://scholar.afit.edu/etd Part of the Databases and Information Systems Commons Recommended Citation Engle, Ryan D., "A Methodology for Evaluating Relational and NoSQL Databases for Small-Scale Storage and Retrieval" (2018). Theses and Dissertations. 1947. https://scholar.afit.edu/etd/1947 This Dissertation is brought to you for free and open access by the Student Graduate Works at AFIT Scholar. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of AFIT Scholar. For more information, please contact [email protected]. A METHODOLOGY FOR EVALUATING RELATIONAL AND NOSQL DATABASES FOR SMALL-SCALE STORAGE AND RETRIEVAL DISSERTATION Ryan D. L. Engle, Major, USAF AFIT-ENV-DS-18-S-047 DEPARTMENT OF THE AIR FORCE AIR UNIVERSITY AIR FORCE INSTITUTE OF TECHNOLOGY Wright-Patterson Air Force Base, Ohio DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited. AFIT-ENV-DS-18-S-047 The views expressed in this paper are those of the author and do not reflect official policy or position of the United States Air Force, Department of Defense, or the U.S. Government. This material is declared a work of the U.S. Government and is not subject to copyright protection in the United States. i AFIT-ENV-DS-18-S-047 A METHODOLOGY FOR EVALUATING RELATIONAL AND NOSQL DATABASES FOR SMALL-SCALE STORAGE AND RETRIEVAL DISSERTATION Presented to the Faculty Department of Systems and Engineering Management Graduate School of Engineering and Management Air Force Institute of Technology Air University Air Education and Training Command In Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy Ryan D.
    [Show full text]
  • VLDB Prerequisite for the Success of Digital India 02 Content
    VLDB Prerequisite for the success of Digital India 02 Content Foreword 05 Introduction to Very Large Database 06 Adoption of VLDB 07 Overview of Digital India Programme 10 How VLDB Can Enable Digital India Programme 12 Key VLDB Challenges and Solutions 13 Conclusion 20 References 21 Contacts 21 03 VLDB | Prerequisite for the success of Digital India 04 VLDB | Prerequisite for the success of Digital India Foreword A few decades ago, data was considered a byproduct To tap ongoing momentum of digitizing India, there is a of algorithms or processes, not quite an integral great need to develop an atmosphere of impregnable part. But as the algorithms started being used for association between government, industry and businesses, it was realized that data generated is common man. A new kind of professional has not just a byproduct, rather an essential part of the emerged, the data scientist, who possesses the skills of process. Personal desktops also began using client- software programmer, statistician and artist to extract server databases regularly. Two decades later, we see the data. With time, the data generated and processed databases being involved in activities we perform on a will further increase and new solutions will have to be daily basis. The presence of the “Industrial Revolution devised, but this first step is essential in ensuring that of Data” is being felt all over the world, from science the whole country moves towards digitization as one. to the arts, from business to government. Digital information increases tenfold every five years that The purpose of this report is to promote discussions results in a vast amount of data being shared.
    [Show full text]
  • Big Data Query Optimization -Literature Survey
    Big Data Query Optimization -Literature Survey Anuja S. ( [email protected] ) SRM Institute of Science and Technology Malathy C. SRM Institute of Science and Technology Research Keywords: Big data, Parallelism, optimization, hadoop, and map reduce. Posted Date: July 12th, 2021 DOI: https://doi.org/10.21203/rs.3.rs-655386/v1 License: This work is licensed under a Creative Commons Attribution 4.0 International License. Read Full License Page 1/9 Abstract In today's world, most of the private and public sector organizations deal with massive amounts of raw data, which includes information and knowledge in their secret layer. In addition, the format, scale, variety, and velocity of generated data make it more dicult to use the algorithms in an ecient manner. This complexity necessitates the use of sophisticated methods, strategies, and algorithms to solve the challenges of managing raw data. Big data query optimization (BDQO) requires businesses to dene, diagnose, forecast, prescribe, and cognize hidden growth opportunities and guiding them toward achieving market value. BDQO uses advanced analytical methods to extract information from an increasingly growing volume of data, resulting in a reduction in the diculty of the decision-making process. Hadoop, Apache Hive, No SQL, Map Reduce, and HPCC are the technologies used in big data applications to manage large data. It is less costly to consume data for query processing because big data provides scalability. However, small businesses will never be able to query large databases. Joining tables with millions of tuples could take hours. Parallelism, which solves the problem by using more processors, may be a potential solution.
    [Show full text]
  • Oracle Database 12C Release 2 for Data Warehousing and Big Data
    Oracle Database 12c Release 2 for Data Warehousing and Big Data ORACLE WHITE PAPER | NOVEMBER 2016 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 1 | ORACLE DATABASE 12C RELEASE 2 FOR DATA WAREHOUSING AND BIG DATA Introduction 3 Big Data: The Evolution of Data Warehousing 4 Oracle Database 12c Release 2 and Oracle Exadata: A Data Warehouse as a Foundation for Big Data 5 Exadata 5 Oracle Database In-Memory 6 Query Performance 6 Data Management 7 Partitioning 7 Compression 8 Read Consistency and Online operations 8 Analytics and SQL 9 SQL Extensions for Analytics 9 Approximate Query Processing 9 SQL Extensions for Non-relational Data 10 Analytic Views 10 Advanced Analytics 10 OLAP 10 Conclusion 11 Introduction What is a data warehouse? Quite simply, a data warehouse is a database built for the purposes of analysis. “Data warehouses” encompass a huge range of applications today, from large-scale advanced analytical data stores supporting dozens of sophisticated analysts to pre-built business intelligence applications with tens of thousands of users, and from enterprise-wide data warehouses to departmental data marts. Data warehouses are now a mainstay of the IT infrastructure, enabling both long-term strategic planning and agile responses to new market conditions.
    [Show full text]
  • Very Large Databases: Challenges and Strategies
    International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395-0056 Volume: 05 Issue: 11 | Nov 2018 www.irjet.net p-ISSN: 2395-0072 Very Large Databases: Challenges and Strategies Ogbonna J. C.1, Nwokoma F. O. 2, Alala A. G. 3 1Reseacher, Dept. of Computer Science, Clifford University Owerrinta, Abia State Nigeria 2Reseacher, Dept. of Computer Science, Federal University of Technology Owerri, Imo State Nigeria 3Reseacher, Dept. of Library and Information Science, Clifford University Owerrinta, Abia State Nigeria ---------------------------------------------------------------------***--------------------------------------------------------------------- Abstract - The world of IT has grown to the point that the 1.1 Very Large Database Challenges rate at which data is being generated calls for appropriate techniques and strategies to handle such large data set called The Very Large Database challenges include the following: Big Data through an appropriate database management There is a steady growth in the size of the database. system beyond the traditional DBMS. As at 30 years ago, data of size 100GB could have been regarded as a very large data, There is no minimum absolute size for a very large but in today’s environment, a new database deployment in a database. large IT industry might start at 1TB meaning that 100GB may It is not cost effective to perform operations against be regarded today as a small database size. The transition a system of such size. from desktop computing to mobile computing also has increase the rate of the usage of mobile devices since these What are the best ways to capture, manage, backup devices are mobile, cheap, easily purchased and easily and recover data in a very large database systems? programmed, though having relatively low processing 1.2 Trends Responsible for the Steady Growth in capabilities.
    [Show full text]
  • VLDB - an Analysis of DB2 at Very Large Scale - D13
    VLDB - An Analysis of DB2 at Very Large Scale - D13 Austin Clifford IBM Session Code: 2130 Fri, May 18, 2012 (08:00 AM - 09:00 AM) | Platform: DB2 for LUW - II Presentation Objectives 1) Design & implementation of a VLDB. 2) Benefits and best practice use of DB2 Warehouse features. 3) Ingesting data into VLDB. 4) Approach & considerations to scaling out VLDB as the system grows. 5) Management and problem diagnosis of a VLDB. Disclaimer ●© Copyright IBM Corporation 2012. All rights reserved. ●U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ●THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE. •IBM, the IBM logo, ibm.com, and DB2 are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
    [Show full text]