Beyond efficiency of the driver, it's capabilities and efficiency of the underlying database engine that you have to consider. And of course how good your database design is.
If you don't need stored procedures, MySQL is great. It's fast and free, and if you're moving from Access, the only thing you'll miss is all the front-end toolbox to manage and program Access. However, MySQL is very fast and scalable. Just run it and access it via DBI, DBD::MySQL and its native driver when you need as high a performance as you can get. The MyODBC driver is also very good if you want to access it through Windows apps. Note that they're not mutually exclusive. MS SQL is also great, has excellent front-end tools for management, but costs $$$ and is very painful to access from Unix boxes. MS SQL also has a big advantage in that it has stored procedures. It also has the usual triggers, profiling tools, etc... common to the big kahunas of RDBMSes as well as some crude OLAP tools out of the box. But your bottleneck is clearly the database engine, not the driver. H Brad Smith wrote: > At present, I am using the DBI module to open Access databases. As > the databases are rapidly growing, the performance is decreasing > greatly. > > If you had the following alternative options, which one would you > choose? > 1. MS SQL Server with corresponding MS SQL driver. > 2. MySQL Server with MyODBC driver. > 3. MySQL Server with MS SQL driver. > > Thanks in advance for offering advice. I don't know enough about how > each of these servers and drivers compares. > > Sincerely, > Brad Smith -- Henri Asseily BizRate.com [EMAIL PROTECTED] The best shopping experience! Chief Technologist http://www.bizrate.com/ "Apprends mon ami que la situation la mieux assise ne r�siste pas au pal." Iznogoud
