Alternate words are sometimes used when defining the four basic functions of CRUD, retrieve instead of read, modify instead of update, or destroy instead of delete.CRUD is also sometimes used to describe user interface conventions that facilitate viewing, searching, and changing information; often using computer-based forms and reports.
Strictly speaking, both PUT and POST can create resources; the key difference is that POST leaves it for the server to decide at what URI to make the new resource available, whilst PUT dictates what URI to use; URIs are of course a concept that doesn't really line up with CRUD.
That's 18 extra column of data that were retrieved for nothing. If someone in the future changes the schema of that table and inserts of column between columns 0 and 1, then your results may not be what is expected.
When you create a database in SQL Server and do not specify a file location for your data and log files SQL Server will rely on the default database file locations as defined in the server properties.
Let’s update the settings to point to the new directories: Press OK, and we’ll run our create database script, modifying the database name, and the results now look like this: Whoa, what happened here?
First, like I said earlier, updating those defaults will not migrate existing files.