Timeline for UPDATE with JOIN on 100mm records, how to do this better? (in T-SQL)
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 8, 2012 at 23:29 | vote | accept | Chris Adragna | ||
| Jul 8, 2012 at 23:30 | |||||
| Jul 6, 2012 at 18:12 | comment | added | Darin Strait | I suggest that you double-check that you have enough free space in your log and data files. If the files are auto-growing, performance will nose-dive. I often see people running some big, one-off update and auto-growing their log file without realizing it. | |
| Jul 6, 2012 at 15:16 | comment | added | Chris Adragna | This sounds like a nice, simple approach, especially given the disk I/O problem I'm having. Thank you for answering so quickly. | |
| Jul 6, 2012 at 15:05 | history | answered | JNK | CC BY-SA 3.0 |