I am using a simple aspx page to calculate a person's tax filing status and capturing statistical information. Most of the items are drop down boxes or radio buttons but a few are checkboxes.
Question
My plan is to give each option in the check boxes its own column in the database this will lead to a table that is 70 columns wide. Is that to many? Most of the info will be very small like "yes" or "no". I will be using a stored procedure to insert the info. This will be coming down a VPN
Goal
I would like to give the admin staff here real time access to the data via link tables and such. I would like there to be only one table so it will be easy for them to pars the info quickly without needing to join tables or write unions. Ideally this would get me out of the business of creating one off reports.I would recomend a more normalized table design.
If your admin users want to view the data de-normailzed you can create a view which accomplishes this.|||Go to the SQL Server Web site and look for the SQL Server 2000 AdventureWorks, it will get you create table statements that is close to what you are looking for because I takes table Reationship to Upper and Lower bound Cardinality. The only human interpretation of Peter Chen ERD relational Algebra. Hope this helps.
Kind regards,
Gift Peddie
No comments:
Post a Comment