Timeline for Trigger to create a variable Table to be sent to service broker
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2015 at 18:51 | comment | added | Hannah Vernon♦ | ahhhh. I understand now. Best of luck with your solution. | |
| Nov 4, 2015 at 18:45 | comment | added | JohnG | It was pure coincidence that I actually tested 1000 rows and you also mentioned 1000 rows. What I was trying to say is that I wasn't satisfied with the results of 1000 rows using XML and if I have a batch of 105 000 updates and i decide to process chunks of 50 or 100 or 500, it would be very time consuming. So I'm trying a solution that doesn't use XML, I hope it works... If it works I will post it... If not I will try with your solution. | |
| Nov 4, 2015 at 18:34 | comment | added | Hannah Vernon♦ | I picked 1,000 rows out of thin-air. You can try adjusting that down to say 50 rows, or 100, etc. Fine tune it to work with your requirements. | |
| Nov 4, 2015 at 18:19 | comment | added | JohnG | +1 That is quite a solution... I like the Idea, though I'm not sure that it will be efficient. I started another solution where the trigger will create unique inserted and Deleted tables which will be referenced in the message... because when I ran an update of 1000 items, it took 40 minutes to run which is too much... I have a feeling that breaking down the XML of 1000 rows of 120 fields per row to do the audit is way too long... If my tests are not satisfactory with the solution I'm building, I will definitely try this one. I thank you for your input it was very helpful. | |
| Nov 4, 2015 at 18:16 | vote | accept | JohnG | ||
| Nov 4, 2015 at 18:04 | history | answered | Hannah Vernon♦ | CC BY-SA 3.0 |