CSC309 Tutorial: SQL

Total Page:16

File Type:pdf, Size:1020Kb

CSC309 Tutorial: SQL CSC309 Tutorial: SQL TA: Lei Jiang March 24, 2003 Outline § SQL: Overview § SQL: Data Definition Language § SQL: Queries § The Pointbase Database SQL: Overview § SQL (Structured Query Language) • is a standard language for RDBMS. • allows user to create new and modify existing databases • allows user to pose complex queries to the database and retrieve data § Some common RDBMS that support SQL: Oracle, Sybase, MS SQL Server, Access, IBM DB2, etc. § In this course, we use the Pointbase database. http://www.pointbase.com SQl: Data Definition Language § Use SQL DDL to create or delete tables. We can also define indexes (keys), specify links between tables, and impose constraints between database tables. The most important DDL statements in SQL are: CREATE TABLE -creates a new database table ALTER TABLE -alters (changes) a database table DROP TABLE -deletes a database table CREATE INDEX -creates an index (search key) DROP INDEX-deletes an index SQL: CREATE § Create a table: Syntax: CREATE TABLE tbl_name( col1 data_type,col2 data_type, ... ) Example: CREATE TABLE employee ( ID int, Name varchar(30), Title varchar(20), Dept varchar(20), Salary decimal(10,2) ) Data types: may vary from system to system Data Type Description integer(size) Hold integers only. The maximum number of digits are specified in int(size) parenthesis. smallint(size) tinyint(size) decimal(size,d) Hold numbers with fractions. The maximum number of digits are numeric(size,d) specified in "size". The maximum number of digits to the right of the decimal is specified in "d". char(size) Holds a fixed length string (can contain letters, numbers, and special characters). The fixed size is specified in parenthesis. varchar(size) Holds a variable length string (can contain letters, numbers, and special characters). The maximum size is specified in parenthesis. date(yyyymmdd) Holds a date SQL: DROP, ALTER § Alter a table (Add/Delete Columns) Syntax: ALTER TABLE table_name ADD column_name datatype Example: ALTER TABLE employee ADD Address varchar Syntax: ALTER TABLE table_name DROP COLUMN column_name Note: Some systems may not support dropping columns of a table § Destroy a table DROP TABLE table_name SQL: INSERT § Insert data to the table insert an entire row Example: INSERT INTO employee VALUES (111, ‘John’, ‘programmer’, ‘testing’, 50000.0) insert data to only specific columns Example: INSERT INTO employee (id, name, title) VALUES (211, ‘Tom’, ‘manager’) ID NAME TITLE DEPT SALARY 111 Johnprogrammer testing 50000.00 211 Tommanager-- SQL: UPDATE, DELETE § Update the table with new data Syntax: UPDATE table_name SET column_name = new_value WHERE column_name = some_value Example: UPDATE employee SET salary=60000.0 WHERE name=‘John’ § Delete data from the table Syntax:DELETE FROM table_name WHERE column_name =some_value Example: DELETE FROM employee WHERE name=‘Tom’ SQL: SELECT SELECT [ALL | DISTINCT] column1[,column2] FROM table1[,table2] [WHERE "conditions"] [GROUP BY "column-list"] [HAVING "conditions] [ORDER BY "column-list" [ASC | DESC] ] Example: comparison operators SELECT * = Equal FROM employee > Greater than WHERE salary>50000.0 < Less than >= Greater than or equal to SELECT * <= Less than or equal to FROM employee <> or != Not equal to WHERE Name LIKE ‘jo%’ LIKE String comparison test SQL: Aggregation Operators MIN returns the smallest value in a given column MAX returns the largest value in a given column SUM returns the sum of the numeric values in a given column AVG returns the average value of a given column COUNT returns the total number of values in a given column COUNT(*) returns the number of rows in a table n SELECT AVG(salary) FROM employee WHERE title = 'Programmer‘ n SELECT COUNT(*) FROM employee SQL: GROUP BY The GROUP BY clause will gather all of the rows together that contain data in the specified column(s) and will allow aggregate functions tobe performed on the one or more columns. SELECT dept, MIN(salary) AS MINIMUM FROM employee GROUP BY dept Original table: Result: NAME TITLE DEPT__SALARY___ DEPT MINIMUM Johnprogmer150000.00 1 40000.00 Tommanager280000.00 2 80000.00 Bobprogmer 140000.00 330000.00 David tester330000.00 SQL: HAVING The HAVING clause allows you to specify conditions on the rows for each group -in other words, which rows should be selected will be based on the conditions you specify. The HAVING clause should follow the GROUP BY clause. SELECT dept, MIN(salary) AS MIN_SALARY FROM employee GROUP BY dept HAVING MIN(salary)>=40000.0 Original table: Result: NAME TITLE DEPT__SALARY___ DEPT MIN_SALARY Johnprogmer150000.00 1 40000.00 Tommanager280000.00 2 80000.00 Bobprogmer 140000.00 David tester330000.00 SQL: ORDER BY ORDER BY allows you to display the results of your query in a sorted order (either ascending order (ASC) or descending order (DESC) based on the columns that you specify to order by. Default is by ASC. SELECT dept, MIN(salary) AS MIN_SALARY FROM employee GROUP BY dept HAVING MIN(salary)>=40000.0 ORDER BY dept DESC Original table: Result: NAME TITLE DEPT__SALARY___ DEPT MINAGE Johnprogmer150000.00 2 80000.00 Tommanager280000.00 140000.00 Bobprogmer 140000.00 David tester330000.00 SQL: Boolean Operators The AND operator can be used to join two or more conditions in the WHERE clause. Both sides of the AND condition must be true in order for the condition to be met and for those rows to be displayed. SELECT * FROM employee WHERE salary>=50000 AND title=‘programmer’ The OR operator can be used to join two or more conditions in the WHERE clause also. However, either side of the OR operator can be true and the condition will be met SELECT * FROM employee WHERE title=‘tester’ OR title=‘programmer’ SQL: IN, BETWEEN The IN conditional operator is a set membership test operator. It is used to test whether or not a value (stated before the keyword IN) is"in" the list of values provided after the keyword IN. SELECT * FROM employee WHERE name IN (‘John', 'Roberts', 'Ruiz'); The BETWEEN conditional operator is used to test whether or not a value (stated before the keyword BETWEEN) is "between" the two values stated after the keyword BETWEEN. SELECT * FROM employee WHERE salary BETWEEN 40000 AND 60000; SQL: Table Join Queries involve more than one table. Table employee: Table: contact ID NAME TITLE DEPT_____ ID ADDRESS PHONENUM 111 John programmer 1 111 23 Yonge ST (416) 123-4567 211 Tom manager 2 112 34 YongeST (416) 223-4567 112 Bob programmer 1 211 45 Yonge ST (416) 143-4567 311 David tester 3 311 56 YongeST (416) 153-4567 SELECT name, address, phonenum Result: FROM employee, contact WHERE employee.id=contact.id NAME ADDRESS PHONENUM John 23 YongeST (416) 123-4567 AND employee.title=‘programmer’ Bob 34 YongeST (416) 223-4567 The Pointbase Database qPointbaseis a full-featured, Java written relational database. CDF Resource: http://www.cdf.toronto.edu/~t2aboels/#JDBC qYou can start PointBasein three different ways: Using PointBaseCommander Using PointBaseConsole Using a JDBC Application qUsing PointbaseDatabase on CDF § Create pointbase.ini file to tell pointbase where to store the database A typicall pointbase.ini will have a line: database.home=<full-directory-path> § To start pointbase commander: java –cp .:/h/u2/csc309h/lib/poitbase/pbembedded41ev.jar:/h/u2/csc309h/lib/pointbase/pbtools41ev.jar com.poitbase.tools.toolsCommander § You can then issue any SQL command to interact with the DB, for example, to check that pointbase was installed successfully, type “select tablename from systables” § More examples at http://www.cdf.toronto.edu/~t2aboels/resources/JDBC/pointbase/example/.
Recommended publications
  • Data Analysis Expressions (DAX) in Powerpivot for Excel 2010
    Data Analysis Expressions (DAX) In PowerPivot for Excel 2010 A. Table of Contents B. Executive Summary ............................................................................................................................... 3 C. Background ........................................................................................................................................... 4 1. PowerPivot ...............................................................................................................................................4 2. PowerPivot for Excel ................................................................................................................................5 3. Samples – Contoso Database ...................................................................................................................8 D. Data Analysis Expressions (DAX) – The Basics ...................................................................................... 9 1. DAX Goals .................................................................................................................................................9 2. DAX Calculations - Calculated Columns and Measures ...........................................................................9 3. DAX Syntax ............................................................................................................................................ 13 4. DAX uses PowerPivot data types .........................................................................................................
    [Show full text]
  • Lesson 17 Building Xqueries in Xquery Editor View
    AquaLogic Data Services Platform™ Tutorial: Part II A Guide to Developing BEA AquaLogic Data Services Platform (DSP) Projects Note: This tutorial is based in large part on a guide originally developed for enterprises evaluating Data Services Platform for specific requirements. In some cases illustrations, directories, and paths reference Liquid Data, the previous name of the Data Services Platform. Version: 2.1 Document Date: June 2005 Revised: June 2006 Copyright Copyright © 2005, 2006 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software- Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems.
    [Show full text]
  • (BI) Using MS Excel Powerpivot
    2018 ASCUE Proceedings Developing an Introductory Class in Business Intelligence (BI) Using MS Excel Powerpivot Dr. Sam Hijazi Trevor Curtis Texas Lutheran University 1000 West Court Street Seguin, Texas 78130 [email protected] Abstract Asking questions about your data is a constant application of all business organizations. To facilitate decision making and improve business performance, a business intelligence application must be an in- tegral part of everyday management practices. Microsoft Excel added PowerPivot and PowerPivot offi- cially to facilitate this process with minimum cost, knowing that many business people are already fa- miliar with MS Excel. This paper will design an introductory class to business intelligence (BI) using Excel PowerPivot. If an educator decides to adopt this paper for teaching an introductory BI class, students should have previ- ous familiarity with Excel’s functions and formulas. This paper will focus on four significant phases all students need to complete in a three-credit class. First, students must understand the process of achiev- ing small database normalization and how to bring these tables to Excel or develop them directly within Excel PowerPivot. This paper will walk the reader through these steps to complete the task of creating the normalization, along with the linking and bringing the tables and their relationships to excel. Sec- ond, an introduction to Data Analysis Expression (DAX) will be discussed. Introduction It is not that difficult to realize the increase in the amount of data we have generated in the recent memory of our existence as a human race. To realize that more than 90% of the world’s data has been amassed in the past two years alone (Vidas M.) is to realize the need to manage such volume.
    [Show full text]
  • Rdbmss Why Use an RDBMS
    RDBMSs • Relational Database Management Systems • A way of saving and accessing data on persistent (disk) storage. 51 - RDBMS CSC309 1 Why Use an RDBMS • Data Safety – data is immune to program crashes • Concurrent Access – atomic updates via transactions • Fault Tolerance – replicated dbs for instant failover on machine/disk crashes • Data Integrity – aids to keep data meaningful •Scalability – can handle small/large quantities of data in a uniform manner •Reporting – easy to write SQL programs to generate arbitrary reports 51 - RDBMS CSC309 2 1 Relational Model • First published by E.F. Codd in 1970 • A relational database consists of a collection of tables • A table consists of rows and columns • each row represents a record • each column represents an attribute of the records contained in the table 51 - RDBMS CSC309 3 RDBMS Technology • Client/Server Databases – Oracle, Sybase, MySQL, SQLServer • Personal Databases – Access • Embedded Databases –Pointbase 51 - RDBMS CSC309 4 2 Client/Server Databases client client client processes tcp/ip connections Server disk i/o server process 51 - RDBMS CSC309 5 Inside the Client Process client API application code tcp/ip db library connection to server 51 - RDBMS CSC309 6 3 Pointbase client API application code Pointbase lib. local file system 51 - RDBMS CSC309 7 Microsoft Access Access app Microsoft JET SQL DLL local file system 51 - RDBMS CSC309 8 4 APIs to RDBMSs • All are very similar • A collection of routines designed to – produce and send to the db engine an SQL statement • an original
    [Show full text]
  • Eclipselink Understanding Eclipselink 2.4
    EclipseLink Understanding EclipseLink 2.4 June 2013 EclipseLink Concepts Guide Copyright © 2012, 2013, by The Eclipse Foundation under the Eclipse Public License (EPL) http://www.eclipse.org/org/documents/epl-v10.php The initial contribution of this content was based on work copyrighted by Oracle and was submitted with permission. Print date: July 9, 2013 Contents Preface ............................................................................................................................................................... xiii Audience..................................................................................................................................................... xiii Related Documents ................................................................................................................................... xiii Conventions ............................................................................................................................................... xiii 1 Overview of EclipseLink 1.1 Understanding EclipseLink....................................................................................................... 1-1 1.1.1 What Is the Object-Persistence Impedance Mismatch?.................................................. 1-3 1.1.2 The EclipseLink Solution.................................................................................................... 1-3 1.2 Key Features ...............................................................................................................................
    [Show full text]
  • Java Database Technologies (Part I)
    Extreme Java G22.3033-007 Session 12 - Main Theme Java Database Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Summary of Previous Session Applications of Java to Database Technology Database Technology Review Basic and Advanced JDBC Features J2EE Enterprise Data Enabling XML and Database Technology Readings Class Project & Assignment #5a 2 1 Summary of Previous Session Summary of Previous Session Enterprise JavaBeans (EJBs) J2EE Connector Architecture Practical Survey of Mainstream J2EE App. Servers Web Services Developer Pack Enterprise Application Integration (EAI) and Business to Business Integration (B2Bi) J2EE Blueprint Programs Class Project & Assignment #4c 3 Part I Java and Database Technology Also See Session 12 Handout on: “Java and Database Technology (JDBC)” and Session 12 Presentation on: “Designing Databases for eBusiness Solutions” 4 2 Review of Database Technology Introduction to Database Technology Data Modeling Conceptual Database Design Logical Database Design Physical Database Design Database System Programming Models Database Architectures Database Storage Management Database System Administration Commercial Systems: www.oracle.com,www.ibm.com/db2, http://www- 3.ibm.com/software/data/informix/,www.sybase.com 5 Advanced Database Concepts Parallel and Distributed Databases Web Databases Data Warehousing and Data Mining Mobile Databases Spatial and Multimedia Databases Geographic Information
    [Show full text]
  • Microsoft Power BI DAX
    Course Outline Microsoft Power BI DAX Duration: 1 day This course will cover the ability to use Data Analysis Expressions (DAX) language to perform powerful data manipulations within Power BI Desktop. On our Microsoft Power BI course, you will learn how easy is to import data into the Power BI Desktop and create powerful and dynamic visuals that bring your data to life. But what if you need to create your own calculated columns and measures; to have complete control over the calculations you need to perform on your data? DAX formulas provide this capability and many other important capabilities as well. Learning how to create effective DAX formulas will help you get the most out of your data. When you get the information you need, you can begin to solve real business problems that affect your bottom line. This is Business Intelligence, and DAX will help you get there. To get the most out of this course You should be a competent Microsoft Excel user. You don’t need any experience of using DAX but we recommend that you attend our 2-day Microsoft Power BI course prior to taking this course. What you will learn:- Importing Your Data and Creating the Data Model CALCULATE Function Overview of importing data into the Power BI Desktop Exploring the importance of the CALCULATE function. and creating the Data Model. Using complex filters within CALCULATE using FILTER. Using ALLSELECTED Function. Using DAX Syntax used by DAX. Time Intelligence Functions Understanding DAX Data Types. Why Time Intelligence Functions? Creating a Date Table. Creating Calculated Columns Finding Month to Date, Year To Date, Previous Month How to use DAX expressions in Calculated Columns.
    [Show full text]
  • Ms Sql Server Alter Table Modify Column
    Ms Sql Server Alter Table Modify Column Grinningly unlimited, Wit cross-examine inaptitude and posts aesces. Unfeigning Jule erode good. Is Jody cozy when Gordan unbarricade obsequiously? Table alter column, tables and modifies a modified column to add a column even less space. The entity_type can be Object, given or XML Schema Collection. You can use the ALTER statement to create a primary key. Altering a delay from Null to Not Null in SQL Server Chartio. Opening consent management ebook and. Modifies a table definition by altering, adding, or dropping columns and constraints. RESTRICT returns a warning about existing foreign key references and does not recall the. In ms sql? ALTER to ALTER COLUMN failed because part or more. See a table alter table using page free cloud data tables with simple but block users are modifying an. SQL Server 2016 introduces an interesting T-SQL enhancement to improve. Search in all products. Use kitchen table select add another key with cascade delete for debate than if column. Columns can be altered in place using alter column statement. SQL and the resulting required changes to make via the Mapper. DROP TABLE Employees; This query will remove the whole table Employees from the database. Specifies the retention and policy for lock table. The default is OFF. It can be an integer, character string, monetary, date and time, and so on. The keyword COLUMN is required. The table is moved to the new location. If there an any violation between the constraint and the total action, your action is aborted. Log in ms sql server alter table to allow null in other sql server, table statement that can drop is.
    [Show full text]
  • Query Execution in Column-Oriented Database Systems by Daniel J
    Query Execution in Column-Oriented Database Systems by Daniel J. Abadi [email protected] M.Phil. Computer Speech, Text, and Internet Technology, Cambridge University, Cambridge, England (2003) & B.S. Computer Science and Neuroscience, Brandeis University, Waltham, MA, USA (2002) Submitted to the Department of Electrical Engineering and Computer Science in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science and Engineering at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY February 2008 c Massachusetts Institute of Technology 2008. All rights reserved. Author......................................................................................... Department of Electrical Engineering and Computer Science February 1st 2008 Certifiedby..................................................................................... Samuel Madden Associate Professor of Computer Science and Electrical Engineering Thesis Supervisor Acceptedby.................................................................................... Terry P. Orlando Chairman, Department Committee on Graduate Students 2 Query Execution in Column-Oriented Database Systems by Daniel J. Abadi [email protected] Submitted to the Department of Electrical Engineering and Computer Science on February 1st 2008, in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science and Engineering Abstract There are two obvious ways to map a two-dimension relational database table onto a one-dimensional storage in- terface:
    [Show full text]
  • Quick-Start Guide
    Quick-Start Guide Table of Contents Reference Manual..................................................................................................................................................... 1 GUI Features Overview............................................................................................................................................ 2 Buttons.................................................................................................................................................................. 2 Tables..................................................................................................................................................................... 2 Data Model................................................................................................................................................................. 4 SQL Statements................................................................................................................................................... 5 Changed Data....................................................................................................................................................... 5 Sessions................................................................................................................................................................. 5 Transactions.......................................................................................................................................................... 6 Walktrough
    [Show full text]
  • Column-Stores Vs. Row-Stores: How Different Are They Really?
    Column-Stores vs. Row-Stores: How Different Are They Really? Daniel J. Abadi Samuel R. Madden Nabil Hachem Yale University MIT AvantGarde Consulting, LLC New Haven, CT, USA Cambridge, MA, USA Shrewsbury, MA, USA [email protected] [email protected] [email protected] ABSTRACT General Terms There has been a significant amount of excitement and recent work Experimentation, Performance, Measurement on column-oriented database systems (“column-stores”). These database systems have been shown to perform more than an or- Keywords der of magnitude better than traditional row-oriented database sys- tems (“row-stores”) on analytical workloads such as those found in C-Store, column-store, column-oriented DBMS, invisible join, com- data warehouses, decision support, and business intelligence appli- pression, tuple reconstruction, tuple materialization. cations. The elevator pitch behind this performance difference is straightforward: column-stores are more I/O efficient for read-only 1. INTRODUCTION queries since they only have to read from disk (or from memory) Recent years have seen the introduction of a number of column- those attributes accessed by a query. oriented database systems, including MonetDB [9, 10] and C-Store [22]. This simplistic view leads to the assumption that one can ob- The authors of these systems claim that their approach offers order- tain the performance benefits of a column-store using a row-store: of-magnitude gains on certain workloads, particularly on read-intensive either by vertically partitioning the schema, or by indexing every analytical processing workloads, such as those encountered in data column so that columns can be accessed independently. In this pa- warehouses.
    [Show full text]
  • LATERAL LATERAL Before SQL:1999
    Still using Windows 3.1? So why stick with SQL-92? @ModernSQL - https://modern-sql.com/ @MarkusWinand SQL:1999 LATERAL LATERAL Before SQL:1999 Select-list sub-queries must be scalar[0]: (an atomic quantity that can hold only one value at a time[1]) SELECT … , (SELECT column_1 FROM t1 WHERE t1.x = t2.y ) AS c FROM t2 … [0] Neglecting row values and other workarounds here; [1] https://en.wikipedia.org/wiki/Scalar LATERAL Before SQL:1999 Select-list sub-queries must be scalar[0]: (an atomic quantity that can hold only one value at a time[1]) SELECT … , (SELECT column_1 , column_2 FROM t1 ✗ WHERE t1.x = t2.y ) AS c More than FROM t2 one column? … ⇒Syntax error [0] Neglecting row values and other workarounds here; [1] https://en.wikipedia.org/wiki/Scalar LATERAL Before SQL:1999 Select-list sub-queries must be scalar[0]: (an atomic quantity that can hold only one value at a time[1]) SELECT … More than , (SELECT column_1 , column_2 one row? ⇒Runtime error! FROM t1 ✗ WHERE t1.x = t2.y } ) AS c More than FROM t2 one column? … ⇒Syntax error [0] Neglecting row values and other workarounds here; [1] https://en.wikipedia.org/wiki/Scalar LATERAL Since SQL:1999 Lateral derived queries can see table names defined before: SELECT * FROM t1 CROSS JOIN LATERAL (SELECT * FROM t2 WHERE t2.x = t1.x ) derived_table ON (true) LATERAL Since SQL:1999 Lateral derived queries can see table names defined before: SELECT * FROM t1 Valid due to CROSS JOIN LATERAL (SELECT * LATERAL FROM t2 keyword WHERE t2.x = t1.x ) derived_table ON (true) LATERAL Since SQL:1999 Lateral
    [Show full text]