Read the comments on your question and put the information in your question.Eg here you have said nothing about keys yet my answer says that they matter.This is the view code: Create View Input Flight Prices As Select ID, Airline, Destination, Airport Name, Price, Departure, Route Status From Airlines As a Join Price Table As p On a. It'll now allow you to view and edit the entire table from the context menu.Per the last sentence: If you want to update a base table for a particular row then it has to be just one base table's columns, columns of some key from that base table must be in the view (UNIQUE NOT NULL or PRIMARY KEY), and you must not be updating those columns.The view will only have a SQL statement that will be executed in background once you query the view.
So data to be inserted for a "Business Entity" may be split into various tables as part of normailzation.
Otherwise when you ask to update some row in the view it's not clear what row in what base table is to be updated.
See also SQL Server 2014 Modify Data Through a View.
Since views are just SQL select statements, there are a few restrictions on which views can update data back to the tables.
The most logical that I can think of is that if you are projecting the result of some computation over a table column, how is the view supposed to revert that computation when trying to insert data back to the table?