DOCSLIB.ORG

A Novel Framework for Querying Multiparadigm Databases

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Novel Framework for Querying Multiparadigm Databases A Novel Framework for Querying Multiparadigm Databases A Thesis submitted for the award of degree of DOCTOR OF PHILOSOPHY by Karamjit Kaur (95 !"!!#$ Under the guidance of Dr% &inkle Rani Assistant Professor (omputer Science and Engineering Department ,-apar .niversity/ 'atiala (omputer Science and Engineering Department ,-apar .niversity/ 'atiala 0 12!!1/ 3NDIA July #! 5 (ontents List of Figures . ............... vi List of Tables . ................ vii Certificate . ................. ix Acknowledgments . ............ x List of Abbreviations . ............ xi Abstract . ................. xii 3ntroduction 1.1 Research Motivation . ........... 1. !ignificance of the Research . ........" 1." Research #aps% Ob'ectives and Methodolog( . ) 1.) Research Contributions . .........* 1.+ &rganization of the Thesis . .........- # Databases5 A &eview .1 Relational .atabase . ........... 1 .1.1 !hortcomings of Relational .atabases . 15 . No!0L Databases . ............ 11 .2.1 No!QL Characteristics . 2 ." NewS0L .atabases . ........... ) " NoSQ6 Data-Stores #2 ".1 3ey45alue .ata-store 635!7 . 1 ".1.1 Redis . .............. - i ".1.1.1 Data T($es in Redis . - ". Column4Oriented Data-store . "" ".2.1 HBase . .............. "+ "." .ocument .ata-store . .......... "1 ".3.1 MongoD9 . ............ )2 ".) #ra$h .ata4store . ............ )" ".4.1 Neo)' . ............... )+ ".+ Conclusion . ............... )* 1 Data 3ntegration ,e*hniques 19 ).1 .ata Integration . ............. )- ).1.1 Multidatabase and Federated .atabases . +" ).1. Mediation based integration . +) ).1." .ata ;arehouse . ......... +< ).1.) &ntology based integration . +1 ). =ol(glot4=ersistence . .......... <2 )." Conclusion . ............... <* 5 Proposed Multi-paradigm Framework5 'olyglot:3) ;9 +.1 :ntroduction.................. .............. <- +.1.1 =ol(glot4$ersistence in Healthcare .ata Management . *2 +. Architecture and Com$onents . *" +.2.1 Agents . .............. *+ +.2.1.1 Graphical :nteraction Agent . *< +.2.1. Data-store Apropos Agent . ** +.2.1." Datalog Agent . ** +.2.1.) KBo. ......... *1 +.2.1.+ !chema Extraction Agent . *- +.2.1.< Query Planning Agent . *- +.2.1.* Learning Agent . 12 +.2.1.1 Query Ma$$ing Agent . 12 ii +.2.1.- Translators and =artial Result !torage . 81 +.2.1.12 Reducer Agent . 11 +." Conclusion . ............... 1 ; Design and Maintenance of K<oD 91 <.1 :ntroduction.................. .............. 1+ <.1.1 First &rder Logic 6FOL7 . 1* <.1. .eductive .atabases . 11 <. .atalog ................. ................. 1- <.2.1 .atalog to Relational Algebra . - <." =ol(glot8:! 3nowledge-base of .ata . -< <.) Conclusion . ............... 12 2 Query and 'erformance +valuation of 'olyglotH3) !1 *.1 0uer(ing data integration s(stems . 12+ *.1.1 0uer( Languages . 12< *. =ol(glot8:! .emonstration . 12- *.2.1 MongoD9 .ata-set . 111 *.2. Neo)' .ata-set . 114 *.2." !am$le 0uer( Execution . 118 *." >xperimental Anal(sis . 1 *.) Conclusion . ............... 1 * 9 3mplementation (hallenges/ (onclusion and Future Scope #9 1.1 Challenges and :ssues . 1 - 1. Conclusion . ............... 1"1 1." Future !cope . ............... 1"< References 6ist of 'apers 'ublished List of Publications . .......... iii )*holarship Awarded iv 6ist of Figures .1 M(!0L% No!QL% New!QL Revenue . 1* . .atabase Landsca$e . ........... 2 ." CAP Theorem . .............. " ".1 .ata storage in 3ey-value data-store . - ". Redis hashes and sorted sets using $(thon . " "." Row Vs Column4oriented storage . "" ".) .ata storage in Columnar data-store . ") ".+ Column4families and 5ersioning in HBase . "< ".< :nteracting with HBase in =(thon . "1 ".* .ata storage in .ocument4oriented data-store . "- ".1 >mbedding and Referencing in Mongo.9 . )1 ".- :nteracting with MongoD9 in =(thon . ) ".10 .ata storage in Gra$h-based data-store . )) ".11 Interacting with Neo)' in =(thon . )< ).1 T($es of data integration . ......... +2 ). .ata ;arehouse Architecture . +* )." Mediation Architecture . ......... +* ).) &ntology-based .ata Integration Architecture . +- +.1 Architectural &verview of =ol(got8:! 6Pro$osed !(stem7 . * +. .etailed architecture of =ol(glot8:! 6Pro$osed !(stem7 . *) v <.1 .atalog facts% rules and ?ueries for an subset of 8:! schema. -* <. Neo4' schema extraction $rocess . -- <." 3nowledge-base of .ata . 101 *.1 Fragment of =atients and .octors Collections . 112 *. MongoD9 .atalog Facts and Rules . 113 *." !ubset of /eo4' graph database shown using Neocli$se editor . 11+ *.) Neo4' .atalog Facts and Rules . 117 *.+ =ol(glot8:! 0uer( Processing >xam$le . 119 *.< !am$le 0uer( Execution using .atalog fact base . 121 *.* =erformance com$arison of =olyglot8:! with Neo)' for retrieval o$4 eration . ................1 ) *.1 =erformance com$arison of =olyglot8:! with MongoD9 for retrieval o$eration . ...............1 + *.- =erformance com$arison of =olyglot8:! with =ostgre!QL for retrieval o$eration . ...............1 < vi 6ist of ,ables .1 .atabase Timeline . ............ 1" . No!0L Timeline . ............. 1- ." NewS0L Timeline . ............ + ).1 .etailed com$arison chart of existing $ol(glot-$ersistent solutions . < <.1 .octor Table in RDBM! . ......... -1 <. !$ecialization Table in R.BMS . -1 <." .octor4!$ecialization Table in RD9MS . - *.1 List the $atients of each doctor. 12* *. Find the medicines which have been $rescribed in the treatment of each$atient.................... ............. 121 *." Find the $atient names which are in the same ward where $atient @$at1A is admitted. 12- vii Dedicated to my loving #arents and amazing husband viii Acknowledgment First of all, I express my gratitude to the Almighty, Who blessed me with the zeal and enthusiasm to complete this work successfully. I thank my supervisor, Dr. inkle ani, Assistant !rofessor, "hapar University, !atiala for her suggestions and constant support during this research. I am grateful to her for motivating and inspiring me to go deeply into the $eld of mutiparadigm databases and supporting me throughout the life cycle of !hD studies. I am also thankful to Dr. Deepak Garg, Head of '(ED, for his guidance through the early years of chaos and confusion. I am thankful to my Doctoral committee members for their constructive comments and regularly ensuring the progress of my research work. My deep regards to Dr. Prakash %opalan, Director, Thapar University for giving me access to facilities, which have been immensely helpful for the completion of my work. I wish to thank the faculty and sta+ members of '(ED of Thapar University, !atiala for their co-operation and support. I am also very thankful to my friends of '()D research lab for their continuous motivation and moral support. My parents provided an environment that guided the $rst steps of the journey and encouraged the later ones. *y brother and sister-in,law helped me in every possible way at each and every step during last few years. My in,laws family provided me an excellent conducive environment for continuing my research. Especially my grand, father-in,law and mother-in,law were highly in.uisitive about the progress of my research work. (upport of my mother-in,law played a very crucial role in my !hD work. My husband has been my pillar of strength throughout. He has played many roles / technical mentor, best-friend and foremost a continuous source of motivation. Karamjit x List of Abbreviations HIS Hospital Information (ystem EMR )lectronic Medical ecord API Application Programming Interface SQL (tructured 0uery 1anguage CAP 'onsistency Availability and !artition "olerance GAV %lobal-As-View LAV 1ocal-As-View JSON Java (cript 4bject Notation KBoD 6nowledge-Base of Data ACID Atomicity Consistency Isolation Durability BASE 7asically Available (oft-state Eventually Consistent CRUD 'reate ead Update Delete NoSQL Not 4nly (01 PolyglotHIS !olyglot-persistent Healthcare Information (ystem xi Abstract elational databases evolved in accordance to the prevailing technological require- ments and constraints that had suitability, applicability and relevance at that time. However, times have changed and also the contemporary requirements. "o allevi, ate the problems associated with relational databases in handling present big data, which is predominantly un,structured, a new class of databases has emerged, known as No(01 databases. As and when a new class of data-storage emerges and be, comes popular, researchers start working towards its integration with the existing databases. Likewise, with the widespread use of No(01 data-stores, the problem of integrating them with existing database technology has became a challenge. The goal is to select the most appropriate data storage technology that meets the speci$c requirements of each module of the application. Amalgamation of different databases within an application is known as Mul- tiparadigm approach or Polyglot-persistence. !ersistence needs of applications are progressing from mostly relational to a mixture of data-stores. For example various modules of Health-care Information (ystem 8&IS9 use different data-stores to model data closer to their semantic usage. The researcher has showcased the applicability of our multipradigm framework in HIS, considering the variety of data and diverse categories of No(01 data-stores with which they may be managed. But the concept is equally well applicable to any other application area, where different parts of the application deals with distinct data formats. The researcher has implemented a healthcare information system : PolyglotHIS, which makes use of one relational and two No(01 data-stores. This coalition
Load more

Recommended publications
  • A Definition of Database Design Standards for Human Rights Agencies
    A Definition of Database Design Standards for Human Rights Agencies by Patrick Ball, et al. AMERICAN ASSOCIATION FOR THE ADVANCEMENT OF SCIENCE 1994 TABLE OF CONTENTS Introduction Definition of an Entity Entity versus Role versus Link What is a Link? Presentation of a Data Model Rule-types with Rule Examples and Instance Examples . 6.1 Type of Rule: Act . 6.2 Type of Rule: Relationship . 6.3 Rule-type Name: Biography Rule Parsimony: the Trade between Precision and Simplicity xBase Table Design Implementation Example . 8.1 xBase Implementation Example . 8.2 Abstract Fields & Data Types SQL Database Design Implementation Example . 9.1 Querying & Performance . 9.2 Main Difference . 9.3 Storage of the Rules in SQL Model 1. Introduction In 1993, HURIDOCS published their Standard Human Rights Event Formats (Dueck et al. 1993a) which describe standards for the collection and exchange of information on human rights abuses. These formats represent a major step forward in enabling human rights organizations to develop manual and computerized systems for collecting and exchanging data. The formats define common fields for collection of human rights event, victim, source, perpetrator and agency intervention data, and a common vocabulary for many of the fields in the formats, for example occupation, type of event and geographical location. The formats are designed as a tool leading toward both manual and computerized systems of human rights violation documentation. Before organizations implement documentation systems which will meet their needs, a wide range of issues must be considered. One of these problems is the structural problems of some data having complex relations to other data.
    [Show full text]
  • Xbase++ Language Concepts for Newbies Geek Gatherings Roger Donnay
    Xbase++ Language Concepts for Newbies Geek Gatherings Roger Donnay Introduction Xbase++ has extended the capabilities of the language beyond what is available in FoxPro and Clipper. For FoxPro developers and Clipper developers who are new to Xbase++, there are new variable types and language concepts that can enhance the programmer's ability to create more powerful and more supportable applications. The flexibility of the Xbase++ language is what makes it possible to create libraries of functions that can be used dynamically across multiple applications. The preprocessor, code blocks, ragged arrays and objects combine to give the programmer the ability to create their own language of commands and functions and all the advantages of a 4th generation language. This session will also show how these language concepts can be employed to create 3rd party add-on products to Xbase++ that will integrate seamlessly into Xbase++ applications. The Xbase++ language in incredibly robust and it could take years to understand most of its capabilities, however when migrating Clipper and FoxPro applications, it is not necessary to know all of this. I have aided many Clipper and FoxPro developers with the migration process over the years and I have found that only a basic introduction to the following concepts are necessary to get off to a great start: * The Xbase++ Project. Creation of EXEs and DLLs. * The compiler, linker and project builder . * Console mode for quick migration of Clipper and Fox 2.6 apps. * INIT and EXIT procedures, DBESYS, APPSYS and MAIN. * The DBE (Database engine) * LOCALS, STATICS, PRIVATE and PUBLIC variables. * STATIC functions.
    [Show full text]
  • An Opinionated Guide to Technology Frontiers
    TECHNOLOGY RADARVOL. 21 An opinionated guide to technology frontiers thoughtworks.com/radar #TWTechRadar Rebecca Martin Fowler Bharani Erik Evan Parsons (CTO) (Chief Scientist) Subramaniam Dörnenburg Bottcher Fausto Hao Ian James Jonny CONTRIBUTORS de la Torre Xu Cartwright Lewis LeRoy The Technology Radar is prepared by the ThoughtWorks Technology Advisory Board — This edition of the ThoughtWorks Technology Radar is based on a meeting of the Technology Advisory Board in San Francisco in October 2019 Ketan Lakshminarasimhan Marco Mike Neal Padegaonkar Sudarshan Valtas Mason Ford Ni Rachel Scott Shangqi Zhamak Wang Laycock Shaw Liu Dehghani TECHNOLOGY RADAR | 2 © ThoughtWorks, Inc. All Rights Reserved. ABOUT RADAR AT THE RADAR A GLANCE ThoughtWorkers are passionate about ADOPT technology. We build it, research it, test it, 1 open source it, write about it, and constantly We feel strongly that the aim to improve it — for everyone. Our industry should be adopting mission is to champion software excellence these items. We use them and revolutionize IT. We create and share when appropriate on our the ThoughtWorks Technology Radar in projects. HOLD ASSESS support of that mission. The ThoughtWorks TRIAL Technology Advisory Board, a group of senior technology leaders at ThoughtWorks, 2 TRIAL ADOPT creates the Radar. They meet regularly to ADOPT Worth pursuing. It’s 108 discuss the global technology strategy for important to understand how 96 ThoughtWorks and the technology trends TRIAL to build up this capability. ASSESS 1 that significantly impact our industry. Enterprises can try this HOLD 2 technology on a project that The Radar captures the output of the 3 can handle the risk.
    [Show full text]
  • Course Description
    6/20/2018 Syllabus Syllabus This is a single, concatenated file, suitable for printing or saving as a PDF for offline viewing. Please note that some animations or images may not work. Course Description This module is also available as a concatenated page, suitable for printing or saving as a PDF for offline viewing. MET CS669 Database Design and Implementation for Business This course uses the latest database tools and techniques for persistent data and object-modeling and management. Students gain extensive hands-on experience with exercises and a term project using Oracle, SQL Server, and other leading database management systems. Students learn to model persistent data using the standard Entity-Relationship model (ERM) and how to diagram those models using Entity-Relationship Diagrams (ERDs), Extended Entity-Relationship Diagrams (EERDs), and UML diagrams. Students learn the standards-based Structured Query Language (SQL) and the extensions to the SQL standards implemented in Oracle and SQL Server. Students learn the basics of database programming, and write simple stored procedures and triggers. The Role of this Course in the MSCIS Online Curriculum This is a core course in the MSCIS online curriculum. It provides students with an understanding and experience with database technology, database design, SQL, and the roles of databases in enterprises. This course is a prerequisite for the three additional database courses in the MSCIS online curriculum, which are CS674 Database Security, CS699 Data Mining and Business Intelligence and CS779 Advanced Database Management. By taking these three courses you can obtain the Concentration in Database Management and Business Intelligence. CS674 Database Security also satisfies an elective requirement for the Concentration in Security.
    [Show full text]
  • SAQE: Practical Privacy-Preserving Approximate Query Processing for Data Federations
    SAQE: Practical Privacy-Preserving Approximate Query Processing for Data Federations Johes Bater Yongjoo Park Xi He Northwestern University University of Illinois (UIUC) University of Waterloo [email protected] [email protected] [email protected] Xiao Wang Jennie Rogers Northwestern University Northwestern University [email protected] [email protected] ABSTRACT 1. INTRODUCTION A private data federation enables clients to query the union of data Querying the union of multiple private data stores is challeng- from multiple data providers without revealing any extra private ing due to the need to compute over the combined datasets without information to the client or any other data providers. Unfortu- data providers disclosing their secret query inputs to anyone. Here, nately, this strong end-to-end privacy guarantee requires crypto- a client issues a query against the union of these private records graphic protocols that incur a significant performance overhead as and he or she receives the output of their query over this shared high as 1,000× compared to executing the same query in the clear. data. Presently, systems of this kind use a trusted third party to se- As a result, private data federations are impractical for common curely query the union of multiple private datastores. For example, database workloads. This gap reveals the following key challenge some large hospitals in the Chicago area offer services for a cer- in a private data federation: offering significantly fast and accurate tain percentage of the residents; if we can query the union of these query answers without compromising strong end-to-end privacy. databases, it may serve as invaluable resources for accurate diag- To address this challenge, we propose SAQE, the Secure Ap- nosis, informed immunization, timely epidemic control, and so on.
    [Show full text]
  • Xbase PDF Class
    Xbase++ PDF Class User guide 2020 Created by Softsupply Informatica Rua Alagoas, 48 01242-000 São Paulo, SP Brazil Tel (5511) 3159-1997 Email : [email protected] Contact : Edgar Borger Table of Contents Overview ....................................................................................................................................................4 Installing ...............................................................................................................................................5 Changes ...............................................................................................................................................6 Acknowledgements ............................................................................................................................10 Demo ..................................................................................................................................................11 GraDemo ............................................................................................................................................13 Charts .................................................................................................................................................15 Notes ..................................................................................................................................................16 Class Methods .........................................................................................................................................17
    [Show full text]
  • Veritas: Shared Verifiable Databases and Tables in the Cloud
    Veritas: Shared Verifiable Databases and Tables in the Cloud Lindsey Alleny, Panagiotis Antonopoulosy, Arvind Arasuy, Johannes Gehrkey, Joachim Hammery, James Huntery, Raghav Kaushiky, Donald Kossmanny, Jonathan Leey, Ravi Ramamurthyy, Srinath Settyy, Jakub Szymaszeky, Alexander van Renenz, Ramarathnam Venkatesany yMicrosoft Corporation zTechnische Universität München ABSTRACT A recent class of new technology under the umbrella term In this paper we introduce shared, verifiable database tables, a new "blockchain" [11, 13, 22, 28, 33] promises to solve this conundrum. abstraction for trusted data sharing in the cloud. For example, companies A and B could write the state of these shared tables into a blockchain infrastructure (such as Ethereum [33]). The KEYWORDS blockchain then gives them transaction properties, such as atomic- ity of updates, durability, and isolation, and the blockchain allows Blockchain, data management a third party to go through its history and verify the transactions. Both companies A and B would have to write their updates into 1 INTRODUCTION the blockchain, wait until they are committed, and also read any Our economy depends on interactions – buyers and sellers, suppli- state changes from the blockchain as a means of sharing data across ers and manufacturers, professors and students, etc. Consider the A and B. To implement permissioning, A and B can use a permis- scenario where there are two companies A and B, where B supplies sioned blockchain variant that allows transactions only from a set widgets to A. A and B are exchanging data about the latest price for of well-defined participants; e.g., Ethereum [33]. widgets and dates of when widgets were shipped.
    [Show full text]
  • Table of Contents
    Table of Contents Introduction and Motivation Theoretical Foundations Distributed Programming Languages Distributed Operating Systems Distributed Communication Distributed Data Management Reliability Applications Conclusions Appendix Distributed Operating Systems Key issues Communication primitives Naming and protection Resource management Fault tolerance Services: file service, print service, process service, terminal service, file service, mail service, boot service, gateway service Distributed operating systems vs. network operating systems Commercial and research prototypes Wiselow, Galaxy, Amoeba, Clouds, and Mach Distributed File Systems A file system is a subsystem of an operating system whose purpose is to provide long-term storage. Main issues: Merge of file systems Protection Naming and name service Caching Writing policy Research prototypes: UNIX United, Coda, Andrew (AFS), Frangipani, Sprite, Plan 9, DCE/DFS, and XFS Commercial: Amazon S3, Google Cloud Storage, Microsoft Azure, SWIFT (OpenStack) Distributed Shared Memory A distributed shared memory is a shared memory abstraction what is implemented on a loosely coupled system. Distributed shared memory. Focus 24: Stumm and Zhou's Classification Central-server algorithm (nonmigrating and nonreplicated): central server (Client) Sends a data request to the central server. (Central server) Receives the request, performs data access and sends a response. (Client) Receives the response. Focus 24 (Cont’d) Migration algorithm (migrating and non- replicated): single-read/single-write (Client) If the needed data object is not local, determines the location and then sends a request. (Remote host) Receives the request and then sends the object. (Client) Receives the response and then accesses the data object (read and /or write). Focus 24 (Cont’d) Read-replication algorithm (migrating and replicated): multiple-read/single-write (Client) If the needed data object is not local, determines the location and sends a request.
    [Show full text]
  • The Network Data Storage Model Based on the HTML
    Proceedings of the 2nd International Conference on Computer Science and Electronics Engineering (ICCSEE 2013) The network data storage model based on the HTML Lei Li1, Jianping Zhou2 Runhua Wang3, Yi Tang4 1Network Information Center 3Teaching Quality and Assessment Office Chongqing University of Science and Technology Chongqing University of Science and Technology Chongqing, China Chongqing, China [email protected] [email protected] 2Network Information Center 4School of Electronic and Information Engineering Chongqing University of Science and Technology Chongqing University of Science and Technology Chongqing, China Chongqing, China [email protected] [email protected] Abstract—in this paper, the mass oriented HTML data refers popular NoSQL for HTML database. This article describes to those large enough for HTML data, that can no longer use the SMAQ stack model and those who today may be traditional methods of treatment. In the past, has been the included in the model under mass oriented HTML data Web search engine creators have to face this problem be the processing tools. first to bear the brunt. Today, various social networks, mobile applications and various sensors and scientific fields are II. MAPREDUCE created daily with PB for HTML data. In order to deal with MapReduce is a Google for creating web webpage index the massive data processing challenges for HTML, Google created MapReduce. Google and Yahoo created Hadoop created. MapReduce framework has become today most hatching out of an intact mass oriented HTML data processing mass oriented HTML data processing plant. MapReduce is tools for ecological system. the key, will be oriented in the HTML data collection of a query division, then at multiple nodes to execute in parallel.
    [Show full text]
  • Projects – Other Than Hadoop! Created By:-Samarjit Mahapatra [email protected]
    Projects – other than Hadoop! Created By:-Samarjit Mahapatra [email protected] Mostly compatible with Hadoop/HDFS Apache Drill - provides low latency ad-hoc queries to many different data sources, including nested data. Inspired by Google's Dremel, Drill is designed to scale to 10,000 servers and query petabytes of data in seconds. Apache Hama - is a pure BSP (Bulk Synchronous Parallel) computing framework on top of HDFS for massive scientific computations such as matrix, graph and network algorithms. Akka - a toolkit and runtime for building highly concurrent, distributed, and fault tolerant event-driven applications on the JVM. ML-Hadoop - Hadoop implementation of Machine learning algorithms Shark - is a large-scale data warehouse system for Spark designed to be compatible with Apache Hive. It can execute Hive QL queries up to 100 times faster than Hive without any modification to the existing data or queries. Shark supports Hive's query language, metastore, serialization formats, and user-defined functions, providing seamless integration with existing Hive deployments and a familiar, more powerful option for new ones. Apache Crunch - Java library provides a framework for writing, testing, and running MapReduce pipelines. Its goal is to make pipelines that are composed of many user-defined functions simple to write, easy to test, and efficient to run Azkaban - batch workflow job scheduler created at LinkedIn to run their Hadoop Jobs Apache Mesos - is a cluster manager that provides efficient resource isolation and sharing across distributed applications, or frameworks. It can run Hadoop, MPI, Hypertable, Spark, and other applications on a dynamically shared pool of nodes.
    [Show full text]
  • SQL Database Management Portal
    APPENDIX A SQL Database Management Portal This appendix introduces you to the online SQL Database Management Portal built by Microsoft. It is a web-based application that allows you to design, manage, and monitor your SQL Database instances. Although the current version of the portal does not support all the functions of SQL Server Management Studio, the portal offers some interesting capabilities unique to SQL Database. Launching the Management Portal You can launch the SQL Database Management Portal (SDMP) from the Windows Azure Management Portal. Open a browser and navigate to https://manage.windowsazure.com, and then login with your Live ID. Once logged in, click SQL Databases on the left and click on your database from the list of available databases. This brings up the database dashboard, as seen in Figure A-1. To launch the management portal, click the Manage icon at the bottom. Figure A-1. SQL Database dashboard in Windows Azure Management Portal 257 APPENDIX A N SQL DATABASE MANAGEMENT PORTAL N Note You can also access the SDMP directly from a browser by typing https://sqldatabasename.database. windows.net, where sqldatabasename is the server name of your SQL Database. A new web page opens up that prompts you to log in to your SQL Database server. If you clicked through the Windows Azure Management Portal, the database name will be automatically filled and read-only. If you typed the URL directly in a browser, you will need to enter the database name manually. Enter a user name and password; then click Log on (Figure A-2).
    [Show full text]
  • Learning Key-Value Store Design
    Learning Key-Value Store Design Stratos Idreos, Niv Dayan, Wilson Qin, Mali Akmanalp, Sophie Hilgard, Andrew Ross, James Lennon, Varun Jain, Harshita Gupta, David Li, Zichen Zhu Harvard University ABSTRACT We introduce the concept of design continuums for the data Key-Value Stores layout of key-value stores. A design continuum unifies major Machine Databases K V K V … K V distinct data structure designs under the same model. The Table critical insight and potential long-term impact is that such unifying models 1) render what we consider up to now as Learning Data Structures fundamentally different data structures to be seen as \views" B-Tree Table of the very same overall design space, and 2) allow \seeing" Graph LSM new data structure designs with performance properties that Store Hash are not feasible by existing designs. The core intuition be- hind the construction of design continuums is that all data Performance structures arise from the very same set of fundamental de- Update sign principles, i.e., a small set of data layout design con- Data Trade-offs cepts out of which we can synthesize any design that exists Access Patterns in the literature as well as new ones. We show how to con- Hardware struct, evaluate, and expand, design continuums and we also Cloud costs present the first continuum that unifies major data structure Read Memory designs, i.e., B+tree, Btree, LSM-tree, and LSH-table. Figure 1: From performance trade-offs to data structures, The practical benefit of a design continuum is that it cre- key-value stores and rich applications.
    [Show full text]