Database Table Normilization

Hi - I have taken over a Database from a co-worker who has stopped showing up for work and I feel the this database is a nightmare. The table structure is non existent and while what was originally set-up "works" - it is not easily understood nor "correct". For example, this is DDL for two tables - that I feel should actually be broken down into multiple smaller tables, what do you guys think here? For example, we have the table HSN New which duplicates data from HSN, but has an active column to show if the info is active or not. To me the best set-up would be to have a table for MSN, SN (which is master site name, site name, and active). Then have a table with a Auto-Number PK and a FK that links back to MSN that has (ID, FKMSN, RN), Then have a table with a Auto-Number PK and a FK for the 'other' non connected data (ID, FKMSN, DQ, Email), and lastly a table for the MT - set-up like this (ID, FKMSN, MT). Essentially everything links back to the MasterStoreNumber in the what I'll call Main table. This is how the current DDL is set-up, I know it's a cluster. What do you guys think? This is a link to a subset of data and DDL [login to view URL]