Database Design Always Matters, Continued.
You can spend a little more time upfront or a lot more time later
Issue: 12.5 (September/October 2014)
Author: Craig Boyd
Author Bio: Craig Boyd is currently an Oracle DBA for a well-known national retailer. But in his 18 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): 17,007
Starting Page Number: 72
Article Number: 12512
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 review the last couple of columns before reading this one as we will be picking up where the last one left off.
As a quick review there are five steps we are going through:
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.