RE: [PHP] insertion question

My experience, at least from Oracle and SQLServer, is that very large tables (many millions of records) is not really a problem as long as you design and index well. Where you'll run into problems is when you try to join 2 very large tables together on the fly. This is where you'll need to do prejoins or look into the whole db wharehouse/OLAP design methodology. So I recommend you use one large table with 3 columns (or 4 if you need the source file info or some surrogate key). This will be a much sleeker and flexible db design, and it sounds like you will not be doing any joins between 2 or more large tables any way. Johan Alfredeen PongWorld.com -----Original Message----- From: Pétur Björn Thorsteinsson [mailto:petur.bjorn.thorsteinsson@islandssimi.is] Sent: Tuesday, August 14, 2001 11:49 AM To: php-general@lists.php.net Subject: [PHP] insertion question I have to store a whole lot of text files into a database, each one containing 3 columns containing numbers and about 2500 lines. I was wondering if anyone knew which would be the best way to store these files, having one big table with each row containing the contents of the files, or making one table for each file and inserting each line of the file into its respective row in the database. The database will probably become pretty big and I'm looking for the option that won't slow it down too much. -petur -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net