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)
1
Section 1: Database Fundamentals
7
Section 2: Basic SQL Querying
11
Section 3: Advanced SQL Querying
16
Section 4: Presenting Your Findings
19
Section 5: SQL Best Practices

Choosing the right data type

It's essential to understand how storage usage affects your database. Most databases are stored on disk (with some exceptions that allow data to be stored in memory). When the database needs to fetch data for you, it needs to read from the disk and return results to you. This is where disk I/O comes into play. I/O stands for input/output, and it's the communication between a system or computer and a person or another system/computer. Disk I/O is the reads and writes that are happening against a disk, and its rate is dependent on the speed at which the data can be transferred from disk to memory. This is the time it will take to return the data for your query. The more data you request, the longer it's going to take, and if you have a lot of people requesting a lot of data, then it may take much longer than is acceptable. This is why...