What SkipVought says is true.
What you can do to achieve something similar is adding an integer identity field, which is an autogenerated and ascending integer. So if you order by that field you get the data in that order. But if using a where clause or deleting rows of course the row number of a record changes in the result.
The row number is not a point of interest at all in a database, what matters is having a unique identifier in a record to have a permanent reference like a permalink is for a blog article. Of course it's as permanent, as the record is similarly as the permalink gets broken if the blogger deletes his article. What's used for that type of identifier called primary key typically is integer identity(1,1) or uniqueidentifier with default value newid().
Bye, Olaf.