table design approach, what is the flaw?
I have a table like below

tblQuestions	<br>
---------------<br>
ID(pk)	int<br>
CustomerID(fk) int<br>
QTypeID(fk)	int<br>
QNumber	int<br>
FieldName	varchar(max)<br>
FieldValue	varchar(max)<br>

clustered indexs on CustomerID, QTypeID, QNumber.<br>
For each combination CustomerID, QTypeID and QNumber, there will be 4 to 5 records. 
and, for each customerID there would be at max 250 records.<br><br>
Another way to design is to create 5 to 6 different tables with defined fields and customerid as foreign key with one record per customer. <BR><BR>

My Question is, after how many records does the first approach starts to effect perfomance or would it ever?<BR>

Do you see any thing wrong with this approach?  The maximum possible records might go upto 50 million records. <BR>

thank you


table design approach, what is the flaw?
===

I have a table like below

tblQuestions	<br>
---------------<br>
ID(pk)	int<br>
CustomerID(fk) int<br>
QTypeID(fk)	int<br>
QNumber	int<br>
FieldName	varchar(max)<br>
FieldValue	varchar(max)<br>

clustered indexs on CustomerID, QTypeID, QNumber.<br>
For each combination CustomerID, QTypeID and QNumber, there will be 4 to 5 records. 
and, for each customerID there would be at max 250 records.<br><br>
Another way to design is to create 5 to 6 different tables with defined fields and customerid as foreign key with one record per customer. <BR><BR>

My Question is, after how many records does the first approach starts to effect perfomance or would it ever?<BR>

Do you see any thing wrong with this approach?  The maximum possible records might go upto 50 million records. <BR>

thank you

