Robert Calhoun Robert Calhoun 4, 1 1 gold badge 35 35 silver badges 32 32 bronze badges. Add a comment. Maybe you should try to commit after the update. Random Random 1 1 gold badge 4 4 silver badges 9 9 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Visit chat. Show 11 more comments. Active Oldest Votes. Something AND I. Community Bot 1 1 1 silver badge. ErikE ErikE It's ironic that, without exception, all the links you have pointed me at pretty much share the same style as mine.
They just go ahead and tell what's not working and ask if anyone knows a solution to make it work. No "original research". If everyone just acted like you did, none of those answers would exists today. But thanks for sharing them anyways.
And you pushed back--bravo! And you got the answer you need. So are we cool now? Regardless of everything, I appreciate you backing down and writing an answer with an appropriate tone. Though, I don't know what you mean by "pushing back" in your comment.
You spoke up for yourself and let me know that you were unhappy with what you were getting. Add a comment. ID -- Point 1. AND C. This way, I'll only go through the rows that have been updated, and I won't mess with the other ones. You can only join with one of them, but I needed to see a difference in one column between the values before and after the update operation. So that's why I used them both. After that, I need to find a row in the whole table that is calculated by a value in the row that is currently being updated.
In my case, there was a parent of the current row and I wanted to find that row. Basically, you write another query to find the row based on your updated row, and then you make another JOIN to that returned table. You can put any kind of criterion here. I have non-clustered indexes on the columns in the first update query that I tried to update 1 row from.
I re-built all of the indexes but no change in execution. What's the wait information for the query? What's the execution plan look like? Gryphoenix Try to see if there are connections blocking your current transaction. Maybe you have already a long running transaction, or there is a transaction left open. How many rows are deleted? Do you shrink your databases at all?
Show 3 more comments. Active Oldest Votes. Improve this answer. MauMen MauMen 3 3 bronze badges. Add a comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown.
0コメント