SQL Server 2000 DB design question

[permissiondenied]

I wish to include a new table in my database which will hold up to 150 different records (17 columns with mostly int values) per customer for a possible 10,000 customers giving me a possible 1,500,000 records in the table.

I will be accessing this table via ASP for the web and pulling only the records belonging to a particular customer.

My question is would this be an acceptable table on its own or is it best to break out to individual tables per customer or groups of customers, my considerations are the speed of the query (which would be a simple SELECT * FROM tbl WHERE custID = ) when executed.

I am afraid I am rather new to SQL Server and this type of database design, I come from a flat txt file db background and probably have unneccessary performance worries.

Great forum, thanks.

Phil

 

[fluteplr]

I would put it all in one table with a clustered index on the custid.

 

[Sawatzky]

Dear Phil,

I agree with fluteplr put it into a single table.

When using the simple SELECT - statement, take the time to do it like this:

Select field1, field2, field3, anotherone from tbl

There are 2 reasons for this.

first is performance.
second is maintenance of code.

regards Astrid