Discover millions of ebooks, audiobooks, and so much more with a free trial

Only $11.99/month after trial. Cancel anytime.

SQL: For Beginners: Your Guide To Easily Learn SQL Programming in 7 Days
SQL: For Beginners: Your Guide To Easily Learn SQL Programming in 7 Days
SQL: For Beginners: Your Guide To Easily Learn SQL Programming in 7 Days
Ebook162 pages2 hours

SQL: For Beginners: Your Guide To Easily Learn SQL Programming in 7 Days

Rating: 5 out of 5 stars

5/5

()

Read preview

About this ebook

There was a time when Information Technology was only known as "Electronic Data Processing." Despite the fuss about innovative techniques, data process is still the heart of every system in the world—and even more so as the data sizes that are being managed today seems to grow at an exponential rate.

Some of the architectural preferences are complete long shots on the future. You will definitely not only need an exceptionally firm grasp on the theoretical knowledge, but also rigor. However, those characteristics are essentials of any art.

This book is definitely not a SQL cookbook wherein all possible problems and their solutions are listed. The aim is to impart not only a firm grasp of the fundamentals of database query language, but also a good working knowledge of the relational theory of SQL.

It is also the aim of this book to help budding developers—and their administrators—to raise exceptionally good questions. There's a big chance that you'll still write bad code—inefficient queries after going through this book. A developer, from time to time, has to. Hopefully, however, it'll be knowingly and with perfectly good reason. Welcome readers to the world of SQL. Let's begin your journey.

LanguageEnglish
Release dateDec 4, 2017
ISBN9781386733959
SQL: For Beginners: Your Guide To Easily Learn SQL Programming in 7 Days

Read more from I Code Academy

Related to SQL

Related ebooks

Programming For You

View More

Related articles

Reviews for SQL

Rating: 4.75 out of 5 stars
5/5

4 ratings0 reviews

What did you think?

Tap to rate

Review must be at least 10 words

    Book preview

    SQL - i Code Academy

    Preface

    There was a time when Information Technology was only known as Electronic Data Processing. Despite the fuss about innovative techniques, data process is still the heart of every system in the world—and even more so as the data sizes that are being managed today seems to grow at an exponential rate.

    Most sensitive corporate data nowadays are stored in computer databases and are accessed via the famous, but imperfect, SQL query language—a combination that had started to gain acceptance among the elite during the 80s and has swept the competition aside ever since.

    There isn’t a developer these days who does not have at least an intermediate working knowledge of Structured Query Language, the standard language for database access, a staple in an Information Technology course. This particular claim is exceptionally accurate, if you see knowledge as the capability to obtain, after a certain degree of effort, functionally correct outcomes. Enterprises around the world, however, are dealing with exceptionally large data volumes. Functionally correct results, therefore, are no longer adequate: they need to be exceptionally fast as well.

    Database performance has become every major company’s bane nowadays. Interestingly, even though everybody accepts the fact that the root of the performance problem resides in the code, it is widely accepted that the developer’s primary concern should be to create a code that works—which obviously seems to be a reasonable expectation.

    The idea is that the code to access the data within the database should be as rudimentary as possible, for reasons of ease of maintenance, and that inefficient SQL should be forwarded to veteran database admins for tweaking using a few magical database parameters. In the event that such tweaking is not sufficient, then a hardware upgrade is the best action to take.

    Most often than not, the safest and most common approach ends up doing more harm than good. Writing bad code and forwarding it to database admins for tweaking is actually just sweeping the dirt under the rug. Many experts agree that developers should be the first people who need to be concerned about performance, and perceive issues about SQL as something that are more than just about proper coding of queries.

    Performance is basically viewed as something that is profoundly dissimilar from tuning when viewed from the perspective of a developer. Database administrators (also called DBAs) may possess some query language skills and is capable to tweak a poorly performing query statement, but developers are the ones who are writing the code that may run for years, surviving numerous hardware generations and numerous reiterations of the software.

    Your SQL code must be sound and fast right from the get-go. It may be a sorry assessment, but if numerous developers know Structured Query Language, only a select few have a firm grasp of its relational theory.

    So, why do you need this SQL book? Well, there are basically three types of SQL book: books that teaches the basics of the SQL syntax and logic, books that talk about how to utilize a more problem-solving approach and advance techniques, and tuning and database performance books that are specifically targeted to veteran database administrators.

    This particular book is basically directed to complete novices who are just starting to learn SQL. This book will teach you how to write SQL code correctly right from the start. Also, this book will also teach you ways on how to optimize your database so that your SQL code will work as intended.

    Teaching someone how to learn—and even to use—a language is hard enough as it is; but how does a book effectively teach someone how to use a language efficiently? SQL is a computer language that looks extremely simple once initiated. However, don’t let its simplicity deceive you. Despite its simplicity, it accommodates an exceptionally large number of combinations and cases.

    Some people first compared it to a game that we all know: chess. However, it dawned on us that chess was basically created to teach the fundamentals of war. We have an inherent tendency to perceive every performance task as a war against battalions of rows, and it dawned on us that the problem in teaching novices how to utilize databases properly also has an uncanny similarity to the problems encountered when teaching military officials how to conduct war.

    You need talent, skills, and knowledge. Talent can never be taught. It can only be nurtured. This notion is what strategists like Sun Tzu, who authored the famous Art of War centuries past, to generals of modern times, have believed—therefore they tried to impart the knowledge and experience that they acquired on the battlefield using simple rules and maxims that they hope would become guiding stars for men in the battle.

    Numerous respected specialists in the Information Technology field see themselves as scientists; Art seems to be more applicable than Science whenever it comes down to denoting an activity that needs not only creativity, experience, and flair, but also understanding and rigor.

    It is very likely that this notion would be disapproved of by Science partisans, who proudly declare that for every SQL problem, there exists an all-encompassing solution, which can only be achieved by meticulous analysis and good data knowledge. However, we do not view the two positions at odds. Scientific approach and rigor will definitely help you address one particular issue at one particular instance.

    In the world of SQL development, if you do not relate the ambiguities with your opponent’s next move, bigger ambiguities rise in future iterations. What if the volume of a table within your database all of a sudden increases? What if, after a combination, the total sum of users has quadruple? What if we decide to retain a century worth of data on the Internet? How will the database software behave on hardware that is totally more powerful than the one that it is currently running?

    Some of the architectural preferences are complete long shots on the future. You will definitely not only need an exceptionally firm grasp on the theoretical knowledge, but also rigor. However, those characteristics are essentials of any art.

    This book is definitely not a SQL cookbook wherein all possible problems and their solutions are listed. The aim is to impart not only a firm grasp of the fundamentals of database query language, but also a good working knowledge of the relational theory of SQL.

    It is also the aim of this book to help budding developers—and their administrators—to raise exceptionally good questions. There’s a big chance that you’ll still write bad code—inefficient queries after going through this book. A developer, from time to time, has to. Hopefully, however, it’ll be knowingly and with perfectly good reason. Welcome readers to the world of SQL. Let’s begin your journey.

    Chapter 1: SQL’s Origins

    In this chapter, we will be talking about SQL’s background on why and how it came to be. If you are an IT professional who focuses mainly on data management and manipulation, having knowledge of SQL’s history will greatly help you understand its significance in the information technology world. Having a firm grasp of SQL’s foundation will also give you the ability to maximize its potential in the constantly changing world of I.T.

    Most businesses today invest millions of dollars in technology that allows them to gather and store data in the most effective and efficient way. Gathering information, however, is only the tip of the iceberg of the whole data manipulation process. Companies, especially the fortune 500 ones, need specialists who possess the ability of storing, managing, analyzing, and presenting data.

    In other words, they need to make use of computer programs that will convert raw data into more understandable and useful information.  Now, thanks to SQL, or Structured Query Language, transforming, manipulating and accessing data has now become very straightforward.

    ––––––––

    SQL History

    SQL, pronounced as see`qwl or ees-que-ell, is basically a computer language that was invented by IBM back in the 1970s. They used a paper called A Relational Model of Data for Large Shared Data Banks that was written by Dr. E.F.

    Enjoying the preview?
    Page 1 of 1