One benefit of using views is that they can send less data across the network. True or False?

One benefit of using views is that they can send less data across the network. True or False?

• A. True
• B. False
• C. Sometimes
• D. Only with distributed databases

Answer: (A)

A view is a saved query that defines exactly which data to return. Because of that, you can design a view to project only the columns you need and to filter out unneeded rows. When you query that view, the database engine returns just the data specified by the view, which often means less data travels across the network compared with retrieving all columns or all rows from the base tables. In distributed databases, views can also push down filtering and projection to the remote data sources, further reducing network movement. There are cases where a view might not reduce data transfer (for example, if it selects all columns and returns all rows), but the typical benefit is that the view can minimize the amount of data sent over the network.

A view is a saved query that defines exactly which data to return. Because of that, you can design a view to project only the columns you need and to filter out unneeded rows. When you query that view, the database engine returns just the data specified by the view, which often means less data travels across the network compared with retrieving all columns or all rows from the base tables. In distributed databases, views can also push down filtering and projection to the remote data sources, further reducing network movement. There are cases where a view might not reduce data transfer (for example, if it selects all columns and returns all rows), but the typical benefit is that the view can minimize the amount of data sent over the network.