Database Design Always Matters III
Spend a little time up front or a lot more time later
Issue: 12.4 (July/August 2014)
Author: Craig Boyd
Author Bio: Craig Boyd is currently an Oracle DBA for a well-known national retailer. But in his 17 years of IT experience, he has been everything from a PC Technician, iSeries System Administrator, iSeries Programmer, Sr. Technical Lead, and Data Modeler. He lives in the great state of Texas with his wife and two kids.
Article Description: No description available.
Article Length (in bytes): 19,494
Starting Page Number: 63
Article Number: 12413
Related Link(s): None
Excerpt of article text...
In this month's column we are continuing our discussion of refactoring an existing database design. I would strongly encourage you to pick up last month's column and review as this one will be picking up where that one left off.
You may remember from the past few columns that I listed five steps that we will be going through as part of this exercise:
Figure out the current state of the existing database
Identify the existing design flaws and determine how best to fix them
Gather requirements for the changes
Create the final design based on fixing the design flaws and the changes from the new requirements
...End of Excerpt. Please purchase the magazine to read the full article.