Thank you, but "rank" is what the indexing engine thinks the rank
should be, while in my application DocScore is actually a more
elaborate column that for example contains the information how often
the document has been viewed.

So is "rank" still the only column the SQL Server 2005 FT engine can
sort by (without diggin up all matches and sort through those)? This
was all SQL Server 2000 could do.

Yes, something like

select top 10 Name, StandardCost
from Production.Product
where contains(Name, '"Mount*"')
order by ListPrice desc

does work, the problem is that the FTS will dig up all matching rows
first (and in my application there are usually a lot of hits) and then
SQL Server will sort there and return the top 10 rows.

With SQL Turbo my queries are a lot faster, since I can specify an
additional ordering index (which may also reside in a different table)
and sort by that index. The SQL Trubo fulltext engine will then only
return the top n rows that I have specified.

The containstable statement allows a similar functionality, like in
Hilary's example:

select top 10 Name, StandardCost from Production.Product
join (
    select [key], rank from
    containstable(Production.Product, Name, '"Mount*"', 1000)
) as k
on k.[key]= Production.Product.ProductID
order by ListPrice desc

The containstable statement will only return the first 1000 rows here,
but these will always be sorted by rank. I need this sorted be
ListPrice instead. If I do this:

select top 10 Name, StandardCost from Production.Product
join (
    select [key], rank from
    containstable(Production.Product, Name, '"Mount*"', 10)
) as k
on k.[key]= Production.Product.ProductID
order by ListPrice desc

I will not get the 10 matching rows with the highest ListPrice.