Lifting the Veil Career Paths: SQL Training & Job Stacking Strategy Revealed

We're live. Let's get it, man. Let's get it. So, tonight I'm super excited because

I've been working last couple of days every actually since Sunday. Uh, I kind

of showed y'all this beginning of class and you know how you think of something and then

your brain just get to going all the sinapses get the firing in your brain and the axioms or whatever and you just

start realizing, man, I could really take this to the next level. And so what I've been doing about what I've been

doing all day, let me show y'all. So, the other day I showed y'all the courses and the courses are were kind of listed

out, but now what I decided to do was build out something called career paths

through Lifting the Veil. And what's so beautiful about this, we've taught I've taught uh well, not me, but

lifting the veil, we've had many, many instructors um that came through that taught different subjects, different

things like that. And so when you look at this, this is just a brief synopsis of of the database

administration course that I had a brother teaching. Um, so we got two sections of it. One is called the job

ready section. This is the bare bones of what you need to get to work. Y'all already got this first one.

Y'all pretty much going to have this one. So, all you gonna have to do is do these two here. If you want to be a

database administrator, there are slight modifications in SQL, but guess what? You going to

already know SQL. So, this is really easy. So all you really got to do is learn this one and you can start trying

to go after database administration administration role. Um the better you are as a developer. Obviously

performance tuning is a big deal. I talked about that. That's 52 classes. Now I haven't developed all

this out as you can see. It's coming. It's stubbed out right now. But I just wanted y'all to see this because this

I'm I'm super excited. Maybe you guys aren't because y'all don't probably know what y'all looking at or maybe you are.

I don't know. But let me say this right here. My course and where you guys are right now. This is what I'mma bring.

I'mma bring this TSQL SSIS development, SSRS development, PowerBI, and I'mma do I'm I'mma dabble into I can do this is

something I can teach all this. I'm pretty comfortable. Now, obviously I I you know, I got to brush up, make sure

I'm right with you guys to get y'all where y'all need to be. But this right here will get you job ready. But as you

can see, I don't have anything else down here. This is to get you get your job ready. Now, when you go back

over here, once you got that, now obviously these two are by themselves, but they pay. Now, this is my thing.

There's this thing called job stacking that companies do that people do where you get multiple projects. One time I

had three projects. I was making over 30,000 a month. Um, I quit after a month because the dude

got on my nerves. He's talking to me like I was crazy. I'm like, "Bro, I got two other jobs. I don't need this." So,

I quit. But the thing is, I I've had two jobs on multiple occasions. It's a it's a comfortable feeling because every

Friday I was getting I was one job was paying me twice a month. Other job was paying me every Friday. I was getting

paid every Friday. Then twice a month I get a big check. So, you know, I was, you know, so I was I was rolling. and I

was saving up money. I was doing a lot of different things. So, what what I want you guys to look at now, this the

thing. So, for example, I'm going to just click on this one, data analyst. Um, this is a little bit more focused,

but guys, y'all gonna be real close to this one because you gonna have the TSQL. Every one of these classes, let me

go back. Just about all these classes up top, it says most paths are start at TSQL,

right? So, you know, a couple of have their own door in, but for the most part, the only

two you got AI engineer, blockchain engineer. Everything else got to do with TSQL. So, you guys are fundamentally in

the door with either one of these paths y'all want to choose. I also put the money up there cuz look, man, that's

what we here for. Ain't nobody coming up here doing this for nothing, right? We doing this for the money. Also, if you

want to track, try to go into a certification, you can. I'm not even done. Y'all saw this the other day. It

was just a list, not turned into something more comprehensive as to what you guys are actually trying to do. And

I wanted to make this like this one's done. So, it literally has So, if I come here and click on this, it's got a

video. I showed y'all this the other day. It's got scripts, right? And then it has a quiz and it got

a lab. See there? Got a lab. So, you can go run these, but then you got quizzes. Now, what I'm

gonna do, what I just decided, like literally earlier today, I just ain't had time to do it.

Every time you get to the end of one of these, you gonna have like a 70 70 uh question quiz.

Um, not even call it, it's going to be a test and you got to get 90 90% success rate.

So if it's 70 of them, that mean you can't miss seven. Are you gonna fail? And the reason I'm

doing that, guys, it's really you can go through these entire courses without me. Now, obviously having me

makes it easier because I can teach this way faster and stuff, but you guys are self-studying different stuff like that.

This is basically all the self-study work is right here. That way you ain't got to go try to find stuff. You ain't

got to look at the bulking. You still have your study groups. Obviously, you gonna still need that,

you know, moral support, motivation. There's a lot of things that happens when you have something like a

mastermind group. But as you can see, these are heavy. I mean, these pay big. Like, I I'm not playing like they you

talking some big money. Like 300,000. You It's nothing. This is Snowflake right here. Let me show y'all something.

I'mma just type I typed up snowflake up top. Starting off the street cold turkey, you

can get as a junior, you can get 120 something thousand. That's at the top end, right? 82 to 12. I try not I try to

come in the middle. So me, I if when I was first starting, I would have tried to come in there about like 105.

That's what I would have did. But as you can see, what's what's going to be crazy about this? all these job

descriptions now everything on this job description y'all y'all ain't y'all can touch just about CFA we going to touch

it you'll be done touched all that so now these job descriptions just everything on here you know

your resume is going to going to read just like their job description so yeah you could and [clears throat]

this is the thing see there you see how you got SSIS still up this is the thing that's why I'm teaching it because

although SSIS is older. You guys are going to have so many pieces. If you come through my class, you going

you going to be straight cuz this is this everything I'm teaching y'all bounces off into something else. So by

the time you get over here and you start trying to go for these 160 $170,000 jobs, they're going to have see their

ETL data pipelines. So that so that's that's um that means you're going to be dealing with uh as

Azure data factory. So when you come back over here um which one was it? Is this it? I think

this it nope. Go back.

Anyway, a couple of them got data factory. I don't know which one. Is it AI? No, it ain't AI.

It's uh It's not this one. It's not that one. Is it this one? Yeah. See there? So, you got data factor

and that's already done. So, by the time I get done, that's why I said I'm going to give y'all this in December because

by the time December get here, it's going to be thick. It's going to be it's going to be like loaded down with

information. And I'm pretty much doing everything for you guys. I'm probably gonna create another page with note

cards for each one of these so that you'll and it'll all be inside

of the port of the lift in the veil portal so you can get to it, but you'll be able to come in there and click and

download all the note cards. We still gonna have the Facebook groups, but you have these note cards. I'm gonna have

note cards for all this. I just think that's going to make it easy for you. That way you ain't got to think.

Everything's done. All the work is done. You really technically won't necessarily need to come to class, but obviously

that makes it easier if you come to class. But what I'm saying is if you want to try to study, you know, as a

subscriber, you'll be able to come in here and study whatever you want. See what I'm saying? I I you may not even

tell me you trying to do this and you come in here. Look at you got snowflake right there. You got you gonna

have these two with my class. GitHub is really just version control. A ain't really much to that. That's why

it's only 25 lessons. I mean guys, y'all you know now I what I'm doing right now is I'm creating like a 14month

curriculum for for some of these. Some of them going to take longer, some of them going to take less. you know my

class you know it's faster a little bit faster but you know like Azure you got data factory here then you got airflow

which I don't even know what that is I think that's some sort of ETL tool but by the time you get those two now you're

an you can literally go for analytical analytics engineer jobs because you got everything

so you come over here and you can really hit them across the head financially you can really hit people across the

head then when you go fully remote, which they have a lot of remote jobs. Let's see.

See, they're they got fully remote jobs, so you can get two or three. If if you get on this one,

everything on here, you'll already know just about give or take a couple of bells and whistles, but you'll be able

to All this is stuff we touching. You're already messing with all this anyway. You're gonna be messing with

that that go data factory. See there? So, you'll really be able to do what these people you gonna be messing with.

You going to be com see let me tell you something. So, let's say you learn Python through through this other course

over here. Let me show you. Let's say you just take Python this way and you do Python for PowerBI, right?

They might want you to do something else with Python, but at least you can say, "Well, I've I've actually dealt with

Python because I did it when I was modifying my PowerBI reports." So, you can literally check that off on your

resume. It's something that you you you're familiar with. That's the difference. So, it's been plenty of

times I've come into jobs and it's been stuff I touched. I didn't actually do it, but I touched it a little bit

because I said that I was able to get a job. So this skill set,

I mean, they want to architect right here. And by the way, you can go down here.

Oops. You can go here to the bottom. And these where the heavy hitters at.

This where this where the dogs at. You know what I'm saying? Because right here is where you can really start mentioning

some high-end stuff. And I'mma add a snowflake architect down here. and you know, but they got a Salesforce

data architect. Each one of these jobs over here, we trying to get 300, you know, that that's what I'm trying to I'm

trying to get right $250, $300,000 per job. That's what you want. Principal data

engineer is big, but this is like a more of a right here. It says this isn't a starting point.

It's shown to students as where you know the other part other paths lead, not something to enroll in directly. Right?

So when you get in here, you choose a specialty. See there? So you choose which one you want to mess

with. You come down here, you get your senior level, and then you get to the leadership level.

And by the time, and that's that capstone project, which is what you're going to do when you going for guess

what? The DP700 certification. So, this will really put you guys in the

driver's seat as far as really what you want to do. You know what I'm saying? And it ain't it's not done. By the time

y'all get here, by the time I give you guys access to this, it's probably going to be way meteor and thicker than what

it is. I don't want to overdo it. I That's what I'm saying. I think it's simple. I got to build out all the

videos, but what I want to do now is improve what I have. So, I'm going to give you guys quizzes or

not quiz, tests. I think that's a big deal because if you can answer these tests,

you can come through here and answer a test and you can ace that test, you're pretty solid. And it's going to be the

types of questions aren't going to just be what is a joint. It's going to be how to, how would you do this, how would you

do that? Because what it wants to see is what you've done. Can you do stuff? As well as what is. So, it's what is this?

What is that? Now, obviously, the SQL test probably gonna be a lot more question because it's 118 sections. So,

that might be 120 questions. And you're like, god dang, you you taking a long time. The reason I'm doing

that is because what I want you guys to be able to do is to be able to come out here and shoot down anybody coming at

you in an interview. and you you're so good to where you beat out so many people. And I've already had students

that did that just doing self-study. But this is gonna change everything. telling you like this is really going to put you

guys in the driver's seat. And um you know if I type up data engineer oops if I type data engineer,

you know, and just hit search, you know, there are jobs out there for that. So

see how much they talking principal data engineer that's that's actually which one was it? I think I saw that

somewhere or was it at the bottom? There you go. So you know everybody don't have these

skills. Everybody doesn't. Now imagine job stacking with two of

these. So we getting four $500,000. You know what I'm saying? So you can literally

come in here and make more than doctors if you if you do it right. Now obviously it's not going to always

be it's going to take some work. It's going to take some time. That's why I'm saying give yourself a year. That's why

I separated it out with job ready versus senior level stuff. So if I click on this, this is job ready. This is more

senior. See that? Go CFO right there. So I got everything for you guys. So y'all can come in here and just start

really working towards what you trying to work toward. Not yet because I'm still working on it. But,

you know, this is something that I'm I'm really happy about because this is something I really, you know, lifting

the I've been doing this for over about right at 10 years now. And I started with just sending an email link through

an email and letting people join the link and just teaching. We have no scripts, but we had the scripts. I did

do that, but we didn't have nothing. We didn't have no portal. We had no website. All we had was a little page

you go and read about what I do and that was it. And I just went there and I just started

helping people and people started getting jobs and I was doing it five days a week. But now this is going to be

set up where if you study six hours a week, which is not that much. I ain't say 10 hours, six. You do six hours a

week for give me 14 months, you should be able to cover this whole thing. You should

job ready is not going to pay. You're going to be near the low end. advanced depending on your experience.

There you go. 160 is easy. Easy. Any of these J senior any of these uh advanced tabs that I have down there

will get you 160 170 easy. Not even a struggle. Data bricks lakehouse engineer. I I you know and we

can look this stuff up but these people you know data engineering foundation so you got to take the foundation so you

got to make up in your mind which one you want that's why I did it like this so you guys can pick up half because you

may not know which one you might want to now these two here are specific they're not they ain't going to really

have nothing to do with what I'm teaching but we're going to teach this too

so this all this is going to be stuff that you have to go learn on your own cuz I do have somebody that can teach it

but I don't know if he going to know all this so I'm probably eventually once lifting the veil if it's running like it

used to where I had a bunch of people teaching at one time I had like four four separate classes going at one time

when I was doing that then that's when I was able to get I was able to hire you know people like a AI engine now I got

somebody that can teach this she's real Good. Oh, this a lot. This is a lot. I don't know if she know

all this. So, I need to find somebody that can do all this, but if it's somebody that can

do all this, they probably going to charge me over $100 an hour. But, we'll see. I mean, even still, I

mean, these are the types of classes that are going to make a huge difference. I'm gonna build all this

out. Worst case, you'll be able to just come in here and self-study. Just do it on your own.

You know, this coupled with the software, coupled with like some YouTube videos, whatever. That's all you really

need, man. You I know you like, well, I need an instructor. But that's why I'm telling you guys this first. This This

is my flagship class. I mean, my flagship. This is everything. This is what I teach. This is what I give you

guys. This will get you in the door pretty much. This gets you in pretty much most of the classes that the other

classes. This is part of it. this to get you in there. This capstone is going to be going to go in a lot of

other areas, but this this is not the same capstone. It's different. This is for what I taught y'all.

So, that's about it. Um, but let me get the class. I just wanted to show y'all that

I already got it on the website, but I didn't change it now. It's probably So, it's been changed, but anyway, we'll get

there, man. I was running my mouth. Sorry about that. Let's go. All right. Where we at?

Let's see. Oh, and by the way, just so you guys know,

y'all might want to watch this video here. I lost a couple subscribers subscribers

with this video, but that's the problem. People don't want to tell the truth. And that's that's one of the problems in

tech. A lot of people don't want to tell people the truth about what it really takes to be successful. So, when you get

a chance, I'm going to put this in the Facebook group. Check it out. You know, it's a bit controversial, but

I think it's the truth, man. I just tell people what what you know what it is. And uh either way, man, we good.

But there we go. Nobody says it. Nobody ever talks like that. Everybody, oh well,

just get a certification or just get Look, man, I tried to get jobs. First of all, those certification tests are

extremely hard because it's a source of revenue. It's not just they're trying to make some money. So they g they gonna

give you seven answers. two of them gonna look like complete ident completely identical. So just be aware.

All right. You checked it out. Yeah, man. You know, and and the thing

is with a video like this, I want people to understand this is not I'm not saying lie on your resume. What I'm saying is

it's certain ways you go about getting a job. It just is. And you're going to have if

you have no tech experience, do you put on and it depends on how you do it. It depends on how you do things. I told you

guys earlier, let me show y'all again. I kind of made this thing for y'all. Let me see.

I got it for y'all. Let me get it. So, let me show you where word

and we fa to finish up um some stuff today. So, don't sweat it. We got time. Plus, I'm going to give y'all a new lab.

This is what's going to go on your um resume if you don't want depending on how you

want your resume to look. Let's put it like that. Some of y'all might want to actually put some experience on. If you

do, you know, we just have to work that out. But what I'm saying is, as you can see,

this is a lot. So, we're we're, you know, changing some things,

working on some stuff. All this is stuff you guys are going to mess with or or should be messing with. You know what

I'm saying? And so, you should be deadly enough to kind of dabble in that. I can take this off. Obviously, some of this

stuff I'mma take off. All this ain't going to be for everybody's resume. But this will be a heck of a resume.

This will be a heck of a resume if you put this out. If all this was on your resume and you out there looking for a

job. Yeah, this a heck of a resume. You'll be like, "What is this?" The the Lifting Veil IT Academy, you know,

apprenticeship program. Okay, man. This is impressive. Well, so tell me about it. There you go. And I'm We'll talk

about that. But that's what's going to go on your resume and it should go on your resume regardless whatever you put

on your resume. Now your resume shouldn't be but two pages at the most but depending on how you set

your resume up that's different. A lot of people don't have no resume. So it's two ways we do it. This is one of them.

The other way is the down and dirty way. [laughter] You know what I'm saying? But however however y'all want to do and

that's what I talked about in here. And I told I think I may have told you guys this where I started a project and a guy

um I was working with this guy Indian guy named Ravi. He we went to lunch one day and he sat there and he broke the

game down. He he really did. And I knew why I know why Indians dominate tech now. It has nothing to do with them just

being smarter than us than Americans or black people. What it is they have a system. They have a way they do things

over there that we don't know about. We don't know that they have you could pay a guy to go sit down and take a

snowflake architect certification. I can send a guy a guy could be a certified snowflake architect in India. If you pay

that guy, let's say, you know, $1,200, he go sit in there and take the test for you with your name. And the guy that

runs the place, he gets a part of that. He get you pay $1,200, he'll get $300. The other guy get 900. He takes the

test. He passes it, but it's in your name. So now you're a snowflake architect.

This this is what you're dealing with. Then you got guys that um you pay for like a doctorate or a PhD or I mean or

you can pay for like a master's in computer science. Literally, I'm talking about official college, official

government stamped master's degree signed. You can get that $800, $1,200. This is the type of stuff, you know, and

so I'm telling you, am I saying that? Well, you need to cheat because they cheating. No, I'm not saying that. I'm

just saying that it's dumb. They dominate the field for a reason. Then on top of that, I had a guy the other day

and I'm at the final interview for this job. But man, the guy changed my resume all the

way around. Man, I have not touched Oracle for real in years. I did some stuff with Oracle last year though, so

he put that on my resume, but then he changed it around. And I had to go look at what he put on there cuz I forgot.

I'm like, "What did he put on my resume?" I done interviewed with these people three times. They hadn't really

asked me any technical twice. They hadn't asked me any technical questions. This is sometimes it's like that. Some

jobs these folks be paying out $95 an hour. They will sit up there and ask you, "Tell me about your past." So I

tell them about what I've done. And the next thing you know, they they I done went through two interviews and these

people, you know, you know what I'm [laughter] saying? And I'm like, man, y'all ain't ask me

nothing about Oracle. You know, this the type of stuff you see. And so, and then the jobs that

might be paying $35, they want to know, you know, you know, what's your blood type?

You know what I'm saying? So, don't get don't get intimidated, guys. It's ways it's tricks of the

trade. And it's always at what your comfort level is. I don't try to tell people, "Look, man, let me just put some

on your resume." What do you feel like you want to have? Like if you want to put those bullet points we just saw then

so be it. That's what we'll do. If you want to say no I want to I want to get to the bag man. Just you know change

this around. Make it say all right. This what you got to say. This is how you got to word it. You know it's it's whatever

you guys want. I let you guys make your own choices. All right. Let's get to it. Man talked enough.

Let's see. So, we already did this one. Close that. We got two more left to do.

Got this one. And we got this one.

There we go. All right. Now, we've already talked about this before. There's a process called normalization

which is like we said the removal of redundant data and dependencies uh and you know and to to basically

remove because if it's redundant then that means it's in in the it's in three or four places in the database for the

same column which is cumbersome. You don't want that. You want everything to be centralized in one location. So if

your employee ID is 3542, why would you want it to be in five different places in the database?

Now it can be as a foreign key in six to 10 different places, 20 places over the database, but it's a foreign key

pointing to the primary key. So the primary key for the employee ID for 3542 needs to be in the employee table. That

is normalization because if it's in the employee table, it's in the customer table, it's in the location table, it's

in the manager table, it's in the but and it's got primary keys on all of them. Then not even primary keys, it's

just there as a a central place and it's it's it's separate and it's not a foreign key, then you're kind of wasting

your time. So you want to do what's called denorm I mean normalization. So right here we says hey what is the rule

to be in first normal form? Now remember guys and we talked about this. Let me show

you that was these. Let me go back right here. It says each cell

is to be single valued because if we look up here it had two values right?

So that's first normal. So it says each cell is single valued entries in the column are of the same data type. So

when you go to first number form everything needs to be the same data type which that's what they did right up

here. You had something that's different. You got a phone number but then it right

here is just tollfree which that's not a phone number. So it kind of worked out the data. You kind of clean this is what

this would be cleaning the data. You would have to clean that because obviously that's what they call cleaning

the data. Right. Then right here it says rows unique rows are uniquely identified.

They added a primary key. Right? A unique ID or add more columns to make it unique.

You know what I'm saying? So that's first normal form. Now we're going to go back over here.

What does it say? says a table is in first normal form if and only if all columns contain only atomic values

that is each column has only one value for each row in the table. So that's first normal form, but

obviously we added a little bit to it, right? We g we added a little bit because it's a little bit more than

that. Now what I want you guys to do really, you can just this is this is what you can get on an interview and

you'll be good. Truth be told. Now, when they talk about normalization,

what they talking about is this paint. See it? Oh, well, hold on.

So, when they when they talk about paint, make this bigger.

And let's make this Let's do it this way. There we go.

All right. So, I'mma go up here to the corner. And when they talk about normal talk about normalization,

bring the data in this way, right? This a spreadsheet. It's Excel spreadsheet, right? We're bringing in

a bunch of columns. Oftent times when you working with a company, they have systems, right? They have

something called enterprise relationship. What is it? Processing ERP enterprise resource planning. That's

what it's called, right? And what it's talking about is enterprise company resource planning. So they have a ERP

system and that system basically talks about how they got 30 different styles. We might have one department that

department is working with um Tableau I mean or they working with Hyperion right then another department they're

working with Snowflake another department they're working with SQL server another department they're

working with Oracle everybody wants to put that data into one central place you want to create something like a data

mart where all the data is so guess what you create something called a like a repository with all your data but guess

what everybody needs to print that data out and send it well everybody got different forms, different ways they do

stuff, but you put it out, you get it all in the form of Excel spreadsheets or you might get a CSV file or you might

get a text file, right? Or you might get a a JSON file, depends on how you want it, right?

Whatever, right? But they print it out. Well, when they give you that, all that data is in different they might have it

all in one table. like the the production like the the manufacturing department will have a

table in it. That table they gave you a one file with everything in it. So it's got the employees. It's got the

customers. It's got the data. I mean the the products. It's got all that's in one document. They spit it out and gave it

to you cuz people are sloppy like that. They lazy. They So now you got to denormalize all that and build out this

database. Or you might have, for example, you might not have that. You might have 30 different departments

giving you stuff. And yeah, they might have it spaced out a certain way, but you got to now make some sort of like

sense of it and put it all in one table for not one table, but one, you know what I'm saying? Like say you got a list

of employees. Well, they might call them employees over here, but and they got a different ID, right? They got a ID for

the employee ID, but then over here in this other department, they don't use that ID. They use something else. they

might use um a a a number that they assign to them instead of a a last for their social, but it's the same person.

I mean, you got that type of stuff going on because people when they build systems, they just do something for

their particular convenience. They don't they may not you got to think they probably didn't even have this other

department at the time when they started doing this. this company just grew exponentially, which you gonna see that

a lot of times when you interviewing with companies, they growing and they're like, "Man, we stuff is getting thrown

in there. We didn't have time to really set it up right. It's not consistent across all the systems and we got to

figure that out." So, this is where a lot of this normalization comes in where you're

creating a data warehouse and in doing so, you need to set this stuff up in third normal form. That's

primarily what you're aiming for. Third normal, right? Now you got this thing called

second normal form. Now what is second normal form? It says a is in first it says a relation is said to be in second

normal form in a database management system or relational database management system. Right? when it is in first

normal form but has no prime attribute functionally dependent on any candidate keys

keys proper subset in a relation that is just all over the place let's take this over here

so now we going to second so it got to be in first normal form and it says all attributes have to be dependent on the

key so everything over here needs to be dependent on the the primary key.

So whatever newsletter that they got is got to be matched up with the customer. Whatever price they paid got to be

messed up with the item. The price the item has a price. So that kind of matches up. The supplier can be broken

out. We'll we'll take that over. Right. And this is see there. So they got the junction table right there.

Right. dictating which particular customer has which particular product. So that's second normal. Everything's

dependent on the primary key. And then third, well that's fourth.

Where's third? There you go. Third. All fields and columns can be determined only by the key. So the item

is here and the supplier is a foreign key going to the supplier table

which is a primary key over here. So you split the supplier out but you still have that correlation between the two

where it's telling you which particular product and so on let me tell you something once you kind of have seen

databases you'll just know where to put stuff. It's weird. This doesn't make sense. This needs to

be broken out into its own table and then we'll just use a foreign key. See, now y'all understand why the first thing

I taught y'all was primary key foreign key relationships cuz that's everything. Now you

understand joins. You can understand how to swing through all this and grab whatever you need.

Y'all see that right? You can pull anything you want. If I want to know what supplier

is being used to uh give this particular customer their product and what product did they buy? Well, you can look you can

look all that up with a select statement. You just joining these tables

and you'll swing through this other table just to get to this information over

here because we want the supplier. We want their name and we say what product. Well, this the

products that they bought. So, we'll get this, right? And then we'll swing through here

because we want to know what customers will get the customer name. So, we got to join all all all four of

these tables, which means we're going to have three joins. Four tables, three joins.

All right. You got a question, Carter? >> I have one. So, you mean tell you you

could join more than two tables at a time at the same time or? >> Yeah, you could join 30 table. Think

about it. Remember I showed you? Hold up. Where is it?

Let's see. I'mma just script this out so you can see.

>> All right. >> Look at all them tables joined together. >> I mean, this is how it makes sense. This

this is how it makes sense. That way you can swing through and grab everything. >> All right.

>> Now, when you go on a a project, you gonna see you gonna see stuff way longer than this. This is just this is

child's play. Then you might see some with 50 different then they might do a derived table down there. You'll see all

these tables joined together. Then they'll do a derived table. They'll do a open parenthesy select get a table of

alias and join to that. Then it got a sub query in there. I mean it's going to get you know so that's why I'm telling

you to learn how to use these constructs individually because if you know how to do that then you can join all this stuff

up and it all makes sense. I could keep going and build a hund and join a 100 tables. So it doesn't matter.

>> You making one big data set. Next question. It says the first normal form. It says right here, what's the

difference between the first and second normal form? It says the first normal form is used to eliminate redundant

records in a data database table. Second normal form is used to make sure that the data dependencies

sure about the data dependencies in in a database table. So, seems like to me what they're saying is first normal form

removes redundancy and second normal form makes sure that all the columns in the in the in the table are dependent on

the primary key. Then you got third and that's the main one that I want y'all to really be aware

of. Right? And third is slide up. It says what is the third normal form in a database management

system? A given relation is said to be in its third normal form when it's in second normal form but has no transitive

partial dependency. Meaning when no transitive dependency exists for you know what I ain't got time for all this.

What we gonna do? We're going to go over here.

Third. There we go. So, it's going to break it down real

simple because that's what I like. And I'mma probably make some new note cards. Let me see if I can do that right quick.

Can I? Where my note cards at? I make some new note cards. Where they at?

It's a It's a W. Hold on. Nope. Nope. Nope. Nope. Nope. I could have swore.

Where's that website at? I know I had it in here. I thought I had it. Hold on.

Uh, let's see. Hold on. is this. Let me see.

It's not Canva. It's a website. Let me see. Is this Let me see. I know it when I see

it. That's not it. Nope. Golly, I had it saved.

You can tell when they want money. Let me see. Best card maker. Is Is it No, it can't be. It's not this

one. No. Yeah, I think that's it. This it right here.

All right, let's get this uh let's see. Okay, think of normalization as

clearing. Okay, so hold on. We going to copy all this. We going to put this in the Facebook group first.

All right. So, let me just go over here. It'll be easier. So, up top,

think of normalization as cleaning up your bedroom. You want everything in the right place so you can find it easily

and don't have 12 copies of the same thing lying around. Right before normalization is messy, right? So you

got student ID, student teacher, teacher phone, subjects, right?

And it says there are a few there are a few problems here. Let's clean them up once at a time. So it's right here. It

says one thing in each box, right? So you got your subjects you got it split up right here. Math and science, English

history. So they split that up, right? Put one in each line.

Says the two things stuffed in one box. They saw it. They split it up. Billy got two rows now. And Sarah got

two rows, right? One thing in each box is first normal

form. Second normal form. Everything should be belong to the whole key. So this sounds

scary but it isn't. Imagine we have. So it's right here. Student ID 1 one and two. We're looking at all this.

Everything looks like okay. So then right here it says our key is student ID plus subject ID.

So this is what's called the what when you got two columns making up the primary key. What's it called?

You have more than one column. Talk to me. >> That's correct. It's a composite key,

right? So that's what this is. It's a composite key, right? It says, for example, on is okay. Right. Says,

but look at the student name right here. says, "Do do I need a student ID and

subject ID to know Billy's name?" No. Student ID is one already tells me that the student is Billy.

Same problem with subject name. Math whatever. So it's saying that hey subject subject 101 already tells me

that the math math is the subject because that's the subject ID 101 and 101 down there.

Y'all see that 101 is here. That's that's math. One is here. That's Billy. One is here. That's Billy. Y'all see

that? Hello. Y'all see that?

What you got? M Swan, what you got? You got a question? Hello?

Guess not. Anyway, so what they did was Go ahead. Go ahead.

>> No, I said it took me a minute, but I'm good. >> Oh, okay. All right. So, right here, it

split it split everything up. Everything's over here and it split it up because you had redundant. It was

redundant. So, it moved it out and said, "All right, everything's dependent on the primary key." So, we made the

student a table. We made the subjects a table. And then you got the grades table with primary key, foreign key over here.

These are foreign keys. Now student ID is a foreign key from the student table. Subject ID is a foreign.

Split this up into three tables. Say kid rule is the key has two pieces. The information

must be must need the whole key. Two p that mean if the primary key has two pieces it must need it.

If it doesn't, then it's obviously and because you were able to split that up, it didn't need it. Right now, we're at

third. It says don't um about something else. So, you got student, student, teacher, teacher,

teacher, teacher. Split it up. Make the teacher a table, student a table. Real simple.

So now it's just telling you everything right here. Now I'm I'm gonna go ahead and jump on this lab. But before I do

the lab, I'mma get this other one too. We got to make some note cards. So we probably going to go over about 15

minutes. That's cool though cuz we got to redo this. Carter, you got a question?

>> Yeah, I got a question man. Uh before you go any further with normalization, I I remember you said a term uh

denormalization. What what why would you do that >> back in other Yeah. Why would you do

that? Um reporting it >> reporting.

So when you're talking about a database that's set up a certain way for pro um um transactions, if it's a

transactional table, you want it uh normalized, but then when you want to report, you would a lot of times go in

de in the direction of denormalization. >> Okay? >> And we g we going to cover that in a

second, but >> All right. So,

let's see. He gave me a bunch of cards. I don't need that.

Three cars total. So and we going to get the answer

the third. Okay, this is actually pretty easy. The answers are better than those real tech

like convoluted answers I was given in the other one. But it's cool.

That seems a bit better right there. Let's preview. Let me see. Let me add some more stuff.

Yeah, let's do that. Let's add. There we go. So, we'll do this one.

I'mma type one. Why? There we go. That's a good one.

So, I'm give y'all both of these. Copy. There we go. That makes it a lot better.

I'mma probably put put this here. Put all that there. There we go. All right. Uh,

what do I do now? Download. That's it. What do I do? There we go. View PDF.

There we go. I think that's it. Boom. There we go.

Now we going to put this in the group. Choose a file. Here we go. Boom.

All right. So, we got that. I'mma do one more now. Explain

the difference between Hey,

actually. There. There we go. That's better. Okay. So, now we're going to go and make

it simple. Right. So, right here. And the reason I'm doing that is because we got these last two questions right here.

The difference between a star schema and snow schema snowflake, right? So it says the table shows sells store sells toys

and we want to answer questions like how many toys did we sell? Which toy made the most money? Which so this is

reporting which store sold the most. Both star and snowflake schema helps us organize the

information. The difference is how many boxes are used to organize it or tables. That's what it's talking about. Star

schema keeps it simple. Imagine we have one big table in the middle

and we got, you know, the sales table. Y'all seen me do that a bunch of times. Around the sales table, you got the

customer table, the toy table, the store table, and the date. It looks like a star.

Now look at your toy box. So you got the toys here. Everything about the toy is kept in one box.

Batman is a toy. His brand is Mattel. His category is action figure. We just keep all of that together.

That's a star schema. Think star equals fewer boxes. Keeps it simple. Snowflake schema.

So now somebody says, "Wait, I want brand and category in their own boxes." So now you got Batman got a box, toy

box, you got the brand box, and you got a category box, right? So we want to make three tables.

Toy, brand, category. See there? Three tables. Now it's starting to spread out like a

snowflake. It's a little bit more complex, right? Here's the big difference.

Imagine your mom tells you, "Hey, clean your room." Right? With a star schema, you might have Batman, Barbie,

basketball, Hot Wheels. Everything is easy to find. With the snowflake schema, you might have

toys, action. So, you got the toys as a category. You got action figures, you got Batman. Dolls, you got Barbie.

sports, you got basketball, everything's split out versus it's in a simple one box,

right? The snowflake is more organized, but you have to open more boxes to find stuff. This is the difference right

here. It says, okay, easy to find, right? Star Starflake Star schema got fewer fewer boxes, right? Fewer tables.

Snowflake is more complicated. joins. You got fewer joins for the star schema, but you got more because you got all

them boxes, all them tables, right? Reporting easier to grab stuff if you got less joints where that

denormalization comes from. That's what I was talking about, right? And it can be more complicated when you start

talking about a snow schema, snowflake schema, sorry. So, you got dimension tables. The

dimension tables are less normalized and they're more normalized and more broken down. with the star I mean snowflake

schema and PowerBI loves a a snow I mean star keep star schema. So I'mma give y'all

all this and let y'all just go through it. It'll break it all the way down. But that's the gist of it and I'm going to

draw it out for y'all real quick. So what I was just basically doing, let me zone this back out a little bit. This

is getting crazy. do this like this, right? So, you'll have a table. Boom.

Y'all seen me do this a lot. That's a star skin. Primary foreign key. Everything real

simple, down and dirty, right? But then snowflake bring this over.

Snowflake is like this. So then you got everything in the, you know,

still got that star in the middle, but now it's more denormalized. That's all you'll see. Now, is a

database always perfectly set up like this? No. you open up a database and you look for

something called an entity relationship diagram. What you'll see is it don't ever be just perfect like this or like

this. It's always somewhere in the middle. That's the difference though.

This is more for transactions cuz it's more normalized. This right here is more for reporting.

That's how the game go. All right. So, we kind of rushed today. Let me go ahead and jump on this lab.

I'mma give y'all this lab because that's the main thing I want to do. SSIS.

All right. So, this is lab number three. I'mma take this out here. Just control A.

Let's put this over here. All right. Lab three. Going to create a table

variable. This time you're going to insert into that table everything from dbo.st staff twice,

right? You're going to use ranking functions to split it into partitions and remove the

underlining duplicate records only if the count is greater than 5,000. So, how did I Wait a minute. So,

I need a loop. I didn't do this right. So I'm going say with

a wow loop eight times.

There we go. So you're going to create a table variable. You're going to insert the

into the table everything in dbo.st staff with a while loop eight times. So it's 1004 records.

So you'll have 8,032 records. Using the ranking function, you're going to split into partitions

and remove the underlining dup. Okay. So split it into partitions by

you're going to split it into partitions ranking it. You're going to rank it by ID.

I'm trying to think. So you're using the ranking function split into partitions. Ranked

not ranked. I only use rank fun. We're going to use Trying to think.

You going to have eight. You know, let me make something else up. I don't like this.

I messed this up. So, y'all gonna keep this right here. I ain't worried about that. And then

otherwise keep inserting by using a while loop using the rank function. Okay.

So let's get rid of this. I messed that up. And I remember every every year I do the

same thing. So create a way to use a table

variable. Use a loop to insert After that, use the ranking functions

and use the ranking functions. Uh

now should I say ranking? I'm going to use row number. I'm going to use row number

partition by um yeah, we'll do that. Let's see if it understand what I'm

talking about. I just threw it together. Let's see. Okay. I don't want the

Okay. Scenario. Yeah, this table variable created loot. It's making

it row number challenge. Okay, y'all. Questions and everything.

Cool. [snorts] We'll deal with this. We'll deal with this Saturday. By the

way, guys, I'mma play an interview for y'all. So, did it

No. Okay. Y'all heard me. So, Saturday, if you're not here, you definitely want to listen to the recording because

Saturday I'mma um I'mma definitely put y'all on with a um with an interview and y'all will see

what time it is. Y'all will see I ain't playing. You like, man, he really ain't lying. This this stuff he teaching us is

actually what these companies want to know. So

you'll see. You shall see. Anybody got any questions?

Actually, let me just Everybody good? >> Yeah.

>> I don't know. Hey Can take my number down, U, fam, because I don't I don't know your number off the top of my head.

Let me uh it's on the website though. It's uh my number

is is right here. It's right here on on the front of the website. So, when you get a

chance, just call me right after class. But uh I'mma look at this because this gonna be

a little bit more in involved. But cool, man. I gave y'all a little bit more work, but this is not bad. I mean,

y'all got a little bit more work to do and that's cool. We'll go through the lab next Tuesday.

Well, since I gave it to you Thursday, I'm gonna give you Thursday. So, we gonna fix this Thursday.

Um, once we go through thing, I'mma look at some stuff, make

sure I covered most everything, and then we going to go back all the way to what's a relational database.

So, we about to start over with SQL. So, if you lost, good, cuz we we going to start all the way over.

And this time, you guys should be able to fill up some of the gaps of stuff that y'all missing.

So, that should be that. All right. Sorry. went over a little bit today. I got to talking about all the class stuff

that I'm developing. So, that kind of took away from it. But, I think y'all will be excited about that. I, you know,

I think this is uh this going to make a difference right here, man. For y'all, this is going to really put a lot of

y'all in. And if you a dog, if you really trying to get it, you trying to get to the money. Y'all see these

numbers. I mean, 160 is cool. I mean, I make that. That's that's pretty comfortable.

You know what I'm saying? But I'm trying to get to, you know, to half a million. [laughter] I'm trying to get I'm trying

to get two or three projects at the house and just be and just stack up and just and put them in a headlock and

just, you know. >> Is that still possible these days, man? The the job stacking.

>> Yeah. Yeah. All day. All day. The thing is >> Yeah. People do it all the time. I mean,

what's his face? Uh Theo Theo do it all the time. In fact, I talked to the people from um Data Engineer Academy.

They got people doing that making getting 600. So, it's doable. The problem that you're going to run into,

do you have the skills? So, this this is going to cover this thing is going to have you in in the mix

for all this stuff. It's going to put you in the mix for it. That's why I'm doing it because you can

come to one place. like you know how many thousands of dollars you going to have to pay if you go to data engineer

academy they they told me they want $25,000 so you you not going to get this and

then on top of that and it's self-study it's crazy they got they got once a week you talk

to a guy you talk to a guy once a week and he tell you a little stuff the rest of the week you studying on your own and

they want 25,000 and they like oh we'll help you get a job I know how to apply I'll apply for 30 40 jobs a day myself I

don't need them to do that. That's not really a flex to me. So >> like colleges, what colleges were doing

during co >> Yeah, it's just a waste of time. But look at it. All this stuff, man. This is

this is money. These people and I said remote. Did I say remote? Yeah, all these are remote.

So I think no, I didn't. This is remote right here. So you can come here and hit the remote

jobs. There's people working remote. I got one job I interview for next week. The guy was talking about

one day a week. But that's cool because if the city call me back, which I'm supposed to be going back to work with

the city. I already got their laptop. I hadn't even turned it in cuz the lady say she going to call me back. Well, she

called me back. Guess what I'm going to do? I'mma just work. I'mma work that job and

I'mma work there. I'mma just double up. Yeah, you can work. You can work remote. I mean, it takes work. Obviously, it's

gonna be more people out there competing for those jobs and stuff, but me, I don't really care. I'll do a hybrid

role. If it's if it's paying, I'll do hybrid. I got 18 years. So, I, you know, I'll take a full-time a full-time

because I hate going in five days a week. But I go in twice a week if you you know, I need I need a couple hundred

though to do that. I can't go in for no, you know, 110. You know what I'm saying? I don't even

want a job. I ain't going to say a I take whatever when I'm unemployed. But what I'm saying is

eventually me I'm trying to get up out of it. I ain't standing at a job like that. So

anyway guys, we got a uh we got class Saturday and I'm gonna play most of Saturday is going to be about the

interview, truth be told. And then I'mma review I'mma look at what we've covered. If I got some gaps or

something I want to cover, I'mma cover those Tuesday. Then we starting over. Thursday, we doing the lab again. We

gonna fix the lab. All right. All right, guys. And like I said, man,

by the time New Year's get here, I mean, not New Year's Christmas, I'm gonna really have that course ready. So, I

mean, you gonna just you be to just go through you guys ain't going to really have to worry about SQL because I'm

going to be done and taught it to you. And you gonna probably know some of that data. You gonna probably know the data

warehouse stuff because we going to go through that. I'm gonna go through the courses material probably around

December. I'm gonna go through that. We gonna go through that data warehouse stuff. You already kind of getting some

of that stuff anyway. So anyway, God bless me and I'll see y'all uh Saturday. Y'all have a good

>> All right. Good night, y'all. >> Chill, man. Take it easy. Thank you.