Beginning SQL
Beginning SQL Beginning SQL
Figure 11-5 Begin Transaction Delete Update Save Transaction Insert Save Transaction Update Roll back To B Commit Database The next section discusses the log file, the key to being able to perform a rollback. A transaction log is generally a text file that is written outside of the database, usually on a completely different physical drive. All potential changes to the database are written to the log file, and then that file is used to actually write the data changes back into the database when a COMMIT is encountered. Should a catastrophic failure occur, such as an abrupt shutdown caused by power loss, the log file holds all changes to that point in time. A B Transactions 311
- Page 612: Chapter 9 Exercises 286 Assume that
- Page 616: Chapter 10 Now that you know what v
- Page 620: Chapter 10 Types of Views Given tha
- Page 624: Chapter 10 Perhaps you need to view
- Page 628: Chapter 10 Figure 10-7 Summary view
- Page 632: Chapter 10 296 This statement gives
- Page 636: Chapter 10 The CHECK OPTION plays a
- Page 642: 11 Transactions When you move out o
- Page 646: Example Data This section creates e
- Page 650: 3. Build a record in the Rentals ta
- Page 654: The other statement that the ANSI S
- Page 658: SAVE TRANSACTION Select Update Begi
- Page 664: Chapter 11 Transaction Logs 312 How
- Page 668: Chapter 11 Database There are perfe
- Page 672: Chapter 11 In order to find and fix
- Page 676: Chapter 11 When discussing locking,
- Page 680: Chapter 11 Usually, the default iso
- Page 684: Chapter 11 From Sue’s perspective
- Page 688: Chapter 11 5. At this point, you ne
- Page 694: 12 SQL Security In today’s world,
- Page 698: Setting up security begins with cre
- Page 702: ALTER USER username options ALTER U
- Page 706: In Figure 12-3, three different gro
- Page 710: How It Works After you run this sta
Figure 11-5<br />
Begin<br />
Transaction<br />
Delete<br />
Update<br />
Save<br />
Transaction<br />
Insert<br />
Save<br />
Transaction<br />
Update<br />
Roll back<br />
To B<br />
Commit<br />
Database<br />
The next section discusses the log file, the key to being able to perform a rollback. A transaction log is<br />
generally a text file that is written outside of the database, usually on a completely different physical<br />
drive. All potential changes to the database are written to the log file, and then that file is used to actually<br />
write the data changes back into the database when a COMMIT is encountered. Should a catastrophic<br />
failure occur, such as an abrupt shutdown caused by power loss, the log file holds all changes to that<br />
point in time.<br />
A<br />
B<br />
Transactions<br />
311
Change language