I need help with this project

My SQL Workbench Project part $3$ In this Project, you will normalize the LetsMeet data. In particular, you will eliminate redundant columns by looking for tables that fail to meet Third Normal Form $(3$NF$).$ Recall that a $3$NF table should not have any transitive dependencies. Generally speaking, all non$-$key columns should be dependent on "the key, the whole key, and nothing but the key."

The LetsMeet data is in your schema. When you look at the navigator on the left side of MySQL Workbench, your schema should be bold. If it's not bold, double click on your schema.

STEP $1$: Find Redundant Columns

Generate the LetsMeet ERD to view all the tables and columns. Scan the tables and columns to identify potential data redundancies.

STEP $2$: Eliminate Redundant Columns

After completing the previous Knowledge Check, you can see that the letsmeet tables contain quite a few redundant columns. In this step you will remove some columns you identified.

You don't need to eliminate all the columns you identified, but should eliminate at least five columns from the letsmeet database.

You should write a SQL statement for each column that you want to remove. Underneath each of the statements used to remove the columns, you should use a multi$-$line comment to state which column you are removing and why.

If you choose to remove the RAND$()$ column from the venue$\_$ table, you will need to enclose it using backquotes like in the following snippet. This is because RAND$()$ is actually a SQL function that returns a random number. So unless it is enclosed in backquotes, you will not be able to drop it$.$

STEP $3$: Split grp$\_$member Table

The grp$\_$member table does not have a PRIMARY KEY according to the ERD.

he member$\_$id column seems like a natural PRIMARY KEY, but it is not unique because members are listed multiple times for each group they are a part of$.$

No PRIMARY KEY means that this table is not normalized. You will need to split it into two tables: one that includes information about the members and one that includes the groups they are a part of$.$

A$.$ Create a new table called group$\_$sign$\_$ups that includes only group$\_$id$,$ member$\_$id$,$ and joined. Use CREATE TABLE $...$ SELECT DISTINCT to transfer the relevant data.

The DISTINCT function is necessary so that you do not end up with duplicate members.

B$.$ Create a new table called members that includes columns about members from the grp$\_$member table. Use CREATE TABLE $...$ SELECT DISTINCT to transfer the relevant data. Be sure to only include columns that are directly related to member information.

C$.$ Alter the members table to include a PRIMARY KEY.

D$.$ Alter the group$\_$sign$\_$ups table to include a FOREIGN KEY that references the members table.

E$.$ Alter the group$\_$sign$\_$ups table to include a FOREIGN KEY that references the grp table.

F$.$ DROP the grp$\_$member table.

STEP $4$: Create a New ERD

Create a new ERD that shows your updated tables and columns.

With your new ERD open, click File $>$ Save Model to make sure it saves.

ERD Model files will not show up automatically when you leave the project and re$-$enter. You can check if the ERD model file was saved by going to File $>$ Open Model $>$ within the pop$-$up screen you should see your saved file.