Timeline for MERGE running slowly
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2016 at 18:39 | vote | accept | Magier | ||
| Nov 14, 2016 at 18:39 | comment | added | Magier | Thanks for this helpful input it's new to me. However since those statements are easy and fast for smaller (<100K rows) tables and I havea generic script to generate any kind of merge statement with different options I just love them. I could improve the performance a lot by using a ROWVERSION to compare the requirement to make UPDATES instead of OR-ing all column contens between source and target table because I have rowversion in almost every table. The two larger table ~10 Mio rows are still a problem maybe I will change the procedure for those two... | |
| Nov 10, 2016 at 16:07 | comment | added | Aaron Bertrand |
...and a handful of other reasons to be careful with MERGE... mssqltips.com/sqlservertip/3074/…
|
|
| Nov 10, 2016 at 14:16 | history | answered | Duane Lawrence | CC BY-SA 3.0 |