I have seen tests that show ODBC (what you call "DSN" connections) to be
faster in some cases than OLE DB connections. It really depends on what
you're doing, how you're doing it and which provider you're using (and how
well that provider is written). There's nothing "wrong" with using what
works. In your case it sounds like ODBC might be a better choice. It's
faster in ADO.NET too (than the OleDb providers)... ;)
--
William (Bill) Vaughn, Author, Trainer, Mentor
Microsoft Pacwest Regional Director
"ADO and ADO.NET Examples and Best Practices for VB Programmers--2nd
Edition" (ISBN: 1-893115-68-2)
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
________________________________
<dvmak_at_earthlink.net> wrote in message
news:nJZl9.700$OB5.69309_at_newsread2.prod.itd.earthlink.net...
> Using a System DSN connection my asp pages are returning recorsets in < 1
> sec. When I switch to Oledb (both OraOLEDB.Oracle.1 and MSDAORA.1) the
> return time is > 15 sec.
>
> Using IIS server and tracing is off. Any hints on why the poor
performance?
>
> Thanks
>
>
Received on Mon Sep 30 2002 - 12:59:09 CDT
