I've noticed that ADO.net is much faster than ADO 2.X for SQL Server.
I can't give you a number, but it's faster since it's all TDS data

I don't think I'd reccomend a straight port.  I don't think you'd see any
real gains unless you designed everything for .net.

Michael

We made exactly the same thing: translating a classic COM
component + minimum ASP application; we saw a 15-20% speed
increase in the .NET version. This 2-3 times quicker thing
is for web sites made with only script using ADO and
Scripting... But yet things are quicker. But if it could
seem like a small gain in performance (especially when you
look at your average CPU usage, which is rarely more than
50% on web sites I know), you will gain many things in
terms of code reusability (.NET includes a "true" object-
oriented approach, to compare with the limited one
available in COM), and you get many new resources: easier
ISAPI filters with IHttpModule, more performant support
for XML and XSLT, a bigger component library (with
libraries such as automatic logging, compression, etc.
available for free), an easily extensible configuration
framework, and a true gem for people who've done a lot of
COM programming with IIS: you don't have to restart your
web server to change your component (yiiiiipie yeah!) and
you won't have registry problems since the components are
not registered in it... And for me, that's just enough to
justify the port.

Good luck

Francois Lemaire