I say random rows because TSQL doesn’t guarantee order unless you have an order by clause.
If you want to update two rows based on the ORDER BY clause then you will need to use the TOP clause in a sub query in conjunction with a WHERE constraint, like in the following example.
Additionally if you forget the WHERE clause altogether, you will update the entire table when you might not intend to.
Here is an example where I specified the WHERE clause incorrectly and I updated too many rows: Here I updated Toy Name on two rows, the “Silver Magic” and the “Super Surfer” Toyname rows.
By doing this I have made sure I don’t have a bogus WHERE clause on my UPDATE statement that is going to incorrectly identify rows to be updated in my table.