by
Jeremy D. Zawodny, Derek J. Balling, Baron Schwartz, Peter Zaitsev, Baron Schwartz. Peter Zaitsev. Vadim Tkachenko. Jeremy D. Zawodny. Arjen Lentz. Derek J. Balling
Sure - here's a list of what's good to know for MySQL. Other DBs are going to have different needs, though the indexing data is good to know regardless.
Start with the book High Performance MySQL. [1]
Follow up with the whitepaper "Causes of Downtime". [2]
Then find a copy of the IMDB dataset, put that in a database, and write an app against it. Make that app perform well, then simulate load against the app (pretend it hit the top of Reddit and Hacker News simultaneously), and keep it performing well.
Start with the book High Performance MySQL. [1]
Follow up with the whitepaper "Causes of Downtime". [2]
Then find a copy of the IMDB dataset, put that in a database, and write an app against it. Make that app perform well, then simulate load against the app (pretend it hit the top of Reddit and Hacker News simultaneously), and keep it performing well.
After that, it's a matter of practical practice.
[1] http://www.amazon.com/High-Performance-MySQL-Optimization-Re...
[2] http://www.percona.com/redir/files/white-papers/causes-of-do...