January 9, 2013 at 8:14 pm
I had a developer ask me an interesting question today about a large update script they wanted to run. If I had a script that had a large amount of UPDATE statements in it like below:
UPDATE TABLE1 SET FIELD1 = .....
UPDATE TABLE1 SET FIELD1 = .....
UPDATE TABLE1 SET FIELD1 = .....
UPDATE TABLE1 SET FIELD1 = .....
UPDATE TABLE1 SET FIELD1 = .....
and so on......
If one or two of the statements were to affect 0 rows how could I report back which actual statement did that?
I assumed they were being lazy and should know if an UPDATE would affect a row, otherwise why put it in the script in the first place.
I just wondered if this was something that people have done before.
January 9, 2013 at 8:59 pm
UPDATE TABLE1 SET FIELD1 = .....
SELECT @@ROWCOUNT
UPDATE TABLE1 SET FIELD1 = .....
SELECT @@ROWCOUNT
UPDATE TABLE1 SET FIELD1 = .....
SELECT @@ROWCOUNT
UPDATE TABLE1 SET FIELD1 = .....
SELECT @@ROWCOUNT
UPDATE TABLE1 SET FIELD1 = .....
SELECT @@ROWCOUNT
This will tell you. You just need to be sure you capture @@ROWCOUNT immediately following the statement you want the count of.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply