If you can't store the values in a real DB, then that might be an option. You might consider using a temporary table if it's available in the database you're using, that way you don't have to worry about implicitly creating then destroying the table. The only problem is how temporary the temporary table may be. If you can do everything you need in one connection, then you should be good. Otherwise you'd want to use either a persistant connection or use a real table. You may also load all your CSV data into an array, but that may use up more memory and be slower and/or more cumbersome to search. You could try out a few scenarios and see how they work speed-wise and impact on system memory and such. -TG ----- Original Message ----- From: Danny Brow <maillist@xxxxxxxxxxxxxxx> To: PHP <php-general@xxxxxxxxxxxxx> Date: Mon, 10 Mar 2008 21:09:15 -0400 Subject: CSV speed > I have about 10 csv files I need to open to access data. It takes a lot > of time to search each file for the values I need. Would it be best to > just dump all the cvs files to an SQL db and then just grab what I need > from there? I'm starting to think it would make a lot of sense. What do > you guys think? > > Thanks, > Dan -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php