Web Forms :: 4.0 SEO URL's - Going Backwards?

For the new ASP.NET 4.0 SEO enhancements, I have followed the following two articles and I have some questions and concerns I hope someone can explain: [URL] For years, from a programming best practice e.g. performance, we've been told to place a Primary Key on a column in a database table e.g. CategoryID which uniquely represents a specific Category record (which contains another field e.g. CategoryName).

Unless I am mistaken, now with the new ASP.NET 4.0 SEO Clean URL features, we are selecting records based on their CategoryName rather than CategoryID. Furthermore, the CategoryName may not be indexed at all, thus resulting in an inefficient database table scan.

SELECT CategoryName FROM Category WHERE Category.CategoryID = @CategoryID

We now need an inefficient version

SELECT CategoryName FROM Category WHERE Category.CategoryName = @CategoryName

There is another more significant issue, when you look at the child table e.g. Products. When trying to find all child records for a given parent record we would typically use this:

SELECT ProductName FROM Products WHERE Products.CategoryID = @CategoryID

We now need an inefficient version

SELECT ProductName FROM Category INNER JOIN Products ON Category.CategoryID = Products. CategoryID WHERE Category.CategoryName = @ CategoryName

So not only are we searching for a string on a non-indexed column rather than an integer on a primary key indexed column, we are also unnecessarily joining parent and child tables which causes yet another performance penalty. This may not be an issue for sample databases such as Northwind or AdventureWorks, but for real life production databases with many thousands of records, I believe it's a significant performance and scalability issue (as more users simultaneously visit the site).