.net - What are the pros and cons of OleDB versus SQLClient? -
some context: 1 of systems i'm working on .net 2.0 web application. vb.net front end, , sql server 2005 backend. variety of reasons have been lost time, original designer decided use .net oledb connection rather sqlclient connection.
after few years of development, particular system on cusp of crossing line "beta" "1.0" status. 1 of things we've been talking @ point moving sqlclient connection. while i'm aware it's best practice using it, , it's way @ fancier features in sql server 2005 (which aren't using, obviously) advantages of using 1 on other? hidden gotchas should know about? , can point me @ benchmarks showing relative speeds? (i hear sqlclient supposed faster, i've never seen numbers up.)
thanks, all.
oledb more generic. if ever move different database type in future there's chance it'll have ole driver , won't have change code.
on other hand, sql server native driver supposed faster said , has nicer parameter support (parameters can use names , don't have in order).
in personal experience, i've never noticed speed difference, couldn't find up. suspect performance advantage real, you'd have process millions of records before start measure it.
what did notice made meaningful difference error messages. having trouble old oledb app, , switched sqlclient out of desperation. still didn't work, of course, better error messages provided enough new information able fix problem.
Comments
Post a Comment