In SQLserver
This criterion is linked to a Learning OutcomePlayer Batting Stats BODY Select
Has 16 columns with headers and proper calculations
data for the 2008 Philadelphia Phillies (TeamID=PHI)
we use have 2 different tables Batting and Players( were name is 2 column nameFirst, nameLast)
We are pulling for 2008. The basic( body) table data should be a simple SELECT based on our
view.
Albeit long, the grid body is a simple SELECT with several calculated columns. About 50% of the
fields
can be plugged into the SELECT directly (i.e. GP, AB, R, H, ...
) from existing columns.
for AVG should be something like this SELECT ......, H/G as BA,
Body of the grid. I expect the same column headers as ESPN. Name should be formatted the
same in a single column.
The data in the body is sorted by batting average
Note that the body is sorted by Batting Average high to low.
GP AB R H 2B 3B HR RBI TB BB SO SB AVG OBP SLG OPS.
In SQLserver This criterion is linked to a Learning OutcomeP.pdf
1. In SQLserver
This criterion is linked to a Learning OutcomePlayer Batting Stats BODY Select
Has 16 columns with headers and proper calculations
data for the 2008 Philadelphia Phillies (TeamID=PHI)
we use have 2 different tables Batting and Players( were name is 2 column nameFirst, nameLast)
We are pulling for 2008. The basic( body) table data should be a simple SELECT based on our
view.
Albeit long, the grid body is a simple SELECT with several calculated columns. About 50% of the
fields
can be plugged into the SELECT directly (i.e. GP, AB, R, H, ...
) from existing columns.
for AVG should be something like this SELECT ......, H/G as BA,
Body of the grid. I expect the same column headers as ESPN. Name should be formatted the
same in a single column.
The data in the body is sorted by batting average
Note that the body is sorted by Batting Average high to low.
GP AB R H 2B 3B HR RBI TB BB SO SB AVG OBP SLG OPS
