The Database Fundamentals series is now done. We started with understanding what a database is, and then spent a little time understanding how databases store text, known as collation. The next step was understanding data types in general, and how SQL Server stores them. After that was understanding normalization, with a focus on only having[…]
My First DELETE Statement Here are the links to the previous posts in this series: My First SELECT Statement My First INSERT Statement My First UPDATE Statement This week is a much shorter post, where we will learn how to remove data from a table using a DELETE statement. We will also refresh our memories[…]
My First UPDATE Statement Last week we covered how to put information into a table using an INSERT statement. This week we will learn how to make changes to data that is already in a table using an UPDATE statement. We are also going to learn all about why the WHERE clause is so important.[…]
My First INSERT Statement Last week we covered how to get information out of a table, using a SELECT query. This week, we will discover some of the myriad ways to put data into a table. The good news is the concept is straightforward: we have a list of columns in a table, and each[…]
My First SELECT Statement Microsoft SQL Server makes it really easy for us to query tables. In SQL Server Management Studio (SSMS) for instance, we can right-click on any table we have access to and select the top 1000 rows from that table. Please don’t query tables this way in a production environment. It’s a[…]
When we want to retrieve information from a database, we query the structure with language appropriate to the database. Remember right at the start of this series we saw that a database could be a phone book or a recipe book. So how do we find the phone number of Randolph West? By looking up the[…]
A friend of mine in the filmmaking business, who is exceedingly bright but has never worked with SQL Server before, was reading through the first five posts of this Database Fundamentals series, and asked a great question: “I guess I’m not understanding what a byte is. I think I’m circling the drain in understanding it, but not[…]
Phew! There’s a lot to take in with data types, collation, precision, scale, length, and Unicode, and we’re just getting warmed up. This week’s post is over 2,000 words long!
Over the last three weeks, we’ve gone fairly deep into data types, and now we are going to see how they come into play with normalization.
If we go back to the first post in this series, I mentioned normalization, and then apparently I forgot about it in the next two posts. What you didn’t see is that I was talking about it all along.
Last week, we discussed storing text in a database. This week we will dive deeper into data types. When storing data in our database, we want to make sure that it’s stored accurately and that we only use the required amount of space. This is because when we access the data later, we want to[…]
Last week we started with a very simple definition of a database: a discrete set of information, with a specific structure and order to it. We briefly looked at normalization, which is a way to store as little of the information as possible, so that it stays unique. We will cover more normalization as we[…]