is a good idea to divide table?

[Ryan Liu]

Hi,

First, thanks for all answered my previous questions.

I have a data table which holds customers data. I am afraid overtime this
data table will grow too many rows (user might not want to maintain it). I
am thinking create one table per customer with identical table schema when
the customer row is inserted.

I have this idea because I never need look at the data in this table cross
customers. I assume by dividing the data table, I can search data faster,
and when deleting data or even drop the data table when a customer is
removed form customer table, it will leads to less fragment on hard disk.

Of cause the down side, is more complicated code, I might need build dynamic
sql string, and have difficult to make tools like Linq to sql to work.

Is this dividing table idea a nonsense or actually in use in database world?
Does it worth the trouble? Or there is better common practice?

Thanks a lot!
Ryan

 

[Ryan Liu]

Sorry, I intent to post this msg to microsoft.public.sqlserver.programming.
And posted here by mistake, sorry for that.