AWS re:Invent 2018: [REPEAT 1] Deep Dive and Best Practices for Amazon Redshift (ANT401-R1)

No video

AWS re:Invent 2018: [REPEAT 1] Deep Dive and Best Practices for Amazon Redshift (ANT401-R1)

Рет қаралды 25,331

Күн бұрын

In this session, we take an in-depth look at how modern data warehousing blends and analyzes all your data, inside and outside your data warehouse, without moving the data. This helps you gain deeper insights in running your business. We also cover best practices on how to design optimal schemas, load data efficiently, and optimize your queries to deliver high throughput and performance.

Пікірлер: 15

@ericliu1114 Ай бұрын

Excellent presentation on Redshift concepts and best practices.

@chaitanyaramisetti5309 5 жыл бұрын

I am ready to answer any question on Red Shift after this video. Just wow..!!!!!

@lindhe 5 жыл бұрын

Yeah, the videos that Amazon put out on their channel are really high quality for the most part, I think!

@saywhat4229 5 жыл бұрын

what job types will use this? only data scientist?

@CloudyWithAChanceOfData 4 жыл бұрын

Really impressive talk, a must-watch for anyone working with Redshift or considering an AWS Data certification

@timurmukhtarov8462 4 жыл бұрын

Thank you! This was such a great overview! Perfect blend of practical big concepts and best practices

@confused6526 4 жыл бұрын

Excellent presentation. Great skill. You made it complicated thing so simple like a walk in the park. Thanks.

@cristianrestrepolopez976 11 ай бұрын

This is terrific. Best explanation in Redshift by far.

@JoaoSilva-vx4sh 5 жыл бұрын

This presentation was very helpful ! thank you

@Bonus2608 3 жыл бұрын

Thanks. Great experience.

@darkomilovanovic7405 4 жыл бұрын

Excellent presentation. Are there slides from this presentation?

@sherazahmedch 4 жыл бұрын

Brilliant session. Really enjoyed it. From where can I get these slides?

@HosamShahin 4 жыл бұрын

aws-reinvent-audio.s3-website.us-east-2.amazonaws.com/2018/2018.html

@techaztech2335 4 жыл бұрын

Excellent session, the Dedup/UPSERT method seems pretty inefficient, wonder what architectural constraints there are to not be able to do a MERGE or Update in-place.