DBA Questionnaire
Jul 10, 2003Hi Mak,
Can you please send me the DBA questionnaire once again that you sent before?
Thanks Mak,
Jannat.
ADVERTISEMENT
Online Questionnaire W Connection To Database
Jul 23, 2005I'm currently developing an online questionnaire system for mydissertation and I have now come across a few problems. I'm developingan online approach recommendation system. The basic feature is that aclient will answer a number of questions online and based on theresults an approach will be recommended.There will be four pages with 5 questions on each site, this will allbe sent to a database and based on this an approach will be generated.I'm using mysql, php and html w/javascript for developing this but theproblem I have is that I'm not sure how the calculation andsuggestions will be coded. I've though of putting an average result into the database and then retrieve a ‘matching' approach based on thiswith querying using php.Any other recommendation is MUCH appreciated.many many thanks!
View 2 Replies View RelatedDesign Question For Survey/questionnaire Type Application
Dec 20, 2007I am a developer and I have a problem trying to design a system to
manage data coming from web surveys. On average each subject will take
part in more than one survey and each survey may potentially have 100+
questions.
I am focusing here only on the table(s) that will hold the survey
data.
I'm thinking about having a wide table storing each question in the
survey(s) as a column against the subjects. My main concerns with this
approach:
- the "yuckiness" and potentially other performance issues(?)
associated with a table with 100s of columns
- the 8kb size limit per row (unlikely to touch it, but possible)
- 1024 column limit (unlikely to touch it, but possible)
Another approach obviously is to have a single table where we have, in
a simplified version, 3 columns: person_id, question_id and data/
answer. The problem with this is that the "data" column will have to
accommodate
all types of data, from bits to varchars, and that field validation
seems now impossible jeopardizing data integrity, and most
importantly, you can't easily work with the data in filtering/
reporting etc.
What do knowledgeable designers come up with in this case? Can someone
point me in the right direction?