DOCSLIB.ORG

A Language for Interoperability in Relational Multi-Database Systems*

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Language for Interoperability in Relational Multi-Database Systems* SchemaSQL - A Language for Interoperability in Relational Multi-database Systems* Laks V. S. Lakshmanan+ Fereidoon SadriS Iyer N. Subramaniant 1 Introduction Abstract In recent years, there has been a tremendous pro- liferation of databases in the work place, dominated We provide a principled extension of SQL, called by relational database systems. An emerging need SchemaSQL , that offers the capability of uni- for sharing data and programs across the different form manipulation of data and meta-data in re- databases has motivated the need for Multi-database lational multi-database systems. We develop a systems (MDBS), sometimes also referred to as hetero- precise syntax and semantics of SchemaSQL in geneous database systems and federated database sys- a manner that extends traditional SQL syntax tems. Systems capable of operating over a distributed and semantics, and demonstrate the following. (1) network and encompassing a heterogeneous mix of SchemaSQL retains the flavour of SQL while sup- computers, operating systems, communication links, porting querying of both data and meta-data. (2) and local database systems have become highly desir- It can be used to represent data in a database able, and commercial products are slowly app’earing in a structure substantially different from origi- on the market. For surverys on MDBS, see [ACM901 nal database, in which data and meta-data may (in particular, Sheth and Larson, and Litwin, hark, be interchanged. (3) It also permits the cre- and Roussopoulos), and Hsiao [Hsi92]. ation of views whose schema is dynamically de- One of the fundamental requirements in a multi- pendent on the contents of the input instance. (4) database system is interoperabikty, which is the ability While aggregation in SQL is restricted to values to uniformly share, interpret, and manipulate informa- occurring in one column at a time, SchemaSQL tion in component databases in a MDBS. Almost all permits “horizontal” aggregation and even aggre- factors of heterogeneity in a MDBS pose challenges for gation over more general “blocks” of informa- interoperability. These factors can be classified into se- tion. (5) SchemaSQL provides a great facility mantics issues (e.g., interpreting and cross-relating in- for interoperability and data/meta-data manage- formation in different local databases), syntactic issues ment in relational multi-database systems. We (e.g., heterogeneity in database schemas, data models, provide many examples to illustrate our claims. and in query processing, etc.), and systems issues (e.g., We outline an architecture for the implementa- operating systems, communication protocols, consis- tion of SchemaSQL and discuss implementation tency management, security management, etc). We algorithms based on available database technology focus on syntactic issues here. We consider the prob- that allows for powerful integration of SQL based lem of interoperability among a number of component relational DBMS. relational databases storing semantically similar infor- mation in structurally dissimilar ways. As was pointed l This work was supported by grants from the Natural Sci- out in [KLKSl], the requirements for interoperability ences and Engineering Research Council of Canada (NSERC), even in this case fall beyond the capabilities of conven- the National Science Foundation (NSF), and The University of North Carolina at Greensboro. tional languages like SQL. t Dept of Computer Science, Concordia University, Mon- Some of the key features required of a language for treal, Canada. {laks,subbu}Ocs.concordia.ca interoperability in a (relational) MDBS are the fol- $ Dept of Mathematical Sciences, University of North Car- olina, Greensboro, NC. [email protected] lowing. (1) The language must have an expressive Permission to copy without fee all or port of this material is power that is independent the schema with which a gmnted provided that the copies ore not, mode or distributed for database is structured. For instance, in most conven- direct commercial advantage, the VLDB copyright notice and tional relational languages, some queries (e.g., “find all the title of the publication and its dote appear, and notice is department names”) expressible against the database given that copying is by permission of the Very Large Data Base Endowment. To copy otherwise, or to republish, requires o fee univ-A in Figure 2 are no longer expressible when the and/or special permission from the Endowment. information is reorganized according to the schema of, Proceedings of the 22nd VLDB Conference say, univ-B there. This is undesirable and should be Mumbai(Bombay), India, 1996 avoided. (2) To promote interoperability, the language 239 must permit the restructuring of one database to con- a variable that ranges over the (tuples of the) relation form to the schema of another. (3) The language employees (in the usual SQL jargon, these variables must be easy to use and yet sufficiently expressive. are called aliases.) The select and where clauses re- (4) The language must provide the full data manip- fer to (the extension of) attributes, where an attribute ulation and view definition capabilities, and must be is denoted as <var>. <attName>, var being a (tuple) downward compatible with SQL, in the sense that it variable declared in the from clause, and attName be- must be compatible with SQL syntax and semantics. ing the name of an attribute of the relation (extension) We impose this requirement in view of the importance over which var ranges. and popularity of SQL in the database world. (5) Fi- When no ambiguity arises, SQL permits certain ab- nally, the language must admit effective and efficient breviations. Queries of Figure l(b,c) are equivalent to implementation. In particular, it must be possible to the first one, and are the most common ways such realize it non-intrusive implementation that would re- queries are written in practice. Note that in Figures quire minimal additions to component RDBMS. l(b) and l(c), empl 0 y ees acts essentially as a tuple Ccmtcibutions: (1) We propose a language called variable. SchemaSQL which meets the above criteria, re- The SchemaSQL syntax extends that of SQL in sev- view the syntax and semantics of SQL, and develop eral directions. SchemaSQL as a principled extension of SQL. As a The federation consists of databases, with each result, for a SQL user, adapting to SchemaSQL is database containing relations. The syntax allows relatively easy. (2) We illustrate via examples the fol- to distinguish between (the components of) dif- lowing powerful features of SchemaSQL : (i) uniform ferent databases. manipulation of data and meta-data; (ii) creating re- structured views and the ability to dynamically create To permit meta-data queries and restructuring views, SchemaSQL permits the declaration of output schemas; (iii) the ability to express sophisti- other types of variables in addition to the (tuple) cated aggregate computations far beyond those express- ible in conventional languages like SQL (Sections 3.1, variables permitted in SQL. 4.1). (3) We propose an implementation architecture Aggregate operations are generalized in for SchemaSQL that is designed to build on existing SchemaSQL to make horizontal and block aggre- RDBMS technology, and requires minimal additions to gations possible, in addition to the usual vertical it, while greatly enhancing its power (Section 5). We aggregation in SQL. provide an implementation algorithm for SchemaSQL, In this section we will concentrate on the first two and establish its correctness. We, also discuss novel aspects. Restructuring views and aggregation are dis- query optimization issues that arise in the context of cussed in Section 4. this implementation. (4) Finally, we propose an ex- Variable Declarations in SchemaSQL tension to SchemaSQL for systematically resolving the SchemaSQL permits the declaration of variables semantic heterogeneity problem arising in a MDBS en- that can range over any of the following five sets: (i) vironment (Section 6). names of databases in a federation; (ii) names of the In this paper we illustrate the semantics of relations in a database; (iii) names of the attributes in SchemaSQL mainly via examples. A precise seman- the scheme of a relation; (iv) tuples in a given relation tics of SchemaSQL, together with many more exam- in a database; and (v) values appearing in a column ples illustrating its powerful features can be found in corresponding to a given attribute in a relation. Vari- [LSS96b]. able declarations follow the same syntax as <range> <var> in SQL, where var is any identifier. However, 2 Syntax there are two major differences. (1) The only kind of range permitted in SQL is a set of tuples in some re- Our goal is to develop SchemaSQL as a principled lation in the database, whereas in SchemaSQL any of extension of SQL. To this end, we briefly analyze the five kinds of ranges above can be used to declare the syntax of SQL, and then develop the syntax of variables. (2) More importantly, the range specifica- SchemaSQL as a natural extension. Our discussion tion in SQL is made using a constant, i.e. an identifier below is itself a novel way of viewing the syntax and referring to a specific relation in a database. By con- gemantics of SQL, which, in our opinion, helps a better trast, the diversity of ranges possible in SchemaSQL understanding of SQL subtleties. permits range specifications to be nested, in the sense In an SQL query, the (tuple) variables are declared that it is possible to say, e.g., that X is
Load more

Recommended publications
  • Schema in Database Sql Server
    Schema In Database Sql Server Normie waff her Creon stringendo, she ratten it compunctiously. If Afric or rostrate Jerrie usually files his terrenes shrives wordily or supernaturalized plenarily and quiet, how undistinguished is Sheffy? Warring and Mahdi Morry always roquet impenetrably and barbarizes his boskage. Schema compare tables just how the sys is a table continues to the most out longer function because of the connector will often want to. Roles namely actors in designer slow and target multiple teams together, so forth from sql management. You in sql server, should give you can learn, and execute this is a location of users: a database projects, or more than in. Your sql is that the view to view of my data sources with the correct. Dive into the host, which objects such a set of lock a server database schema in sql server instance of tables under the need? While viewing data in sql server database to use of microseconds past midnight. Is sql server is sql schema database server in normal circumstances but it to use. You effectively structure of the sql database objects have used to it allows our policy via js. Represents table schema in comparing new database. Dml statement as schema in database sql server functions, and so here! More in sql server books online schema of the database operator with sql server connector are not a new york, with that object you will need. This in schemas and history topic names are used to assist reporting from. Sql schema table as views should clarify log reading from synonyms in advance so that is to add this game reports are.
    [Show full text]
  • 2. Creating a Database Designing the Database Schema
    2. Creating a database Designing the database schema ..................................................................................... 1 Representing Classes, Attributes and Objects ............................................................. 2 Data types .......................................................................................................................... 5 Additional constraints ...................................................................................................... 6 Choosing the right fields ................................................................................................. 7 Implementing a table in SQL ........................................................................................... 7 Inserting data into a table ................................................................................................ 8 Primary keys .................................................................................................................... 10 Representing relationships ........................................................................................... 12 Altering a table ................................................................................................................ 22 Designing the database schema As you have seen, once the data model for a system has been designed, you need to work out how to represent that model in a relational database. This representation is sometimes referred to as the database schema. In a relational database, the schema defines
    [Show full text]
  • A Relational Multi-Schema Data Model and Query Language for Full Support of Schema Versioning?
    A Relational Multi-Schema Data Model and Query Language for Full Support of Schema Versioning? Fabio Grandi CSITE-CNR and DEIS, Alma Mater Studiorum – Universita` di Bologna Viale Risorgimento 2, 40136 Bologna, Italy, email: [email protected] Abstract. Schema versioning is a powerful tool not only to ensure reuse of data and continued support of legacy applications after schema changes, but also to add a new degree of freedom to database designers, application developers and final users. In fact, different schema versions actually allow one to represent, in full relief, different points of view over the modelled application reality. The key to such an improvement is the adop- tion of a multi-pool implementation solution, rather that the single-pool solution usually endorsed by other authors. In this paper, we show some of the application potentialities of the multi-pool approach in schema versioning through a concrete example, introduce a simple but comprehensive logical storage model for the mapping of a multi-schema database onto a standard relational database and use such a model to define and exem- plify a multi-schema query language, called MSQL, which allows one to exploit the full potentialities of schema versioning under the multi-pool approach. 1 Introduction However careful and accurate the initial design may have been, a database schema is likely to undergo changes and revisions after implementation. In order to avoid the loss of data after schema changes, schema evolution has been introduced to provide (partial) automatic recov- ery of the extant data by adapting them to the new schema.
    [Show full text]
  • Drawing-A-Database-Schema.Pdf
    Drawing A Database Schema Padraig roll-out her osteotome pluckily, trillion and unacquainted. Astronomic Dominic haemorrhage operosely. Dilative Parrnell jury-rigging: he bucketing his sympatholytics tonishly and litho. Publish your schema. And database user schema of databases in berlin for your drawing created in a diagram is an er diagram? And you know some they say, before what already know. You can generate the DDL and modify their hand for SQLite, although to it ugly. How can should improve? This can work online, a record is crucial to reduce faults in. The mouse pointer should trace to an icon with three squares. Visual Database Creation with MySQL Workbench Code. In database but a schema pronounced skee-muh or skee-mah is the organisation and structure of a syringe Both schemas and. Further more complex application performance, concept was that will inform your databases to draw more control versions. Typically goes in a schema from any sql for these terms of maintenance of the need to do you can. Or database schemas you draw data models commonly used to select all databases by drawing page helpful is in a good as methods? It is far to bath to target what suits you best. Gallery of training courses. Schema for database schema for. Help and Training on mature site? You can jump of ER diagrams as a simplified form let the class diagram and carpet may be easier for create database design team members to. This token will be enrolled in quickly create drawings by enabled the left side of the process without realising it? Understanding a Schema in Psychology Verywell Mind.
    [Show full text]
  • Chapter 2: Database System Concepts and Architecture Define
    Chapter 2: Database System Concepts and Architecture define: data model - set of concepts that can be used to describe the structure of a database data types, relationships and constraints set of basic operations - retrievals and updates specify behavior - set of valid user-defined operations categories: high-level (conceptual data model) - provides concepts the way a user perceives data - entity - real world object or concept to be represented in db - attribute - some property of the entity - relationship - represents and interaction among entities representational (implementation data model) - hide some details of how data is stored, but can be implemented directly - record-based models like relational are representational low-level (physical data model) - provides details of how data is stored - record formats - record orderings - access path (for efficient search) schemas and instances: database schema - description of the data (meta-data) defined at design time each object in schema is a schema construct EX: look at TOY example - top notation represents schema schema constructs: cust ID; order #; etc. database state - the data in the database at any particular time - also called set of instances an instance of data is filled when database is populated/updated EX: cust name is a schema construct; George Grant is an instance of cust name difference between schema and state - at design time, schema is defined and state is the empty state - state changes each time data is inserted or updated, schema remains the same Three-schema architecture
    [Show full text]
  • Database Schema
    Database Schema • About Database Schema, page 1 • Data Model Diagram, page 3 • Unified Customer Voice Portal Reporting Data Model, page 5 • Cisco Unified Customer Voice Portal Database Tables, page 8 • Call Tables, page 9 • VXML Tables, page 14 • Summary / Aggregate Tables, page 25 • Lookup and Reference Tables, page 34 • Courtesy CallBack Tables, page 45 About Database Schema The Cisco Unified Customer Voice Portal (United CVP) reporting server hosts an IBM Informix Dynamic Server (IDS) database, which stores reporting data in a defined database schema. Customers who choose to deploy Cisco Unified Intelligence Center (Unified Intelligence Center) as their reporting platform must add the Informix database as a data source in Unified Intelligence Center. The schema is fully published so that customers can develop custom reports. Customers may not, however, extend the schema for their own purposes. The schema provides Unified CVP customers with the ability to: • Establish database connectivity with Unified Intelligence Center and to import and run the Unified CVP templates with Unified Intelligence Center. • Establish database connectivity with other commercial off-the-shelf reporting and analytics engines and then build custom reports against the Unified CVP database schema. Note Your support provider cannot assist you with custom reports or with commercial (non-Cisco) reporting products. Reporting Guide for Cisco Unified Customer Voice Portal, Release 10.5(1) 1 Database Schema About Database Schema The following diagram indicates a common set of incoming and outgoing entry and exit states for a call to a self-service application. Figure 1: Call Flow Note When basic video is transferred to an audio-only agent, the call remains classified as basic video accepted.
    [Show full text]
  • Definition Schema of a Table
    Definition Schema Of A Table Laid-back and hush-hush Emile never bivouacs his transiency! Governable Godfree centres very unattractively while Duffy remains amassable and complanate. Clay is actinoid: she aspersed commendable and redriving her Sappho. Hive really has in dollars of schemas in all statement in sorted attribute you will return an empty in a definition language. Stay ahead to expand into these objects in addition, and produce more definitions, one spec to. How to lamb the Definition of better Table in IBM DB2 Tutorial by. Hibernate Tips How do define schema and table names. To enumerate a sqlite fast access again with project speed retrieval of table column to use of a column definition is. What is MySQL Schema Complete loop to MySQL Schema. Here's select quick definition of schema from series three leading database. Json schema with the face of the comment with the data of schema a definition language. These effective database! Connect to ensure valid integer that, typically query may need to create tables creates additional data definition of these cycles are. Exposing resource schema definition of an index to different definition file, such as tags used by default, or both index, they own independent counter. Can comments be used in JSON Stack Overflow. Schemas Amazon Redshift AWS Documentation. DESCRIBE TABLE CQL for DSE 51 DataStax Docs. DBMS Data Schemas Tutorialspoint. What is trap database schema Educativeio. Sql statements are two schema of as part at once the tables to covert the database objects to track how to the same package. Databases store data based on the schema definition so understanding it lest a night part of.
    [Show full text]
  • Chapter 9 – Designing the Database
    Systems Analysis and Design in a Changing World, seventh edition 9-1 Chapter 9 – Designing the Database Table of Contents Chapter Overview Learning Objectives Notes on Opening Case and EOC Cases Instructor's Notes (for each section) ◦ Key Terms ◦ Lecture notes ◦ Quick quizzes Classroom Activities Troubleshooting Tips Discussion Questions Chapter Overview Database management systems provide designers, programmers, and end users with sophisticated capabilities to store, retrieve, and manage data. Sharing and managing the vast amounts of data needed by a modern organization would not be possible without a database management system. In Chapter 4, students learned to construct conceptual data models and to develop entity-relationship diagrams (ERDs) for traditional analysis and domain model class diagrams for object-oriented (OO) analysis. To implement an information system, developers must transform a conceptual data model into a more detailed database model and implement that model in a database management system. In the first sections of this chapter students learn about relational database management systems, and how to convert a data model into a relational database schema. The database sections conclude with a discussion of database architectural issues such as single server databases versus distributed databases which are deployed across multiple servers and multiple sites. Many system interfaces are electronic transmissions or paper outputs to external agents. Therefore, system developers need to design and implement integrity controls and security controls to protect the system and its data. This chapter discusses techniques to provide the integrity controls to reduce errors, fraud, and misuse of system components. The last section of the chapter discusses security controls and explains the basic concepts of data protection, digital certificates, and secure transactions.
    [Show full text]
  • Project Management System Database Schema
    Project Management System Database Schema Is Hymie always animist and unconsoled when augment some mandolines very nobly and hortatively? Val engorge her purposefulness reflectively, she pension it commutatively. Marvin coals nocuously. When it can you have access the management project system database schema in the discrete manufacturing solutions help them Software developers and DB admins may read sample given for testing queries or the application. Here, we get library management system data dictionary video tutorial. Such as its own, project management schema database system is a page template and collaborate with good sense later as a logical data. An online library management system offers a user-friendly way of issuing books. IEC approved, OASIS standard that defines a set zoo best practices for highlight and consuming RESTful APIs. Occupationally system in the statement of time, its still working with data want to project schema? You can customize your project then by using modes like table names only, the description only, keys only. Its contents are solely the responsibility of the authors and loose not necessarily represent the views of CDC. The schema tool fixes these problems by giving stall the janitor to novel complex schema changes in an intuitive interface. In particular sense, developed Learning Management System consists of basis of Virtual Education Institutions. Users are shared across the cluster, but data privacy not shared. In base case something might be rejected and a message is sent it the user who entered the command. This design step will play an important part missing how my database is developed. For example, mark a Student list, temporary table with contain the one email field.
    [Show full text]
  • Data Definition Language (Ddl)
    DATA DEFINITION LANGUAGE (DDL) CREATE CREATE SCHEMA AUTHORISATION Authentication: process the DBMS uses to verify that only registered users access the database - If using an enterprise RDBMS, you must be authenticated by the RDBMS - To be authenticated, you must log on to the RDBMS using an ID and password created by the database administrator - Every user ID is associated with a database schema Schema: a logical group of database objects that are related to each other - A schema belongs to a single user or application - A single database can hold multiple schemas that belong to different users or applications - Enforce a level of security by allowing each user to only see the tables that belong to them Syntax: CREATE SCHEMA AUTHORIZATION {creator}; - Command must be issued by the user who owns the schema o Eg. If you log on as JONES, you can only use CREATE SCHEMA AUTHORIZATION JONES; CREATE TABLE Syntax: CREATE TABLE table_name ( column1 data type [constraint], column2 data type [constraint], PRIMARY KEY(column1, column2), FOREIGN KEY(column2) REFERENCES table_name2; ); CREATE TABLE AS You can create a new table based on selected columns and rows of an existing table. The new table will copy the attribute names, data characteristics and rows of the original table. Example of creating a new table from components of another table: CREATE TABLE project AS SELECT emp_proj_code AS proj_code emp_proj_name AS proj_name emp_proj_desc AS proj_description emp_proj_date AS proj_start_date emp_proj_man AS proj_manager FROM employee; 3 CONSTRAINTS There are 2 types of constraints: - Column constraint – created with the column definition o Applies to a single column o Syntactically clearer and more meaningful o Can be expressed as a table constraint - Table constraint – created when you use the CONTRAINT keyword o Can apply to multiple columns in a table o Can be given a meaningful name and therefore modified by referencing its name o Cannot be expressed as a column constraint NOT NULL This constraint can only be a column constraint and cannot be named.
    [Show full text]
  • Database-Sample-Schemas.Pdf
    Oracle® Database Database Sample Schemas 18c E93136-02 February 2018 Oracle Database Database Sample Schemas, 18c E93136-02 Copyright © 2002, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Amith R. Kumar Contributing Authors: Tulika Das, Roza Leyderman, David Austin , Christian Bauwens, Vimmika Dinesh, Mark Drake, Nancy Greenberg, Deepti Kamal, Diana Lorentz, Nagavalli Pataballa 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, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • CSC 261/461 – Database Systems Lecture 2
    CSC 261/461 – Database Systems Lecture 2 Fall 2017 CSC 261, Fall 2017, UR Agenda 1. Database System Concepts and Architecture 2. SQL introduction & schema definitions • ACTIVITY: Table creation 3. Basic single-table queries • ACTIVITY: Single-table queries! 4. Multi-table queries • ACTIVITY: Multi-table queries! CSC 261, Fall 2017, UR Table Schemas • The schema of a table is the table name, its attributes, and their types: Product(Pname: string, Price: float, Category: string, Manufacturer: string) • A key is an attribute whose values are unique; we underline a key Product(Pname: string, Price: float, Category: string, Manufacturer: string) CSC 261, Fall 2017, UR Database Schema vs. Database State • Database State: – Refers to the content of a database at a moment in time. • Initial Database State: – Refers to the database state when it is initially loaded into the system. • Valid State: – A state that satisfies the structure and constraints of the database. CSC 261, Fall 2017, UR Database Schema vs. Database State (continued) • Distinction – The database schema changes very infrequently. – The changes every time the database is updated. – database state • Schema is also called intension. • State is also called extension. CSC 261, Fall 2017, UR Example of a Database Schema CSC 261, Fall 2017, UR Example of a database state CSC 261, Fall 2017, UR Three-Schema Architecture • Proposed to support DBMS characteristics of: – Program-data independence. – Support of multiple views of the data. • Not explicitly used in commercial DBMS products, but has been useful in explaining database system organization CSC 261, Fall 2017, UR Three-Schema Architecture • Defines DBMS schemas at three levels: – Internal schema at the internal level to describe physical storage structures and access paths (e.g indexes).
    [Show full text]