SQL Job Interview Prep: What Companies Really Ask (Watch Real Calls)

How's everybody doing? >> Morning. How you doing? >> I'm doing all right. I'm doing all

right. Let me go ahead and stop sharing and I'm going to share again.

Share the whole screen. So today I want to show you guys something

because you guys probably aren't aware how resumeé prepared you guys actually

are, how job ready you actually are if you have been studying. But even if you haven't,

uh I want you guys just to see specifics. Let me go ahead and see what this is.

Hello. >> Hello. Uh, is this Jennifer? >> Yes, it is. How can I help you?

>> Hi. This is Pat. Actually, I got your contact from Jordan Andrews from

>> I skip some of the stuff. I want to get to the questions because that's really what we want to see.

everything. >> So, a lot of times when people call you for interview, they're gonna ask you a

bunch of they're gonna say a lot of stuff like, "Oh, this is what we do. I lead a team. Da da da da da. We're

working on this. We're working on that. This is my colleague so and so, so and so." That's how they talk. I want y'all

to >> data warehouses. also include a >> so how about like you know why don't you

give us some you know overview of your experience of experience and >> sure so um I have experience um within

>> now she has no experience by the way >> SQL server many aspects of the SQL server data tools including using SSIS

for um data loads from servers uh into staging tables and finally into data warehouses. Um I have experiencing using

SSRS to pull reports from data warehouses. Also I have experience using uh TSQL uh

the constru the TSQL construct of um you know the SQL language uh within uh SQL server management studio. Uh my

background required me to create store procedures necessary to create the data sets uh for required reports. also to

modify any existing store procedures as needed. Um, and also to if there were any current package implementations that

handled the ETL loads just to make sure that all that data was loaded properly and if anything wasn't loaded properly,

find out why and if need be manually insert that data into the database. >> Okay, that's good. That's that's very

nice to hear. Um so what was your background like have you started like SQL development or you were were you a

programmer initially to begin with I see like you're working from 2015 onwards were you out of college from from there

or >> yes >> what was what motivated you to get into

the data business >> I was actually a freelance designer doing graphic design and web design

um okay I was you know always looking to brush up on my skills and a lot of my family, they're actually um backend

developers and um I saw a course on linda.com and decided to take it uh for SQL and realized that I had a love for

and passion for SQL. So, you know, I just devoured everything that I could and look for u my way into uh working

via friends and things like that uh within the industry. So, that's how I started. I actually made a pivot from

doing more of the design aspects. >> Okay. Okay. That's that's that's interesting. Um so you you've been

working on this uh company which is it own castle material. >> That was that was the client. Yes.

>> Client. Okay. Okay. And um is is this project completed or you still working on?

>> No, the contract has completed. >> So you're more looking I mean you're working on a contract piece.

>> I am. >> And you're working with this. Okay. >> Okay. Um so I mean I I have seen a lot

of work you've done in this particular almost like a two year time period. Seems like a lot

of work. What is essentially data flow here like what what kind of from a domain not not to specific to the

domain but like from an implementation technology side of it what's the platform what what what do you role in

that process? >> Yes. So um again like you know if any uh packages needed to be developed

um that would pull data from historical CSV files um and load those datas into the per into the appropriate uh staging

tables and finally into the data warehouse. That would be my role also um to create any reports as requested or if

I need needed to create any ad hoc queries. Okay.

So, uh it seems like you worked on a lot of um like stroke procedures, >> right?

>> That's what I see. >> Um so, what's been like, you know, I mean, I'll

just not get into the nitty-gritty details, but like what's been your um you know, your friends are like, you

know, or like what do you think is single? a couple of interesting um features of TSQL what you like most I

mean during the course of your programming uh years you must have done something improvising in TQL what what

is that what do you think is like most thing that you have worked on in the SQL and why do you think like good features

to implement >> I've had to work with various constructs of the language

>> so he's asking her basically like what she's done this is something that I would tell you guys when I give you guys

stuff on your resume, like when I give you guys what I told showed y'all the other day, y'all definitely need to have

that memorized. You need to know how to talk about it. You need to know how to speak.

And you really kind of need to touch everything that's on there. So, if I give you something, I give you like a a

long list of different things that you say you've done, then you definitely need to know how to

actually touch everything that that's on there. That way it's not it's not a situation

where you sitting there and you saying you did something and then they they looking and it's like okay if you say

you did this then what about this? What about that? Tell me about this. Tell me about that. So you should know this

stuff. That's the truth. So you want to you know take your time and really touch

everything that that you see. So, it's just, you know, um, so as things are being developed, I want you guys to

just, you know, let me see if I can see I got it here. So, that's probably not it here. So, you

guys definitely want to be able to like this is my course. I kind of set set my course apart separately.

This capstone project right here, that's basically what you're going to be talking about.

So by the time we get done this is going to be you know they're going to give you a scenario

you know actually is it says is a project that uses every tool prior every tool from the prior course in this

program wired together in a single working pipeline says the business process this capstone

models manufacturing work orders and why it's a genuinely new scenario, not a repeat of sales process. So, it's SSIS,

SSRS, development or procurement process, data modeling and data warehousing already built elsewhere in

this catalog. So, you going to already be built stuff. You got to you got to do this stuff, man. I ain't saying you

listen, you ain't got to do what I say. You can do what you want. You could really, you really could just study the

note cards, practice the scripts and do the labs that I give you and that'll be enough to get a job.

But you want to get on these interviews and really wow people. You want to talk about stuff you've done, especially

depending on how you word your resume. So if you word your resume like that you've actually done stuff then you

definitely need to you know but if you saying you went through the apprenticeship program you

need to be able to talk about this stuff authoritatively like you really know and really go I mean talk and go into detail

and say yeah so I did this and I did that and I was able to discover in the data there was there was a business

problem and I was able to come in and figure out why this was going on why that's what I'm talking about. So, you

got to be able to, you know, talk about this stuff. And that's what that's what I want you guys to be able to do. So,

just understand. Um, and I'mma probably, you know what? I'm glad I said that.

Let me type a note out. I'm glad I said that. So, I'm going to add that. I'm just

setting a note for myself to be able to do that. But the reason I'm doing that, man, and is because I want you guys to

really be able to talk about this stuff, man. I want you to get on these interviews. And this the advent of this

new stuff that I'm developing is really going to set you guys apart. make you guys a lot better as um as developers.

So, it's not just going to leave y'all hanging where you you stuck and you you trying to explain and you don't know how

to explain. I don't want that. I want you guys to really come in here and just knock it clean out the part. And so,

this is my course. This is pretty much everything I'm teaching. Um this is a new part right here that I'm

going kind of go through with y'all, but it's not that big. It's only 39 lessons. Um, so it don't take that much. The

these shouldn't take that much. These take like couple of weeks to like I can run through SSRS in about two and a

half, three weeks. It's really not that hard. Um, SSIS, I'm going to take a little bit more time just because I

already know what it is. I know this is one y'all gonna struggle with. PowerBI, we gonna go through that, you know. Um,

but these are the main ones, man. I'm not really adding Tableau cuz I I've worked with Tableau but it's been a

while and I don't want to just be in the middle of class trying to look stuff up and stuff. PowerBI I'm kind of

comfortable. I work with PowerBI for the last two years actually. So, but I want you guys to really get

familiar with this. Let me keep going. But I just wanted y'all to see that. Let me get let me get off this. If he ain't

gonna ask no questions, let me see if he gonna ask some real tech questions. um and so vast and so heavily logic based

um >> is like a better you know um running procedures like doing data processing

what is the uh you know the biggest you know data processing done like let's just say I'm saying perspective

hypothetical is transaction processing table um which has like millions of records and then you have to kind of you

know go through certain business tools and apply filter conditions do the data processing

which you when you are doing what was the biggest cables or data you have

>> yeah I don't I don't want to he he really just asking her how to what she's done let's see if I can find something

else notice I this is the thing I just looked I just pulled down a few out of my email

a lot of students don't record the interviews, especially if you do it on teams. A lot

of them feel like they don't want to record it. But I'm telling you right now, that's how you actually get win.

You need to see what you sound like. It's like playing a basketball game and not getting it on video.

So then somebody got to sit there and try to you got to come back and tell them what happened. Oh yeah, man. I I

hit I hit 10 points. I had a couple of turnovers. I did it. But see, if I can watch the video, I can say, "Well, man,

you got this turnover cuz you was trying to do X, Y, and Z. you being too fancy. Are you doing this? You doing that? Stop

doing this. I can really tell you, but if you just come and tell me, I can't really help you.

And I be telling people, man, send me your interviews. Nobody listens. It's just how it is, man. It's like pulling

teeth to get people to actually record interviews. And I remember when I first started teaching, a lot of the people

that got jobs were the people that followed directions. That's just the bottom line. And if you

go back to my first class, I told y'all I said follow directions. That's what's going to get you where you got to go.

All right, let's get it. >> Hello, this is Jimma. >> Hi, Jimma. This is April calling with US

Vision. How are you doing today? >> Hey, how are you? >> I'm well.

Um, can you pull the numbers, you know, for >> be no problem at all. I'm just sitting

here >> myself. >> I know people who go out and buy glass

by mountain. >> Oh, wow. Yeah. Materials manufacturing company.

>> And was the reporting functions that you were doing? Were they, you know, were you given specific reports to do or

could it have been all? >> So, a lot of it depending on what your resume they're asking you what you've

done. So now you got to understand like I told y'all and I just told y'all that. So let's keep

>> you know somebody coming to you say >> let's see if she gets some technical questions

>> server from their product vendor or >> are you looking for a strictly contract position?

>> I'm actually open to both. Um, so I just want to make sure because I know some people that I've talked to

>> um, a lot of that I was that was like my first four-way. >> And so for SSRS,

um, is it just the, um, the two years experience that you have with the old >> This is more screening. Let me go back.

Lord have mercy. Let's see. Let's try this one. >> Culture and Boston. And it's conversant

work either we're actually trying to >> right walking that tight rope like what's your development time frames from

I guess and you >> sure um I have a background in TSQL um using

>> so see as you can see they this is the thing what people do is they ask you a question well they come on there they

spend most of the first few minutes as you can see explaining what they do and then they start asking questions about

your background that's actually a time for you to really wow Like if like like if you guys can really

do projects end to end and be able to explain it and put it in a work depending on how you set your resume up.

You can either put it in in a in an environment where you saying hey I work within the apprenticeship program for

lifting the veil or you can say hey I worked at XYZ company and this is what I was doing and I was able to discover da

da da and I helped the end users discover that you know certain things about their data because I figured out

this that I developed reports dashboards I did that's how you can talk >> the SSIS tool and allow for the ability

for you know create the you know the entire system as far as talking to the client and getting the

>> scale of one to 10, 10 being the highest, where would you rank yourself? >> Uh, anywhere between 7.5 and eight.

>> Okay. Can you explain some of the from a querian perspective not really so much concerned on a kind of an administrative

perspective but strictly on a querying perspective some of the um some of the features some of the SQL um query

features that you've actually used example maybe CTE um >> exactly

>> so you guys know what a CTE is common table expression let's go >> um I've definitely worked with CTE when

uh any sort of you know recursion was needed or where there was large chunks of code that I didn't want.

>> You guys are doing recursion in your lab this week because I gave you that recursive CTE at the bottom of your lab.

>> Want to kind of go through and write over and over again or when I had to remove duplicates from a table. Um just

simple things like that. I would use a store procedure. I'm sorry a CTA. Um, a lot of the work was, you know, inserting

records as needed, updating records as needed. Um, nothing super complex. Um, but that's what my basic day-to-day uh,

SQL skills involved. >> Okay. >> So, give me so I brought CTAs as an

example. Give me an idea of some of the sort of features used within SQL. >> Sure. like uh let's say if I if I there

may have been duplicates in a table I would use like your CTA along with the row num function um and let's say I

would use that output that as a column called like duplicate count um and as the row num function is given

an assigned value to each column uh anything that had a count greater than one I would just remove that record from

the Okay, it's good. Keep going.

>> Um, let's see. I'm just trying to think of specific like examples. That's the main

one that I can think of using um my CTE for. Um, >> so the more than just CTE, I just

brought CT up itself as an example. I'm just looking for um types of um

>> yeahes and syntactical things within SQL that you've actually have experience, >> right? Well, let's say if I needed to uh

create a store procedure that had parameters uh let's say where the end user just

wanted to be able to select by region and city to generate that report. Um I know a lot of people name their store

procedures SP underscore. Um I try and avoid that. Um I would name the store procedure like database object name. Uh

set the note count on to my uh in my store procedure for efficiency. uh to clear any parameters using you

know the ad symbol and you know uh so that when the end user actually was able or needed to um run that report they

were able to import the values that's needed uh the syntax that I used for creating let's say the column name was

region um I would say where region equals I'm going to call the parameter at

region name or region code, something like that. That's what I would do. >> Okay. Um, any experience with indexes?

Um, I haven't had to go in and manually add indexes or anything like that on a table, but you know that when you create

a primary key uh within a record set, your primary key is automatically going to create a clustered index. Uh, your

index is going bas >> so I mean you you kind of see is there anything they're talking about you guys

that haven't heard before? Obviously, you hadn't got to reports because I hadn't we hadn't got that far in the

course, but she she's really just kind of this is surface stuff. She he's not really asking her quiz it quizzing her

per se. Um, but these are the the actual constructs and different things that I

am teaching you guys. Let's keep going. >> Basically allows your records to be accessed more quickly will be your

database. >> The difference between clustered and nonclustered indexes.

>> I ain't going to say nothing. Y'all already know that. You already know that structured I mean clustered nonclustered

indexes root branch leaf. You already know. >> Yeah. Your cluster index is actually

related to how your records are physically stored on disk within a database. Uh where your non-clustered is

not attached to how the records are physically stored. It's more of data pointers uh using something called row

locators to locate that data. Um you can have many non-cluster indexes on a table >> 999

>> which are created when you use unique keys. Um but you can only have one cluster and index.

So regarding unique keys, what what's the uh benefit of using a unique key as far as the execution of the index

>> unique key constraint? >> It's concerned. >> So if you have a unique uh key on a

table, it will allow you to kind of um speed up the querying process if you needed to find a record.

>> You know how it speeds it up? Um I'm not sure exactly >> like

something else. >> Don't want to mess up nothing. How does a

speed up? Let's see what

says a unique key can speed up queries because SQL server normally creates a unique key index behind it. Right? Uh

let's see that index gives SQL server a much faster way to locate which is pretty much what we already knew

when you make okay so you got this table right here. So you make one on unique email. SQL server creates a unique index

on email. So now you run where email is equal to this. It says without an index

is this. Nope. Is this? Nope. Is this? Nope. Full table scan. And we know that. And it Oh, okay. Okay.

Okay. So it does whenever you use a unique whenever you use an index period. uh the primary way that an index work is

with creating a uh index seek.

So whenever it utilizes an index is using a index seek which we've already talked about. Let's keep going. Let's

make sure that's what it's talking about. SQL server has organized the structure

for the emails and you navigate directly towards it. There we go. As you can see, instead of checking every row, SQL

server can perform in index seek. See there? Just said that. That's probably what he was trying to get her to say.

Everybody with me? >> Yeah. >> I'm with you.

>> All right, let's keep going. >> The logic that the engine is using behind the scenes.

>> Um, >> okay, that's cool. So yeah, what what it does just as an FYI, you know, if it's

unique, it knows when it finds the first instance of a value. If you think how a when you do a join, you do a join on you

the product ID and the line items an order and the order line items. The line items are all going to point back up to

the same order, right? So in that table, your key, you might have ID 127. You might have 10 times in that table

because that's a line item, right? Mhm. >> that can't be unique in that table. If you know it in the order table as 127

that's unique in there, you know there's only one instance of it in there. The uh when you actually run in the search,

when it comes across the first instance because it's unique, it it terminates the search.

>> Oh, okay. Okay. >> But if you if it's not unique, you got to keep going. Now you've got an index.

So it should be pretty efficient to go through all your leave nodes and figure it. you still have to keep going through

till you reach the end of time. >> Ah, okay. So, it's as opposed to the unique, it finds it immediately and it

knows it can stop right there. >> Yep. And another thing too because that's

that's kind of straightforward but I would also if somebody asked me how an index how a nonclustered index or a you

a unique key constraint allows us to access records fast faster then I would actually get into the bit tree.

So you know starting at the root level going down the branches it finds out which branch is is more closer or

closely related to the the actual um information we're trying to locate. And so that's what I would say and it's

using an index seek when it whenever it does that that's called a index seek. So you know that I do think that would have

probably left he got him off her you know but I don't think she doing too bad. So cool that's good. So um

that's by your knowledge there. So that's awesome. So um

how question for you how aggressively if that's the right word or and to you of being able to learn

>> um I'm very flexible. >> When they talk about business processes and or business logic, what they're

talking about is the way they do things. So, I can teach you everything. I can teach you the constructs. I can teach

you the language. I can teach you how to develop stuff. But you need to learn how they do stuff. It's like if you work at

Burger King and then all of a sudden you go to Arby's, you need to learn the Arby's way

and you go from Arby's, you go to work at Crystals, you need to learn the Crystals way or what you might guys

might call White Castle. So, that's what they talking about. So, let me let me go somewhere else though because let me

see. Let's try this one >> and then from or to restructure those

particular records so that they could be um one of the challenges is uh you know when there's issues let's say things

have been redirected to an audit table for whatever reason um and just having to go in and either manually

insert inert those records because they couldn't be inserted or to restructure those particular records so that they

could be inserted. Um that's one of the standard things that would happen from time to time.

Mhm. So like so in SSI sometimes that we have to load data from other data source and it's

through like we have to put data from the table using the SQL query those that we use extensively

on the SQL query bowling. Um so like do you know the difference between the

time table CPE and in the SSI? >> Yes. So uh one thing your temporary

tables is just a temporary object that exists while that connection um is live. Um you know and once that connection

goes your your temp table is no longer valid. um your CTA. You can almost think of it as

>> this is a question I p I posted in the group, guys. This is exactly what I posted in the group. I told you guys

this was an interview question. It just so happened I forgot what he asked her because I hadn't heard this in a while.

But as you can see, they're asking specifics there. This is the thing, and I want you guys to be aware of this.

There is a reason that I put this at the top that they start with TSQL. Most of these

interviews when you go on them, they may have different job titles, but a lot of times they want you to know SQL.

Not every job. Obviously, I've never been on an AI engineer interview or a blockchain engineer interview, but as it

retains anything dealing with data because that's where the money is. you trying to get north of six figures, you

you going to deal with data a lot of times, at least from my experience. There are other ways like certain cyber

security ways to get into it as well. But I'm just telling you like the main thing you want to look at with this is

the uh the sequel the sequel that I'm teaching you guys. So the fact that we done went through all of this, let me

show you. We've gone through this and I've gone through most of this. You guys have seen most of this.

This is exactly what you guys can kind of you know you've already done most of this while loops we covered beginning

and end blocks if else. We've covered all this um asset properties principles

um we didn't we didn't covered this. This is pretty much most of what we covered.

Now even the design fundamentals primary key foreign key relationships unique key constraints we just talked about that

constraints profiler tables y'all see that

first second third normal form normalization um you know one to one one to many many

to many like that and then we get down here this is where we getting into stuff we kind of already

talked about transactional processing versus analytical ical processing databases where we where the analytical

process is where you a lot of times are just trying to read data transactional processes is and I can kind of show you

I thought I put it in here I didn't but that's okay because go back over here where did I put it

oops go back I think it's um did I put it down here

data modeling. So you go right here. See here analytical processing is when you trying to read stuff, select from it

and analyze it. Transactional is just that short-term transactions. But the problem with transactional processing,

if you say, well, why not just analyze and build your reports off the transactional processing database? you

gonna have a bunch of joins because you gonna have 30 40 tables you got to go reach out to to get the data. Whereas

analytical it'll be more denormalized and you'll be able to just grab from one or two tables. So it's going to

be easier for for reading which you going to learn that when we go through here. We going to talk about that.

Now I'm kind of shaky on some of this stuff but it's good because it I do have experience so I will be able to help you

guys. So, we'll go through this near the end cuz it's not that much. This This ain't that much. We can go through this

in probably like about a week and a half. Won't take us that long.

Everybody with me? >> Yes. >> So, I wanted y'all to see this. I'mma

let this keep playing because I want y'all to see that what I taught you is what companies want to know.

a condensed way of coding when you have more complex queries uh that you have to reference and you know another select

statement or such after the CTA um so it doesn't actually create an object um but it allows you to

reference information from more complex queries um if you are using temp tables and SSIS and you need it within in the

same package but within different tasks. Um you definitely want to retain the connection and delay validation so that

the other tasks have access to that temp table. Uh so like what's that

to you to use the time table? Well, um it could be, you know, I guess for like

performance and things like that, you know, if you don't necessarily need to create a table on the database, um you

could just run that, you know, create that temp table in your execute SQL task and use it to hold and store values

throughout your package. >> Okay. What about the like the view? Can we use

the temp table in the view? >> Can you use uh do you mean can you create a view based off of a temp table?

>> Uh yeah. >> Yeah, you can. Uh from my understanding we can. Um views are just virtual

tables. Um, and they're just you can create them off of a number of base tables.

>> Yeah, but table is not a table, right? >> Well, it's an object on a database. So, it has a lot of the attributes of a

real. >> So, she's saying he asked her, could you create a view?

I'm sorry. I'm I'm assum I'm assuming if you're talking about the actual inner workings of the view itself with a

temporary table then the only way that would actually work and I've never done that would probably be if you actually

uh keep that connection going which would be kind of crazy just to have it access be able to be accessed

continually for the view because every time the view runs it's looking for the temporary table because every time a

view run it's running the underlying select statement. So I would probably say no because let's

say something happens and you lose that connection. Now the view is broken. But let's find out

can you create a view using a temp

table. Let's see. It says no. SQL server cannot create a

view create a regular view that directly uses a temp table. This will not work.

Says SQL server will reject it because the view is a parameter database object. See that? That was a trick question. I

didn't know that. while the local object is a temporary session object scoped object.

So you can't use a temporary scoped object to create a uh permanent a permanent database object.

So the answer is no. Let's keep going. a table. Um the only difference is is that when the connection is gone.

>> So she wrong on this one. >> And that just that's part for the course though. That's going to happen.

>> Was gone. >> Yeah. Where it's not physically stored on the database.

>> Can you tell me something about the indexing in the >> Sure. Um so your indexes provide a way

to optimize your queries. Um you have two types. You have your clustered indexes which are related to

basically how your your rows are physically stored on disk. And whenever you place like a primary key constraint

on a column um it in turn creates a clustered index um because of that you can only have one

clustered index on a table where you can have many non-cluster indexes. your non-cluster indexes

they they use a system of kind of data pointers or row locators to find that data.

So again what's the advantage of using the index in a datab so let's say you have a table that has

uh a lot of that has a foreign um you can um you can use let's say you put a unique key constraint on it um and

it creates a non-cluster index instead of scrolling through all of those box. >> So you don't I wouldn't put a unique key

constraint on a foreign key column. Why wouldn't I do that? Somebody tell me

what does a unique key constraint do? What does a unique key constraint do? Talk to me.

Hello. It enforces uniqueness. Is anybody there? Can y'all hear me?

>> Yeah. It makes it makes it singular. Yeah, it it it enforces uniqueness. But when you talking about a foreign key

constraint, you can have duplicates. Let's say sales. >> So if you got an employee ID, that

employee can't just be the made one sale. >> What if that employee made a thousand

sales >> and multiple sales, right? >> So I wouldn't do that. That he's trying

to And this thing a lot of times she's nervous. Now, let me say something. This she got a job like it only took her

about two weeks to get a job. So don't don't look at this like, "Oh man, she's messing up." It took her two weeks to

get a job. She was probably one of my greatest students. As you can see, she followed directions. She recorded three

interviews and she got a job quick. But the point I wanted y'all to see and hear with this whole thing is even she

messed up. This the second time she messed up. See what I'm saying? Now, I can keep

going and play all the stuff that because they're they're going to ask us some basic SQL stuff, but the thing is

you need to understand what each construct does and how to use it. Even I with 18 years, 17 years of experience

didn't know that you could it didn't it didn't make sense actually cuz it say I say you would have to have that actual

temporary table up the whole time. So, it don't make sense. So, you'll get an error.

So, it's not going to let you use a temp table to create a view. You're going to get an error, which is

cool. Shouldn't it shouldn't do that because tempt tables is is temporary and uh you know, a view is a permanent

object and that's how that works. Um, so you know, views are built off

permanent objects, not temporary objects. You guys should know that now. But you gonna see me tell you something.

This is why I tell you guys to record interviews. Now, who would have knew that? She probably didn't knew that.

Didn't know that. But I bet she went looked it up. That's why she got a job. But would you remember that when you're

nervous, when this guy's kicking the tires 20, 30 minutes at a time, you might, he might hit you with something.

So, what you do is you go back, you play everything, and then you find your weak points. Now, you got chat GPT. You can

look stuff directly up. So, you really can get through this. You can improve. So, guess what? Next time she goes on an

interview, I'm going I will bait the person interviewing me by saying certain things and then try to get them to dive

in depth and then I'm going to hit them across the head with some more depth knowledge because I did the research to

show off, which is what I would do. Y'all see that? That's how you do it. You bait you bait and switch. You You go

in, you get an interview, you record it. If you got some gaps, you look those gaps up. The next time you go in an

interview, you try to bake, you say certain things hoping they ask you. I hope you asking me to expound on this

cuz I got a whole saliloquy I'm going to go through, right? But did they Let me ask you

something and I want you guys to tell the truth. Are they talking about anything? I want you guys to actually

answer this. Don't just sit there when I ask this question. Are they discussing something you guys don't know about? Are

they discussing anything I haven't covered? Now, obviously you don't know SSIS,

but you will. So, you don't know how to create ETL packages yet. But are they discussing anything

that I have not told you guys about? Are they mentioning different constructs of SQL that you guys have never heard

of? You know what a view is. You know what a store procedure is. You

know what an index is. You know what a temporary table is. Right? These are the different things.

And I told y'all I was teaching y'all exactly what and that's what you guys have already worked with tempt tables

because you you already using them on your labs. This is what matters.

I'm teaching you specifics for job readiness. I'm not teaching you I'm not trying to teach you stuff that ain't got

nothing to do with a job. It's a waste of time. Why would I do that? That would be a complete waste of your time.

Everybody understand that? >> Yes. >> Yes.

>> Yep. >> And so we gonna pause here because I don't want to waste the whole Saturday.

We probably play some more this uh Tuesday if y'all want if y'all want to hear more of it. Um but I got some other

interviews from other students. I gota I got to dig them up, man. They email them to me. I just got to search. But it's

been a while, man. Nobody really been sending me interviews. They're not. And I've had students bomb real bad. That's

that's those are the interviews I want y'all to listen to. So, I want y'all to see what it's like. I want y'all to see

how they try to hit you. And they do. They try to hit you bad, across the head. They want to make sure that you

know what you know. And they try to ask you questions to trick you. That's what they do. Some people do. Some people

just want to be straight up and ask you straight up questions, right? Tell me how to remove duplicate records from a

table. Tell me the difference between a clustered and unclustered index. Tell me uh what is a a unique key constraint?

What's a foreign key constraint? What's a um uh you know different you know they ask

just ask the basic straightforward questions right um you know how when would you use

a merge statement when would you use a pivot statement when would you you know give me a

scenario okay okay so I want to know all of the top highest grossing movies I want to know the top five from 30

different categories how would you find That's when you use the top function with a CTE or you use the CTE with the

row number function and you would just select from the CTE where it's less than or equal to five

and that'll give you the top five for the row numbers because you're going to group it or partition it by genre. See?

See how that work? I just told you. But guess what? We did that in the lab.

And so what I'm doing is I'm trying to get you ready for certain types of things. And then guess what? But you

going to get out there and they still going to hit you. You still going to get hit across the head with stuff you

wasn't expecting. Just like that question I just saw where they was talking about creating it from

a temporary object. I never really did that and I said it doesn't make sense because you would actually have to keep

that object open and around the whole time or the view will never work. So

now we know that it can't be done. Those are different things. But see, they'll ask you something like that.

It's a little weird question. Or they'll ask you something crazy like how could you create a table and it's empty

without using the create statement, right? What they want to know is you want to select into

and create the table, but then you want to say where one equals two because one never equals two. That creates an empty

table. So little stuff like that. I got asked that I got asked that question one time.

But guess what? You going to go to interviews, they going to trick you. They going to ask you little weird

quirks, questions that you don't know. But you're going to know the gist of it. 80% of it. Eventually, nine times out of

10, they gonna go on a interview and they probably not not every interview is going to do that. They're just going to

ask you basic questions and you gonna answer them. And then it's I got the job offer for a job one time. I I don't even

think I say the video. I was in a Facebook group. I went live when I was walking out the interviews about two

years ago. And I was laughing because I was like, "Man, this interview is so easy. All y'all could have got this

job." It was like 150,000. And I took the job that I got that I just worked where the project just ended, which I'm

actually glad I did because I worked there for two years. But who knows? I probably should have took the other job

because I probably still be working there. Who knows? You never know. But the point I'm trying to make is, guys,

y'all can figure this stuff out, man. You just got to put the time in. Put the time in. All right, everybody

with me? So, >> we gonna call it a day

and we'll, like I said, we'll be back um Tuesday and we gonna get the party rocking, man. So, God bless y'all. Have

a great weekend. I'll see y'all. All right. Have a good one. Thanks, sir. Yes, sir. Y'all take these.