fatalmind

I've given this talk on Saturday in Moscow again and it was video taped there. Organizers told me they'll publish the English original as well as the Russian voice over version. I'm keen for the second one ;)

I keep you posted.

X-comment so you get it too:

Quoting from http://Use-The-Index-Luke.com/ (the main page):

Use The Index, Luke is the free web-edition of SQL Performance Explained. If you like this site, consider getting the book. Also have a look at the shop for other cool stuff that supports this site.

http://use-the-index-luke.com/shop

Quoting from http://Use-The-Index-Luke.com/ (the main page):

Use The Index, Luke is the free web-edition of SQL Performance Explained. If you like this site, consider getting the book. Also have a look at the shop for other cool stuff that supports this site.

http://use-the-index-luke.com/shop

That 100GB+ guide has re-appeared at a new URL:

  http://blog.mongodb.org/post/62899600960/scaling-advice-from-mongohq

The MsSQL locking problems is just because snapshot isolation is disabled per default: http://use-the-index-luke.com/blog/2011-06-24/dear-database-...

Seems like. That's also what this comment on Reddit says:

http://www.reddit.com/r/programming/comments/1niheb/mongodb_...

here you go: http://use-the-index-luke.com/sql/join/hash-join-partial-obj...

It's really a PIA.

Recently, I've learned about http://jooq.org/ — not having checked in detail yet, it might be easier there.

Other formats (PDF and paperback) are available on a commercial basis:

http://sql-performance-explained.com/

Besides your points, we must also consider that MySQL does neither support hash joins nor sort/merge join. MySQL it just not very good at joining.

Nevertheless, a MySQL join should never be slower than the N+1 select approach.