Member Avatar for mir_sheely

I am doing a survey for writing a technical report (Part of my BS technical report writing course.) I have chose the subject as which database Management System people select when writing database application while keeping in view their preference and options.

So please help me, kindly take your time and just fill this (14 questions) questionnaire, so I can complete my Primary research. Do me favor please.

Link to Questionnaire.

thanks and regards.

  • 2 Contributors
  • 2 Replies
  • 120 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by mir_sheely

Dani AI

Generated

Brief expert note addressing the thread and the exchange between and . Surveys about DBMS feature preferences can be a valid teaching exercise, but to make results useful even as an example, structure questions around feature categories and context rather than brand names. Collect both importance (how much a feature matters) and satisfaction/experience (how well the respondent’s current DBMS meets that need).

Core feature categories to include and why:

  • Transaction model and isolation/durability needs (ACID semantics and alternatives) — drives choice for OLTP vs OLAP systems (ACID (computer science)).
  • Scalability and replication (vertical vs horizontal, sharding, read replicas).
  • Performance controls: indexing types, query optimizer visibility, and execution plans.
  • Data model and schema flexibility (relational, document, hybrid) and migration tooling.
  • Backup, recovery, failover and point-in-time restore.
  • Security and compliance: auth, encryption, auditing, role-based access.
  • Tooling and ecosystem: connectors, GUI/admin tools, monitoring, ORMs.
  • Licensing, cloud/managed options, and extensibility (UDFs, procedural languages).

Survey design tips (methodology and validity): keep it short, pretest with a small group, use Likert scales for importance, allow multiple selections and an open "other" field. Capture respondent context: role, primary use case (OLTP/analytics/event sourcing), typical data size, and concurrency requirements. Report sample size, recruitment method and clear limitations—small convenience samples are fine for coursework but must not be presented as generalizable findings (Survey methodology).

A practical analysis step is to cross-tab feature importance by experience and primary use case; that reveals which features are deal-breakers for production-critical systems versus hobby projects.

Recommended Answers

All 2 Replies

Member Avatar for jwenting

if you had any common sense you'd know that any such random "research" is utterly useless.

Member Avatar for mir_sheely

Oh, you took it wrong.
This research/survey not being done for any benefit of people or database administrators, nor it is meant for it. It is done as a dummy or example survey for preparing technical report for TRW course.
A report is done via secondary and than primary research. And then it includes interpretation of information gained from that survey. It is basically done for demonstrating the skills of technical report writing.
The skill to be learned is how to prepare a technical report, not on providing a survey based article over choosing DBMS, it is useless from that perspective..
Now I think you got an idea and wont mind sparing ur some time by filling my form.
Thanks..

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.