The major advantage is improved performance.
Having redundant and duplicate data takes up valuable space; it is harder to code, and much more data maintenance is required.
If the table has redundant groups of data, this data would be a candidate to remove into a separate table.
Overnormalization can lead to excess CPU and memory utilization, which can put excess strain on the server.
False. When a transaction is committed, the transaction cannot be rolled back.
False. A SAVEPOINT is used only as a point for a ROLLBACK to return to.
COMMIT saves changes made by a transaction. ROLLBACK undoes changes made by a transaction. SAVEPOINT creates logical points in the transaction to which to roll back.
SQL Server auto-commits statements unless specifically placed in a transaction and has a different syntax for SAVEPOINT. Also, it does not support the RELEASE SAVEPOINT command.
No, a ROLLBACK will go back only to the first SAVEPOINT that you ask it to ROLLABACK to.
The SELECT and FROM keywords, also called clauses, are required for all SELECT statements.