Article Preview
Buy Now
| PDF: |
Feature
Good Database Design Principles
Designing a database upfront can save you a lot headaches later
Issue: 8.2 (January/February 2010)
Author: Craig Boyd
Article Description: No description available.
Article Length (in bytes): 32,670
Starting Page Number: 16
RBD Number: 8209
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
It is my hope to help you understand what good database design is and how to design your database for optimal performance and maintainability.
There are three broad areas that directly impact database performance:
Actual Database Design and Architecture
SQL Usage
Hardware and Network Design and Architecture.
Actual Database Design and Architecture
There are several database platforms and each has its own sets of rules and design constraints. It is beyond the scope of this article to address each platform or even a single platform. Whole books have been written about the individual platforms and how best to performance tune them as well as what unique set of tools should be used. Instead my intent is to present you with some general principles which will apply to all (or at least most all) the platforms and will serve you well as you set out to design your next system or rework an existing one for better performance.
While good database design and good performance are not mutually exclusive they are two different things. A good database design is one that is easily understood by developers and the database savvy business users without a great deal of explanation. That does not mean a complex design is bad, but like all things the more simple the design, the better it is for all involved.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.
|
