c# - Storing Data from Forms without creating 100's of tables: ASP.NET and SQL Server -


Let me describe the situation first. We host several alumni during each year and provide an online registration form for each program.

  1. An event with date, time, managers, internal billing information etc.
  2. with a registration record
  3. 1 or more attendees (name , Address, degree, etc.) Information about bio / demographic and alumni data payments and payments

We expect that all the above data columns in the table we store We do.

The problem is with the 'extra' field that we put on the form. Maybe it is a dinner and there is a veggie or carnivor option, maybe there is a bed and smoking option, or maybe alternative transportation option. It is very strange in "Can you add it in this form?" The types of requests we receive

At present, we store any non-standard data in JSONify and in a column (present), which is called 'extra', we can read this data in code but it Not suitable for inquiries. Our internal staff want to generate a quick report on Veggie Dinner for example.

In addition to creating a separate table for each form containing specific 'extra' data items, is there any other approach that makes your life (and reporting) easy? Any simulator working in the environment?

This is really the most difficult problem to solve efficiently. The SQL Server Customer Advisory Team has dedicated a white paper on the subject which I highly recommend to you.

You have basically 3 options:

  • Mean database ()

Each solution comes with fluctuations from the top of my hat, I can say that XML is probably the one who gives you the best balance of power and flexibility, but the optimum solution really depends on many factors. Is the data set size, the frequency at which new features are created, the actual process (ma And operators) who use these properties, and at least your team skills set (some may be better with some EAV solutions, some may be better with XML solutions) if the features are of the Central Authority Are made / managed under and adding new features is a fairly rare event, then the rare column can be a better answer.


Comments

Popular posts from this blog

paypal - How to know the URL referrer in PHP? -

oauth - Facebook OAuth2 Logout does not remove fb_ cookie -

wpf - Line breaks and indenting for the XAML of a saved FlowDocument? -