If this is just a training exercise, fair enough. But this is not the best way to solve such a problem - in SQL Server, loops are used infrequently as there is a set-based solution to most problems (including this one).
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.