It is kinda. TOP (100) PERCENT ... ORDER BY will result in SQL ignoring the order by in a view because it's not a row-limiting top. Whether the optimiser will get smart enough to realise that TOP (really large number) is also not a row limiting top and hence will allow it to ignore the order by is an open question. It's probably not something that will be indicated as deprecated if it ever happens, because it's used to evade the SQL rule that only and ORDER BY on the outer-most select has any effect on the ordering.