Book Image

Learn SQL Database Programming

By : Josephine Bush
5 (1)
Book Image

Learn SQL Database Programming

5 (1)
By: Josephine Bush

Overview of this book

SQL is a powerful querying language that's used to store, manipulate, and retrieve data, and it is one of the most popular languages used by developers to query and analyze data efficiently. If you're looking for a comprehensive introduction to SQL, Learn SQL Database Programming will help you to get up to speed with using SQL to streamline your work in no time. Starting with an overview of relational database management systems, this book will show you how to set up and use MySQL Workbench and design a database using practical examples. You'll also discover how to query and manipulate data with SQL programming using MySQL Workbench. As you advance, you’ll create a database, query single and multiple tables, and modify data using SQL querying. This SQL book covers advanced SQL techniques, including aggregate functions, flow control statements, error handling, and subqueries, and helps you process your data to present your findings. Finally, you’ll implement best practices for writing SQL and designing indexes and tables. By the end of this SQL programming book, you’ll have gained the confidence to use SQL queries to retrieve and manipulate data.
Table of Contents (24 chapters)
Section 1: Database Fundamentals
Section 2: Basic SQL Querying
Section 3: Advanced SQL Querying
Section 4: Presenting Your Findings
Section 5: SQL Best Practices

Chapter 4

  1. Keywords and spaces.
  2. Numbers (0-9), lowercase letters (a-z), uppercase letters (A-Z), the dollar sign ($), and the underscore (_).
  3. CREATE DATABASE yourschema;
  4. The Output panel.
  5. With a natural key, you are using unique columns, and the data in those columns exists outside the database (that is, in the business world). With a surrogate key, you are creating a column to hold a unique value for each row, and that value isn't used anywhere outside the database.
  1. # this is a single line comment
  2. /*
    this is a
    multi line
  3. Clustered indexes sort the data in order on disk and nonclustered indexes don't.
  4. If two or more queries are requesting the same data, creating locks that won't be resolved, MySQL will decide which is easiest to kill (usually based on how long it will take to roll back any given query).
  5. Yes.