
October 21st, 2004, 12:53 AM
|
 |
Contributing User
|
|
Join Date: Oct 2004
Location: Honolulu
Posts: 184
  
Time spent in forums: 20 h 29 m 2 sec
Reputation Power: 8
|
|
|
If you properly index your 1 table it should not be slower than making the database chug 30 times against 6 tables. Every table has behind-the-scenes information stored in system tables. This is where SQL Server retrieves indexes and primary keys for peforming selects, for deciding how many times to scan a table when looking for data etc... You would end up with 6 times the number of places SQL Server has to go retrieve this informaiton if you break it up. You said your tables have 800 rows. Times 6 that is a measly 4,800 records. 800 or 4.800 is not significant number of records to SQL Server. I would say create one table and create an index on those fields most commonly searched so SQL server can be as fast as possible retrieving the data, and index any fields you may use for joining to other tables if they are not already part of a foreign key (which they should be).
|