You'll probably need a cursor to update your values, because to calculate the OneStopOrNot column for one row, you need the calculated result of OneStopOrNot column of the previous row.

With a set-based solution all the rows would be updated at once, which means you cannot use the result of the previous row.

To get you started on cursors:

SQL Server Cursor Example[/url]

Just to be perfectly clear: cursors are bad and slow for performance. However, in your specific business case you might need them. (unless someone else proves me wrong of course and uses set-based TSQL to solve this issue)