DOCSLIB.ORG

Thesis Title

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Thesis Title Otto-von-Guericke-Universit¨atMagdeburg School of Computer Science Department of Technical and Business Information Systems Master Thesis Feature-Oriented Decomposition of SQL:2003 Author: Sunkle Sagar October 24, 2007 Advisor: Prof. Dr. rer. nat. habil. Gunter Saake, Dipl.-Inform. Marko Rosenm¨uller, Dipl.-Inform. Martin Kuhlemann University of Magdeburg School of Computer Science Department of Technical and Business Information Systems P.O. Box 4120, D{39016 Magdeburg Germany Sunkle, Sagar: Feature-Oriented Decomposition of SQL:2003 Master Thesis, Otto-von-Guericke-Universit¨at Magdeburg, 2007. i Acknowledgements I would like to thank my master thesis advisors for their support and reviews. I would like to thank Prof. Dr. Gunter Saake for his support and confidence in me and allowing me to work on master thesis in his group. I would like to thank Marko Rosenm¨uller, Martin Kuhlemann and Norbert Siegmund for their helpful reviews and suggestions. Marko and Martin reviewed this thesis for smallest details. I would like to especially thank Marko, he was specifically assigned to me for the thesis and without our lengthy and very interesting discussions about various related topics where he tried patiently to answer my innumerable queries orally or by emails, this thesis would not have been possible. Finally I would like to thank my family because of whom this education is made possible for me. ii CONTENTS iii Contents Contents iii List of Figures vii List of Tables ix List of Abbreviations x 1 Introduction 1 1.1 Motivation . .1 1.2 Goals . .4 1.3 Structure of the Thesis . .4 2 Background 5 2.1 SQL . .5 2.1.1 History . .5 2.1.2 Standardization and Evolution . .6 2.2 Software Product Line Concepts . .7 2.2.1 Software Product Line Engineering . .7 2.2.2 Domain Engineering . .8 2.2.3 Application Engineering . 10 2.3 Feature-Oriented Decomposition . 11 2.3.1 Features . 11 2.3.2 Feature Diagrams . 11 2.4 Feature-Oriented Programming . 17 2.4.1 GenVoca . 17 2.4.2 AHEAD . 18 iv CONTENTS 2.4.3 Using GenVoca/AHEAD and Related Tools . 19 2.5 Separation of Concerns . 20 2.6 Summary . 23 3 Feature-Oriented Decomposition of SQL:2003 24 3.1 Feature Modeling Technique for SQL:2003 . 24 3.1.1 Basis for Modeling Features in SQL:2003 . 25 3.2 Feature Diagrams for SQL:2003 . 28 3.3 Sub-grammars Based on Feature Diagrams . 36 3.4 Summary . 41 4 Issues in Feature-Oriented Decomposition of SQL:2003 42 4.1 Other Implementation Models . 42 4.1.1 Superimposed Variants . 42 4.1.2 Hyperspaces . 43 4.1.3 Comparison of Different Implementation Models . 45 4.2 SQL:2003 Specific Issues . 45 4.3 Related Work . 50 4.4 Summary . 52 5 Conclusion 53 5.1 Further Work . 54 Bibliography 56 Appendices A SQL:2003 Feature Diagrams 61 B Taxonomy of SQL Non-Framework Optional Fearures 86 B.1 Java Routines and Types Using the Java Programming Language (SQL/JRT) . 87 B.2 SQL Object Language Bindings (SQL/OLB) . 87 B.3 SQL Persistent Stored Modules (SQL/PSM) . 87 B.4 SQL Management of External Data (SQL/MED) . 88 B.5 SQL XML-Related Specifications (SQL/XML) . 88 CONTENTS v C SQL Platform Support 91 vi CONTENTS LIST OF FIGURES vii List of Figures 2.1 Structure of the SEI Framework for Product Line Practice [CE00] . .8 2.2 Domain Engineering and Application Engineering as parallel processes [CE00] . 10 2.3 Feature Diagram with a concept node and three features. 12 2.4 Feature Diagram with mandatory and optional features. 13 2.5 Alternative and OR features. 13 2.6 AND features. 14 3.1 Parent child relationships in feature diagrams as grammar rules [Bat05]. 26 3.2 Main Feature Diagram of SQL:2003 . 28 3.3 Domain Definition Feature Diagram . 29 3.4 Table Definition Feature Diagram . 30 3.5 View Definition Feature Diagram . 31 3.6 Schema Routine Feature Diagram . 32 3.7 Insert statement Feature Diagram . 33 3.8 Merge statement Feature Diagram . 33 3.9 Query Expression Feature Diagram . 34 3.10 Query Specification Feature Diagram . 35 3.11 Table Expression Feature Diagram . 35 4.1 Overview of Superimposed Variants Approach [CA05] . 43 4.2 Hyperspace matrix with two relevant dimensions; Classes and Features [PRB03] . 44 A.1 SQL/Foundation Feature Diagram . 61 A.2 SQL schema statement Feature Diagram . 62 viii LIST OF FIGURES A.3 Schema Definition Feature Diagram . 63 A.4 Column Definition Feature Diagram . 64 A.5 Sequence Generator Feature Diagram . 65 A.6 Trigger Definition Feature Diagram . 66 A.7 User-Defined Type Definition Feature Diagram . 67 A.8 Grant Privilege Feature Diagram . 68 A.9 Privilege Feature Diagram . 68 A.10 Alter Statements Feature Diagram . 69 A.11 SQL Data Statements Feature Diagram . 70 A.12 Cursor Feature Diagram . 71 A.13 SQL Data Change Statements Feature Diagram . 71 A.14 Delete statement Feature Diagram . 72 A.15 Update statement Feature Diagram . 72 A.16 SQL Transaction statements Feature Diagram . 73 A.17 SQL Control statements Feature Diagram . 74 A.18 SQL Connection statements Feature Diagram . 74 A.19 SQL Session statements Feature Diagram . 75 A.20 SQL Dynamic Statements Feature Diagram . 76 A.21 SQL Diagnostic Statements Feature Diagram . 76 A.22 Scalar Expressions Feature Diagram . 77 A.23 Data Type Feature Diagram . 78 A.24 Window Function Feature Diagram . 79 A.25 Function Specification Feature Diagram . 80 A.26 Search Cycle Clause Feature Diagram . 81 A.27 Table Reference Feature Diagram . 82 A.28 Group By Clause Feature Diagram . 83 A.29 Window Clause Feature Diagram . 84 A.30 Predicate Feature Diagram . 85 LIST OF TABLES ix List of Tables B.1 Number of Features enlisted in the SQL:2003 Specification Draft . 86 B.2 SQL/JRT features . 87 B.3 SQL/OLB features . 87 B.4 SQL/PSM features . 88 B.5 SQL/MED features . 89 B.6 SQL/XML features . 90 C.1 SQL Platform Support -1 . 91 C.2 SQL Platform Support -2 . 92 x List of Abbreviations AHEAD Algebraic Hierarchical Equations for Application Design BNF Backus Naur form CLI Call Level Interface DSL Domain Specific Language FOD Feature-Oriented Decomposition FODA Feature-Oriented Domain Analysis FOP Feature-Oriented Programming FOR Feature-Oriented Refactoring FOSD Feature-Oriented Software Development JTS Jakarta Tool Suite JRT Routines and Types for Java Programming Language MED Management of External Data MBSE Model Based Software Engineering OLB Object Level Bindings PSM Persistent Stored Modules SPL Software Product Line SPLE Software Production Line Engineering SQL Structured Query Language Chapter 1. Introduction 1 Chapter 1 Introduction 1.1 Motivation Databases have come up a long way since Codd's concept of relational data model in 1970, now posed as the most vital component in the status quo of information technology. Database technology is at the core of multitude of software applications such as business transaction applications of varying size, digital libraries, web applications like online banking and online shopping, scientific projects like the human genome mapping project and NASA's earth observation system, Enterprise Resource Planning (ERP) systems, data warehouses, business intelligence applications like data mining and Online Analytical Processing (OLAP), embedded systems for personal information management, etc. The basic structure of databases has evolved from the relational model to encompass other conceptual models like entity relationship model, object relation model, object role model1, etc. Databases are available now also in the form of semi structured databases, object-oriented databases, multi-dimensional databases, distributed and parallel databases, etc. It can be argued that database technology will continue to evolve at an alarming rate as it makes foray into new domains with new domain specific techniques being invented and merged into current database technology. It has been observed that most popular database vendors tend to provide bits and pieces of support to every other kind of database functionality, be it indexes or XML support or special kinds of queries, etc [CW00]. Many small database vendors, which are large in number, cater only to a specific type of database technology, but large companies inevitably offer a jumble of features packed in one product. In a way, features of database products have been treated as a sales and marketing issue by big players without much consideration to how bloated such a product becomes for simplest of database applications. Every new release of the database product comes with the tag `Feature Rich', claiming to be better than competitors. Ironically, any enterprise of modest size makes use of only a tiny bit of mam- moth functionality provided by database products. This tends to be low-end features [CW00]. Most of the high-end features are rarely or never used. On one hand, it's good to have a large array of features that could give enhanced performance and 1http://www.orm.net/ 2 1.1. Motivation other advantages, on the other hand one can also say that database products are overloaded with features [CW00]. Database vendors have `learned' to adopt a one size fits all approach and maintain a single code line with all database management services they provide, reasons for which Stonebraker et al. [SC05] identify as maintenance and compatibility cost of code base and sales and marketing problems. They conclude that this is no more applicable and that \the commercial world (of databases) will fracture into a collection of independent database engines, some of which may be unified by a common front-end parser". Like databases which are getting caught in the universality trap [CW00], the structured query language (SQL) which is the basis for interaction between database technology and its user, has grown enormously.
Load more

Recommended publications
  • Support Aggregate Analytic Window Function Over Large Data by Spilling
    Support Aggregate Analytic Window Function over Large Data by Spilling Xing Shi and Chao Wang Guangdong University of Technology, Guangzhou, Guangdong 510006, China North China University of Technology, Beijing 100144, China Abstract. ​Analytic function, also called window function, is to query the aggregation of data over a sliding window. For example, a simple query over the online stock platform is to return the average price of a stock of the last three days. These functions are commonly used features in SQL databases. They are supported in most of the commercial databases. With the increasing usage of cloud data infra and machine learning technology, the frequency of queries with analytic window functions rises. Some analytic functions only require const space in memory to store the state, such as SUM, AVG, while others require linear space, such as MIN, MAX. When the window is extremely large, the memory space to store the state may be too large. In this case, we need to spill the state to disk, which is a heavy operation. In this paper, we proposed an algorithm to manipulate the state data in the disk to reduce the disk I/O to make spill available and efficiency. We analyze the complexity of the algorithm with different data distribution. 1. Introducion In this paper, we develop novel spill techniques for analytic window function in SQL databases. And discuss different various types of aggregate queries, e.g., COUNT, AVG, SUM, MAX, MIN, etc., over a relational table. Aggregate ​analytic function, also called aggregate window function, is to query the aggregation of data over a sliding window.
    [Show full text]
  • A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon
    A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon To cite this version: Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon. A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine. DEXA’2014 (Database and Expert System Applications), Sep 2014, Munich, Germany. pp.433-440. hal-00993260 HAL Id: hal-00993260 https://hal.archives-ouvertes.fr/hal-00993260 Submitted on 28 Oct 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Fr´ed´ericDumonceaux, Guillaume Raschia, and Marc Gelgon LINA (UMR CNRS 6241), Universit´ede Nantes, France [email protected] Abstract. Partitions are a very common and useful way of organiz- ing data, in data engineering and data mining. However, partitions cur- rently lack efficient and generic data management functionalities. This paper proposes advances in the understanding of this problem, as well as elements for solving it. We formulate the task as efficient process- ing, evaluating and optimizing queries over set partitions, in the setting of relational databases.
    [Show full text]
  • Look out the Window Functions and Free Your SQL
    Concepts Syntax Other Look Out The Window Functions and free your SQL Gianni Ciolli 2ndQuadrant Italia PostgreSQL Conference Europe 2011 October 18-21, Amsterdam Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Outline 1 Concepts Aggregates Different aggregations Partitions Window frames 2 Syntax Frames from 9.0 Frames in 8.4 3 Other A larger example Question time Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Aggregates Aggregates 1 Example of an aggregate Problem 1 How many rows there are in table a? Solution SELECT count(*) FROM a; • Here count is an aggregate function (SQL keyword AGGREGATE). Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Aggregates Aggregates 2 Functions and Aggregates • FUNCTIONs: • input: one row • output: either one row or a set of rows: • AGGREGATEs: • input: a set of rows • output: one row Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Different aggregations Different aggregations 1 Without window functions, and with them GROUP BY col1, . , coln window functions any supported only PostgreSQL PostgreSQL version version 8.4+ compute aggregates compute aggregates via by creating groups partitions and window frames output is one row output is one row for each group for each input row Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Different aggregations Different aggregations 2 Without window functions, and with them GROUP BY col1, . , coln window functions only one way of aggregating different rows in the same for each group
    [Show full text]
  • Lecture 3: Advanced SQL
    Advanced SQL Lecture 3: Advanced SQL 1 / 64 Advanced SQL Relational Language Relational Language • User only needs to specify the answer that they want, not how to compute it. • The DBMS is responsible for efficient evaluation of the query. I Query optimizer: re-orders operations and generates query plan 2 / 64 Advanced SQL Relational Language SQL History • Originally “SEQUEL" from IBM’s System R prototype. I Structured English Query Language I Adopted by Oracle in the 1970s. I IBM releases DB2 in 1983. I ANSI Standard in 1986. ISO in 1987 I Structured Query Language 3 / 64 Advanced SQL Relational Language SQL History • Current standard is SQL:2016 I SQL:2016 −! JSON, Polymorphic tables I SQL:2011 −! Temporal DBs, Pipelined DML I SQL:2008 −! TRUNCATE, Fancy sorting I SQL:2003 −! XML, windows, sequences, auto-gen IDs. I SQL:1999 −! Regex, triggers, OO • Most DBMSs at least support SQL-92 • Comparison of different SQL implementations 4 / 64 Advanced SQL Relational Language Relational Language • Data Manipulation Language (DML) • Data Definition Language (DDL) • Data Control Language (DCL) • Also includes: I View definition I Integrity & Referential Constraints I Transactions • Important: SQL is based on bag semantics (duplicates) not set semantics (no duplicates). 5 / 64 Advanced SQL Relational Language Today’s Agenda • Aggregations + Group By • String / Date / Time Operations • Output Control + Redirection • Nested Queries • Join • Common Table Expressions • Window Functions 6 / 64 Advanced SQL Relational Language Example Database SQL Fiddle: Link sid name login age gpa sid cid grade 1 Maria maria@cs 19 3.8 1 1 B students 2 Rahul rahul@cs 22 3.5 enrolled 1 2 A 3 Shiyi shiyi@cs 26 3.7 2 3 B 4 Peter peter@ece 35 3.8 4 2 C cid name 1 Computer Architecture courses 2 Machine Learning 3 Database Systems 4 Programming Languages 7 / 64 Advanced SQL Aggregates Aggregates • Functions that return a single value from a bag of tuples: I AVG(col)−! Return the average col value.
    [Show full text]
  • Sql Server to Aurora Postgresql Migration Playbook
    Microsoft SQL Server To Amazon Aurora with Post- greSQL Compatibility Migration Playbook 1.0 Preliminary September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 9 Tables of Feature Compatibility 12 AWS Schema and Data Migration Tools 20 AWS Schema Conversion Tool (SCT) 21 Overview 21 Migrating a Database 21 SCT Action Code Index 31 Creating Tables 32 Data Types 32 Collations 33 PIVOT and UNPIVOT 33 TOP and FETCH 34 Cursors 34 Flow Control 35 Transaction Isolation 35 Stored Procedures 36 Triggers 36 MERGE 37 Query hints and plan guides 37 Full Text Search 38 Indexes 38 Partitioning 39 Backup 40 SQL Server Mail 40 SQL Server Agent 41 Service Broker 41 XML 42 Constraints
    [Show full text]
  • Firebird 3 Windowing Functions
    Firebird 3 Windowing Functions Firebird 3 Windowing Functions Author: Philippe Makowski IBPhoenix Email: pmakowski@ibphoenix Licence: Public Documentation License Date: 2011-11-22 Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions What are Windowing Functions? • Similar to classical aggregates but does more! • Provides access to set of rows from the current row • Introduced SQL:2003 and more detail in SQL:2008 • Supported by PostgreSQL, Oracle, SQL Server, Sybase and DB2 • Used in OLAP mainly but also useful in OLTP • Analysis and reporting by rankings, cumulative aggregates Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions Windowed Table Functions • Windowed table function • operates on a window of a table • returns a value for every row in that window • the value is calculated by taking into consideration values from the set of rows in that window • 8 new windowed table functions • In addition, old aggregate functions can also be used as windowed table functions • Allows calculation of moving and cumulative aggregate values. Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions A Window • Represents set of rows that is used to compute additionnal attributes • Based on three main concepts • partition • specified by PARTITION BY clause in OVER() • Allows to subdivide the table, much like GROUP BY clause • Without a PARTITION BY clause, the whole table is in a single partition • order • defines an order with a partition • may contain multiple order items • Each item includes
    [Show full text]
  • Going OVER and Above with SQL
    Going OVER and Above with SQL Tamar E. Granor Tomorrow's Solutions, LLC Voice: 215-635-1958 Email: [email protected] The SQL 2003 standard introduced the OVER keyword that lets you apply a function to a set of records. Introduced in SQL Server 2005, this capability was extended in SQL Server 2012. The functions allow you to rank records, aggregate them in a variety of ways, put data from multiple records into a single result record, and compute and use percentiles. The set of problems they solve range from removing exact duplicates to computing running totals and moving averages to comparing data from different periods to removing outliers. In this session, we'll look at the OVER operator and the many functions you can use with it. We'll look at a variety of problems that can be solved using OVER. Going OVER and Above with SQL Over the last couple of years, I’ve been exploring aspects of SQL Server’s T-SQL implementation that aren’t included in VFP’s SQL sub-language. I first noticed the OVER keyword as an easy way to solve a problem that’s fairly complex with VFP’s SQL, getting the top N records in each of a set of groups with a single query. At the time, I noticed that OVER had other uses, but I didn’t stop to explore them. When I finally returned to see what else OVER could do, I was blown away. In recent versions of SQL Server (2012 and later), OVER provides ways to compute running totals and moving averages, to put data from several records of the same table into a single result record, to divide records into percentile groups and more.
    [Show full text]
  • Efficient Processing of Window Functions in Analytical SQL Queries
    Efficient Processing of Window Functions in Analytical SQL Queries Viktor Leis Kan Kundhikanjana Technische Universitat¨ Munchen¨ Technische Universitat¨ Munchen¨ [email protected] [email protected] Alfons Kemper Thomas Neumann Technische Universitat¨ Munchen¨ Technische Universitat¨ Munchen¨ [email protected] [email protected] ABSTRACT select location, time, value, abs(value- (avg(value) over w))/(stddev(value) over w) Window functions, also known as analytic OLAP functions, have from measurement been part of the SQL standard for more than a decade and are now a window w as ( widely-used feature. Window functions allow to elegantly express partition by location many useful query types including time series analysis, ranking, order by time percentiles, moving averages, and cumulative sums. Formulating range between 5 preceding and 5 following) such queries in plain SQL-92 is usually both cumbersome and in- efficient. The query normalizes each measurement by subtracting the aver- Despite being supported by all major database systems, there age and dividing by the standard deviation. Both aggregates are have been few publications that describe how to implement an effi- computed over a window of 5 time units around the time of the cient relational window operator. This work aims at filling this gap measurement and at the same location. Without window functions, by presenting an efficient and general algorithm for the window it is possible to state the query as follows: operator. Our algorithm is optimized for high-performance main- memory database systems and has excellent performance on mod- select location, time, value, abs(value- ern multi-core CPUs. We show how to fully parallelize all phases (select avg(value) of the operator in order to effectively scale for arbitrary input dis- from measurement m2 tributions.
    [Show full text]
  • Data Warehouse Service
    Data Warehouse Service SQL Error Code Reference Issue 03 Date 2018-08-02 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: http://www.huawei.com Email: [email protected] Issue 03 (2018-08-02) Huawei Proprietary and Confidential i Copyright
    [Show full text]
  • Sql Server to Aurora Mysql Migration Playbook
    Microsoft SQL Server To Amazon Aurora with MySQL Compatibility Migration Playbook Version 1.8, September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 8 Tables of Feature Compatibility 11 AWS Schema and Data Migration Tools 23 AWS Schema Conversion Tool (SCT) 24 SCT Action Code Index 38 AWS Database Migration Service (DMS) 54 ANSI SQL 57 Migrate from SQL Server Constraints 58 Migrate to Aurora MySQL Constraints 62 Migrate from SQL Server Creating Tables 67 Migrate to Aurora MySQL Creating Tables 71 Migrate from SQL Server Common Table Expressions 77 Migrate to Aurora MySQL Common Table Expressions 80 Migrate from SQL Server Data Types 84 Migrate to Aurora MySQL Data
    [Show full text]
  • Microsoft® SQL Server ® 2012 T-SQL Fundamentals
    Microsoft ® SQL Server ® 2012 T-SQL Fundamentals Itzik Ben-Gan Published with the authorization of Microsoft Corporation by: O’Reilly Media, Inc. 1005 Gravenstein Highway North Sebastopol, California 95472 Copyright © 2012 by Itzik Ben-Gan All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. ISBN: 978-0-735-65814-1 1 2 3 4 5 6 7 8 9 M 7 6 5 4 3 2 Printed and bound in the United States of America. Microsoft Press books are available through booksellers and distributors worldwide. If you need support related to this book, email Microsoft Press Book Support at [email protected]. Please tell us what you think of this book at http://www.microsoft.com/learning/booksurvey. Microsoft and the trademarks listed at http://www.microsoft.com/about/legal/en/us/IntellectualProperty/ Trademarks/EN-US.aspx are trademarks of the Microsoft group of companies. All other marks are property of their respective owners. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. This book expresses the author’s views and opinions. The information contained in this book is provided without any express, statutory, or implied warranties. Neither the author, O’Reilly Media, Inc., Microsoft Corporation, nor its resellers, or distributors will be held liable for any damages caused or alleged to be caused either directly or indirectly by this book.
    [Show full text]
  • T-SQL Querying
    T-SQL Querying Itzik Ben-Gan Dejan Sarka Adam Machanic Kevin Farlee PUBLISHED BY Microsoft Press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2015 by Itzik Ben-Gan, Dejan Sarka, Adam Machanic, and Kevin Farlee. All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of Congress Control Number: 2014951866 ISBN: 978-0-7356-8504-8 Printed and bound in the United States of America. First Printing Microsoft Press books are available through booksellers and distributors worldwide. If you need support related to this book, email Microsoft Press Support at [email protected]. Please tell us what you think of this book at http://aka.ms/tellpress. This book is provided “as-is” and expresses the authors’ views and opinions. The views, opinions, and information expressed in this book, including URL and other Internet website references, may change without notice. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. Microsoft and the trademarks listed at http://www.microsoft.com on the “Trademarks” webpage are trademarks of the Microsoft group of companies. All other marks are the property of their respective owners. Acquisitions Editor: Devon Musgrave Developmental Editor: Devon Musgrave Project Editor: Carol Dillingham Editorial Production: Curtis Philips, Publishing.com Technical Reviewer: Alejandro Mesa; Technical Review services provided by Content Master, a member of CM Group, Ltd. Copyeditor: Roger LeBlanc Proofreader: Andrea Fox Indexer: William P.
    [Show full text]