Using tables noted below, createa view named NJITID_Player_History. you MUST replace NJITID with your NJIT ID.

Using tables noted below, createa view named NJITID_Player_History. you MUST replace NJITID with your NJIT ID. For example, the view name in question 1 should look something like jm123_Player_History that contains:

playerid ---From PEOPLE table

Player Full Name

# of Teams played for --- From APPEARANCES table

# of yrs played

Use a Case clause to indicate "Hall of FaMer" if the player is in the Hall of Fame, otherwise the column should contain "Not Inducted" ---From HALLofFAME table

Total Salary --- From SALARIES table

Average Salary

Name of the last College Attended --- From COLLEGEPLAYING table

Year Last played in College

The number of years attended college

The number of difference colleges played for

Hint: To find the last college requires 2 steps. Use a subquery to find everything but the last college name. Use that subquery and the TOP 1 statement in the select to get the full answers.

Career Home Runs --- From BATTING table

Career Batting Average

Highest year Batting Average

Pitcher Career Wins --- From PITCHING table                                                                                               

Pitcher Career Losses

Career Average ERA

Highest ERA

Career StrikeOuts

Highest Strikeouts

Number of Player Awards --- from AWARDSPLAYERS table

Number Of Player Shared Awards --- from AWARDSSHAREDPLAYERS table

Year Last Played --- from APPEARANCES table

Name of last team played for

Note: If written correctly, view will return 19,370 rows (1 for each player in the PEOPLE table)

Remember to check your answers. Due to the data, if you do not associate the tables properly, you will lose results. You should end up with the same number of rows in the results as there are in the Master table. 15 points will be taken off if your answer does not contain all the required columns.

I recommend breaking the required columns up into pieces and use WITH statements or subqueries to create each part. Use left joins to insure data is not dropped due to all players not having information in all tables.