SQL Tutorial: Aliasing

Want to learn more? Take the full course at https://learn.datacamp.com/courses/improving-query-performance-in-sql-server at your own pace. More than a video, you'll learn hands-on coding & quickly apply skills to your daily work. --- In this lesson, we'll discuss how to use aliasing to avoid some kinds of errors and how it can make code easier to read and understand. Aliasing refers to providing a short name, code, or simple identity to tables, columns, and sub-queries in a query. Aliases are temporary and only applied during the running of the query; they do not alter the table or column names in the database. They can be handy for making code in a query easier to read. And, in many cases, are required, for example, a new column or sub-query, that will be re-used in another part of the query. Let's look at some reasons why we need to use aliasing. We use aliasing to: Avoid repetitive use of long table or column names. Easily identify joined tables and associated columns. Identify new columns. Identify sub-queries. Avoid ambiguity when columns from joined tables share the same name. And rename columns. In this example, we want to know the 2017 population of each Nation capital. We can get this by joining the Nations and Cities tables from the Earthquakes database. When run, it returns an error because both tables have a column named Pop2017. These refer to 2017 census populations. In the Nations table, it is the population of each Nation, and in the Cities table, it is the population of each City. The query needs to know which is which. In this case, we want the City population. Aliasing tables can correct this; Nations as n and Cities as c. Now if we look at the SELECT statement, we see aliases used to indicate the source table of each selected column with the column name prefixed with the alias of the table name. The Cities table has the c alias, and therefore the 2017 population column is identified as c.Pop2017. Note, there are no rules to what