Good Database Design Books?

OneC0de writes "I am the Director of IT for a small/medium sized marketing company, where I personally write the code that runs our applications. We use a variety of technology at our office, the majority of which rely on MS-SQL and MySQL databases. I am familiar with tables, SQL queries, and have a general understanding of how the SQL databases work. What I'm looking for is a good book, particularly a newer book, to explain general database design techniques, and maybe explain some relational tables. We have some tables that have million of rows, and I'd like to know the best method of designing these tables."

Comments

Re:Somewhere, a coder is polishing his resume

[RyuuzakiTetsuya]

He's lame then.

If I had the flexibility to call myself whatever I wanted, I'd make damn sure that my business cards all said, "Batman" on them.

Re:Can you be more precise ?

[itwerx]

Here, let's just give him some answers:
- normalize everything for consistency
- denormalize everything for performance
- index only key fields for performance
- index everything for performance
- date index everything for logging purposes
- don't date index anything for performance reasons
- sanitize your inputs at the db level instead of the client for security and performance
- sanitize your inputs at the client level instead of the db for security and performance
- use Postgresql because MySQL sucks
- use MySQL because Postgresql sucks
- use [favorite db engine] because [some other engine] sucks

There, HTH!