GSquared (7/26/2012)
PaulB-TheOneAndOnly (7/26/2012)
Lucky9 (7/26/2012)
I have to redesign the database based on the new business requirementsCould someone please help me with the steps that needs to be followed
when redesigning a database.
Either the current database was a complete disaster or the business changed drastically (like from being a hospital to be a car manufacturer). No change in business model should trigger a full redesign of the underlying database.
Start by doing a Gap Analysis which means...
a) What you have today,
b) What are the new requirements,
c) What's the gap between today's functionality and required functionality
d) Evaluate changes needed to fill the gap.
Which is the same thing I already said, but with different names for the steps.
I'm sorry but I have to differ on this one GS; I couldn't see in your post anything that remotely resembled Gap Analysis - a very nicely worded and accurate for sure general guideline but not what I posted. I do my best not to be redundant.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.