response database

 (Adam) A database table is the object that stores all the data for your database. A database is essentially a collection of tables that feature the data you need to be stored and possibly recalled later. A database view is for grabbing specifically identified attributes from multiple tables and combining them into a new, non-permanent, custom table that shows you relevant information. Sometimes the data you need to compare or analyze can be on different tables and creating a view can give you the data on the same table/screen to look at.

   There are certainly similarities between database tables and database views. First, the format between views and tables should be the same. The database view is going to consist of rows and columns just like your table. Since you are pulling from your tables it will contain the same data as what you are pulling from.

   An example where it makes sense to create a view would be when you have a database that records football statistics. The running back position has a primary focus on running the ball out of the backfield, but they can also play a significant role in the passing game. You wouldn’t keep the rushing and receiving data for players in the same table, but occasionally you would want to compare the total production from players at the position. There is an award in college football called the Doak Walker award that goes to the top college running back every year. If you were comparing the top two candidates that had similar rushing resumes, it would be wise to create a view that shows more applicable information. If candidate A had 1,400 yards with 10 TD’s with 10 receptions for 85 yards and candidate B had 1,350 yards with 9 TD’s with 50 receptions for 450 yards and 4 touchdowns, candidate B would be more deserving of the award. If you were only looking for rushing statistics, candidate A would appear like the better choice, but the view that included the receiving statistics showed that candidate B was actually better.