When
12:45 PM Sunday
Where
Fireside A
Silicon Valley Code Camp : October 19 & 20, 2019session

One key to rule them all! Destroying data consistency and query performance

Have you ever stopped to wonder why almost every table has some ID field as its primary keys? Is it a 'design pattern', or an unfortunate misunderstanding that got rooted? The answer might surprise you...

About This Session

Every beginner knows that every table has an identity/auto increment primary key, supported by a main index. If I told you that these keys that you take for granted, are the primary factor that destroy your database's consistency, performance, scalability, and modularity, you'd probably think I'm crazy. But what if I can prove it, scientifically, and beyond any reasonable doubt? "It ain't what you don't know that gets you into trouble. It's what you know that just ain't so..." Join me on this fascinating journey down the rabbit hole, where we will shed new light on some of the most fundamental aspects of database design. You will experience hands-on how you can drastically improve your database consistency, simplify your queries, improve performance by orders of magnitude, allow for unprecedented scalability, and modularity. Prepare for a paradigm shift. By the end of this session, you will chant with me: "The key, the whole key, and nothing but the key, so help me Codd".

Time: 12:45 PM Sunday    Room: Fireside A 

The Speaker(s)

undefined undefined

Ami Levin

Data tier architect , Self Employed

Senior data tier architect, data modeler, database designer and SQL developer.