how many field is rational in one table

Hi there,
I have a program whose database is in SQL.
My fields numbers are more than 250 and as I normalized it one of my tables
has 250 fields.
Is that rational and possible to have 250 fields in only one table and is
that affects the speed of my program?
Thanks in advance
RedhIt is always advisible to have less number of fields (columns).
It is easy to maintenance and write simple queries if columns are less.
Normalization is a technique to reduce redudancy.
Reducing the columns in a table increases the performance of the system
because you will not be using all the 250m columns in one query.
Try to split the table further. Hope this answers your question
best Regards,
Chandra
---
"redha" wrote:

> Hi there,
> I have a program whose database is in SQL.
> My fields numbers are more than 250 and as I normalized it one of my table
s
> has 250 fields.
> Is that rational and possible to have 250 fields in only one table and is
> that affects the speed of my program?
> Thanks in advance
> Redh
>
>|||Is it necessary to have 250 columns in a single table? Otherwise Look
for normalization
Madhivanan|||No 250 fields in one table would definitely cause you performance issues. I
n
my experience having taken flat file (AS400) data and broken it apart into
understandable data in SQL Server I know the seriousness of having too many
fields in one table. You want to take segments of the data that does not fi
t
the normaliziation process and extract that data into smaller subset tables
that are easily managed. When all the data for all departments for instance
is tacked onto one record in a large table when you go to pull data in or ru
n
major processes you are going to have a lot of lag time because even if the
table is indexed the process still has to run through every record and
caching each records data in memory to return you results sets. I would
suggest taking the data and identify what information is related to what and
breaking it down so that you dont run into major issues.
Hope this helps.
"redha" wrote:

> Hi there,
> I have a program whose database is in SQL.
> My fields numbers are more than 250 and as I normalized it one of my table
s
> has 250 fields.
> Is that rational and possible to have 250 fields in only one table and is
> that affects the speed of my program?
> Thanks in advance
> Redh
>
>|||First of all, columns are not fields; totally different concepts!
Next, there is no "magic number" of columns in a normalized table. But
from experience, 250 columns sounds like a design problem. Are you
sure that you are in 3NF now? If so, look for 4NF problems and MVDs.