Name	Objects	Area	Capital	Population	Mayor	MayorParty	Statehood	Governor	GovParty
Colorado	1	104185	Denver	5.812	Hancock	D	1876	Polis	D
Delaware	1 2 3 4 5 6	1 0.5 0.1 1 1982 0.5	Dover	1.003	Christiansen	D	1787	Carney	D
Idaho	1	83642	Boise	1.901	McLean	D	1890	Little	R
Alabama	1 2 3 4 5 6 7 8 9	52419 1.8 2 0.6 7.5 0.05 0.01 0.1 1.15	Montgomery	5.04	Reed	D	1819	Ivey	R
Oklahoma	1	69889	Oklahoma City	3.987	Holt	R	1907	Stitt	R

You have been asked to comment on this table structure as it is. They ask you the following set of questions:

Which objects are we likely to lose information about if we delete something?

Assuming we broke this table into objects within states (i.e., geometric objects), which attributes are we most likely to make consistency mistakes on (i.e., they are repeated a lot)?

The folks at the US Census Bureau ask you to fix this situation such that these idiosyncracies will be mitigated. To do that, do the following:

Identify the current primary key of this table

Identify how this table would be taken to 1NF

Identify the new most logical primary key

Identify how this new table would be taken to 2NF, establishing which attributes belong to which parts of the primary key

Identify the foreign keys between these tables, and which one is controlled by which

Identify how these new tables would be taken to 3NF, establishing which attributes depend on the primary key through some other attribute

Identify the foreign keys in these new tables, identifying which one is controlled by which

You are not allowed to add any columns to these tables for the purposes of identification. You must utilize what you have only.

You do not need to present in your solution how the rows in the tables change. Your goal is to identify the structure of the tables with respect to one another. You should denote what fields are primary keys and foreign keys as you go through this process.