G
Guest
I have acquired the wonderful task of redesigning a database that has been in
use for about 3 years. The person who designed the database did not normalize
the data, so I have one table with several columns that all represent the
same type of data (imagine a student schedule with a column for each class,
rather than a table to link the student and class tables).
What my problem is now is that I must either continue to work with the poor
design, or split the 48,000 or so records into maybe 200,000 records. What I
need to know is if there is a quick and painless way to do this. The analyzer
seems to only want to split out certain fields, and not the way I would want
it. Besides, like I said, it's one-to-many, but there are always 3 columns
for categories and 6 columns for reasons. Let me know if there is any more
information you would need to help me out on this one...
OLD TABLE:
Tracking # (key)
Employee (who dealt with the application)
Date
Customer Name
Category for review
Reason for review
Reason for review 2
Category for review 2
Reason for review 3
Reason for review 4
Category for review 3
Reason for review 5
Reason for review 6
Comments
NEW TABLES:
APPLICATION
Tracking # (key)
Employee (who dealt with the application)
Date
Customer Name
REASONS
Reason # (key)
Tracking #
Category for review
Reason for review
use for about 3 years. The person who designed the database did not normalize
the data, so I have one table with several columns that all represent the
same type of data (imagine a student schedule with a column for each class,
rather than a table to link the student and class tables).
What my problem is now is that I must either continue to work with the poor
design, or split the 48,000 or so records into maybe 200,000 records. What I
need to know is if there is a quick and painless way to do this. The analyzer
seems to only want to split out certain fields, and not the way I would want
it. Besides, like I said, it's one-to-many, but there are always 3 columns
for categories and 6 columns for reasons. Let me know if there is any more
information you would need to help me out on this one...
OLD TABLE:
Tracking # (key)
Employee (who dealt with the application)
Date
Customer Name
Category for review
Reason for review
Reason for review 2
Category for review 2
Reason for review 3
Reason for review 4
Category for review 3
Reason for review 5
Reason for review 6
Comments
NEW TABLES:
APPLICATION
Tracking # (key)
Employee (who dealt with the application)
Date
Customer Name
REASONS
Reason # (key)
Tracking #
Category for review
Reason for review