So let me show you how a view is created. If you look here on the left, you'll notice that I have a customers table that has a CUSTID, and a CUSTNAME. And an employees table that has an EMPID and an EMPNAME. And a sales table that has a SALESID, an EMPID, and a CUSTID. So basically the sales table has a bunch of numbers, isn't what it looks like because this EMPID is associated with the EMPID in the employees table. If I take the EMPID from the sales table and I join it or combine it with the EMPID in the employees table, I'm able to take a look at what the employee name or the EMPNAME is. If I take the CUSTID from the sales table, I join it with the CUSTID in the customers table, I can find out the CUSTNAME. That sounds cryptic, but let me show you what I'm talking about. If I do a select and I do a custid,custname from customers, notice here's the CUSTID in the CUSTNAME, okay? But if I do select custid,empid from sales, notice its numbers, see that 1, 1, 2, 2, right? You don't really know who the cost is, and who the employee is. And I did it from the sales table, the sales table is filled with numbers, so let me show you the join if you will. What I want to do is I want to say that I want to select from the customers table. I want to select customer name or custname from the employees table. I want to select empname, just like that. Yeah, and I want to do it from the employees table and the customers table. And I want to say where, and I want to join them, and I want to do comma sales. And I want to do where sales table, custid = customers table, custid. And sales table, empid = employees table, empid. And now when I run this, what ends up happening is I see the customer name and employee named, this customer and this employee. So here's the thing, this statement right over here, this is a complex statement, is it not? A lot of joining and wear claws, and look at the names of the columns custname and empname, and it would be weird. It would be difficult for someone who doesn't know or work with SQL to figure this out when all they want is the employee name and the customer name. So if I include the salesid here, like so, and I'm going to show the result of this notice. So there's a salesid, notice 1, 2, 3, 4, 5, 6 the custname and the employee name. I'm showing the customer name and I'm showing the employee name, and I'm doing it all from the sales table. So what do I do to make this a view? I just do this, I do create view as, and I'm going to do create view sales info as, I'm going to make it even better, I'm going to make a sound better. I'm going to do vsalesinfo. So v for view, and then I'm going to make this better. I'm going to say that this is going to be called ID, okay, this will be called customer name, this will be called employ name like that. Now I run this and look what it says, view VSALEINFO created you see that. Now look, I want to show you something, when I say select star from VSalesInfo. There's customer name, there's employee name, and there's a salesid just called ID, notice that? So this view right here really has three columns, the salesid called ID, notice that right there ID. The customer name, the custname which is really a customer name, which is that right there. And the employee name, which is the empname right here. So from a reporting perspective, wouldn't you rather query, and use, and filter the sales info view, or would you rather write this out every time? This is much simpler, isn't it? So when you look at views here, you'll notice if I go down to the view that I'm interested in. Here's the VSalesInfo view noticed a column name, ID, customer name, and employee name. Look at the data types, yeah, very easy, isn't it? If I expand this, it shows me the columns, okay? If I right-click and click on, edit, it shows me what the view is made of, okay, so that's a view.
