So are there any maturity, reliability, performance, or functionality differences between ODBC and ADO, anything that might recommend one over the other?
Thank you, -Brian -----Original Message----- From: Stricker, Scott E (IS) [mailto:[email protected]] Sent: Wednesday, May 20, 2009 06:48 To: Brian H. Oak Subject: RE: :ODBC vs. DBD::ADO I've got perl code that to swap between ODBC and ADO, I simply change the connect string. At one point, there was a bug in ADO driver that pushed me to ODBC, other than that, I was able to swap back and forth. E. Scott Stricker Senior Software Engineer Northrop Grumman - Information Systems - C2SD MailStop 4S02 2340 Dulles Corner Blvd. Herndon, VA 20171 703-561-3671 703-713-1601 (fax) -----Original Message----- From: Brian H. Oak [mailto:[email protected]] Sent: Tuesday, May 19, 2009 6:48 PM To: [email protected] Subject: DBD::ODBC vs. DBD::ADO I have used DBD::ODBC for years, connecting to and working with MS SQL Server. In all that time I have been very happy with DBD::ODBC. Now I'm porting someone else's code into Perl, and it was originally written to use ADO. I already know that I can make the code work with ODBC, but I have to wonder if there would be enough advantages in using ADO to justify the jump -- and the corresponding learning curve. Has anyone out there used both technologies with SQL Server? If so, have you formed an opinion about the pluses and minuses of each? Thank you, -Brian
