TRANSCRIPTEnglish

Snowflake vs BigQuery | What's Different?

3m 38s745 words107 segmentsEnglish

FULL TRANSCRIPT

0:00

snowflake was my introduction to Modern

0:02

Cloud databases and it's still where I'd

0:03

say I'm most comfortable even today but

0:06

this year I've had two clients recently

0:07

that needed to use bigquery and I'd

0:10

definitely be lying to say that there

0:11

wasn't a learning curve trying to go

0:13

between the two so in today's video I

0:15

want to talk about a few of the lessons

0:16

I've learned working uh between the two

0:18

the similarities differences so that you

0:20

can feel more comfortable working on

0:22

either of them so number one is the fact

0:24

that bigqueries naming conventions are

0:27

unique they're different especially for

0:29

somebody coming from a traditional data

0:31

warehouse background a SQL server

0:33

postgres and now snowflake to me

0:35

snowflake is really simple it just makes

0:37

sense you have objects like databases

0:39

and schemas and all that but when you go

0:41

to bigquery you'll see stuff like

0:43

project and data set now ultimately

0:46

they're they're kind of the same thing

0:48

but at first there was a little bit of a

0:50

learning curve just figuring out you

0:52

know what does that mean so just to make

0:54

it even more clear in bigquery a project

0:56

is essentially the same as a database

1:00

and a data set is the same as a schema

1:03

and when you use tools like DBT you're

1:05

going to use those interchangeably and

1:07

regardless of what you call it on any

1:08

platform really the data modeling

1:10

Concepts and discussions and approaches

1:12

are going to be the same regardless so

1:14

just embrace it and just keep a look out

1:16

for that now the second thing has to do

1:18

with computation and really I'd say even

1:20

more so what it means to be serverless

1:22

because when you see stuff for Google

1:24

bigquery they're talking about how it's

1:26

serverless Computing in a serverless

1:27

database I didn't really understand

1:29

fully what that meant I'd say until I

1:30

started working with it more and the

1:33

biggest place that I saw this is with

1:34

computation so if you're familiar with

1:36

snowflake you make different objects for

1:39

compute so they'll be called a warehouse

1:41

you'll have different ones you could

1:42

have extra small large medium depending

1:45

on your use case and each of them have

1:47

more of a cost have more bandwidth Etc

1:49

when you go to bigquery one of the

1:52

things you notice is you don't have any

1:53

of that you don't do anything with

1:55

computation it just Auto scales for you

1:58

so if you have more up a workload it's

2:01

just going to Auto scale up to meet that

2:02

workload and even more specifically here

2:04

an example is Auto resuming and auto

2:06

suspending on snowflake you have to set

2:09

that feature and that that setting or

2:11

else you know it'll just keep running

2:12

indefinitely but on bigquery that's just

2:15

again handled behind the scenes it's

2:17

serverless it just spins up and works as

2:19

needed there's nothing for you to

2:21

configure or set so that's kind of nice

2:23

just one less thing to worry about now

2:25

the last thing I'll talk about here is

2:26

pricing and cost structure they are

2:29

different because on snowflake

2:30

everything is based around computational

2:33

spend and processing time so if you have

2:37

a warehouse running for a certain amount

2:39

of time that's going to cost x amount of

2:41

dollars whereas on bigquery everything

2:44

is based on bytes scan so rather than

2:46

time it's about the kind of the sheer

2:49

volume of data that you're scanning and

2:50

there's ways to minimize that on

2:52

bigquery which is nice so if you have

2:53

things like clusters or partitions it

2:56

will make your query engine more

2:58

efficient and therefore scan less bytes

3:01

which means lower costs on snowflake I

3:03

guess you could kind of have a similar

3:04

outcome if you had a more optimized

3:06

query it doesn't have to run as long and

3:08

then it won't cost as much but they are

3:10

not exactly the same which again was a

3:12

little bit of a learning curve at first

3:13

but either way you know as long as you

3:15

understand what's going on you can work

3:17

around that accordingly so bytes

3:19

processed first credits and that's the

3:21

difference so as a data engineer it's

3:23

important to be well-rounded and be

3:25

flexible to work on these different

3:26

types of platforms and hopefully this

3:29

has helped you a little bit with

3:30

understanding the difference between

3:31

Snowflake and bigquery thank you as

3:33

always for watching and I'll see you at

3:35

the next video

UNLOCK MORE

Sign up free to access premium features

INTERACTIVE VIEWER

Watch the video with synced subtitles, adjustable overlay, and full playback control.

SIGN UP FREE TO UNLOCK

AI SUMMARY

Get an instant AI-generated summary of the video content, key points, and takeaways.

SIGN UP FREE TO UNLOCK

TRANSLATE

Translate the transcript to 100+ languages with one click. Download in any format.

SIGN UP FREE TO UNLOCK

MIND MAP

Visualize the transcript as an interactive mind map. Understand structure at a glance.

SIGN UP FREE TO UNLOCK

CHAT WITH TRANSCRIPT

Ask questions about the video content. Get answers powered by AI directly from the transcript.

SIGN UP FREE TO UNLOCK

GET MORE FROM YOUR TRANSCRIPTS

Sign up for free and unlock interactive viewer, AI summaries, translations, mind maps, and more. No credit card required.