That's right; we've just arrived to the end of this part. During our short journey we have seen the importance of query optimizations and schema design. You see, the most critical distinction in the real world is that performance comes into play. And in order to achieve high performing servers, responsive queries, and efficient functioning, "just all right" is never enough.

The most useful advice regarding database design planning is that we should think as early as possible. We shouldn't sacrifice the best just for a currently working setup that gives us "acceptable" performance. We need to do our best to get the most out of what we have because later on down the road we (and the management) will be glad we did so. Lots of companies end up struggling, not knowing what to do when it's too late.

And then to alleviate the "sudden" panic, they hire DBA experts and professionals in their fields, which most of the time recommend a total revamp. Why? Because the mindset on which everything was based-the foundation-wasn't strong. At the beginning it was decent and satisfying, but as the company's needs have grown, well, imagine a building becoming larger, taller, and wider... and you get my drift!

The total revamp usually requires a clean design, and this may not be possible without losing resources (money, time, etc.). Altogether, the conclusion is that regardless of the situation, it is always much more profitable to think big and plan for the future right from the beginning. But don't exaggerate; be realistic, think over multiple times the requirements, and do your best. Never settle for less. All will be well.

As a closure, I'd like to invite you to join our experienced community of technology professionals in all areas of IT&C starting from software and hardware up to consumer electronics at Dev Hardware Forums. As well as, be sure to check out the community of our sister site at Dev Shed Forums. We are friendly and we'll do our best to help you.