Timeline for SQL Server: affect other transactions?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2014 at 13:58 | comment | added | Yuri Makassiouk | Yes, that's the way we are going now - log entries are duplicated in a local table variable and if we have to roll back, the log table is re-populated from the variable. It sort of works, but I am looking at improving this anyway. Just in case some really bad stuff happens, the transaction goes away and the catch section never occurs and then the log is lost. | |
| Jun 27, 2014 at 13:51 | history | tweeted | twitter.com/#!/StackDBAs/status/482521570385338368 | ||
| Jun 27, 2014 at 13:49 | comment | added | Brian Bentley | You may be able to use a table variable depending on what you want to do. Table varibles do not participate in tranactions and are not affected by rollbacks. | |
| Jun 27, 2014 at 13:40 | vote | accept | Yuri Makassiouk | ||
| Jun 27, 2014 at 12:59 | answer | added | Sean Gallardy | timeline score: 1 | |
| Jun 27, 2014 at 12:50 | history | asked | Yuri Makassiouk | CC BY-SA 3.0 |