Member Avatar for yaragalla_mural

I am actually new to schema designing. I have read few articles about data modeling and started building schemas for real time data. I have done one. I need guidance in my first steps. Just some one who can have a glance at it and can suggest mistakes that I have done. So that I can correct them and learn. If any one have interest to provide little bit of guidance please respond.

Any guidance at this stage would be a great help to me. Thanking you so much.

  • 2 Contributors
  • 6 Replies
  • 122 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by trudge

Dani AI

Generated

As suggested, the fastest way to get useful feedback is to post a plain, machine-readable schema and a short statement of what the database must do. Reviewers can do very little with a binary Access file or an unlabeled diagram. The following checklist shows exactly what to include so reviewers can spot design problems quickly.

  • A one-paragraph functional summary: core business rules, typical transactions, whether this is OLTP or reporting, expected row counts and growth.
  • Table definitions in plain text (or SQL CREATE TABLE): table name, column name, data type, nullability, default, primary key, foreign keys, and indexes.
  • A simple ER diagram (PNG/PDF) showing entity names, relationship lines and cardinality (1:1, 1:N, M:N).
  • 10–20 sample rows per table (CSV) for realistic data shape and values.
  • A short list of non-obvious rules (unique constraints, cascading deletes, computed values, audit columns).

Common mistakes to watch for: embedding multiple values in one column, missing junction tables for many-to-many relationships, storing derived/calculated fields instead of computing them, relying on nullable columns for “unknown” semantics, weak or undocumented keys, and wrong data types (dates or numbers stored as text). Also check that foreign keys and indexes exist for join columns you will query often.

Quick validation steps before reposting: write and run a few representative INSERT/UPDATE/DELETE scenarios to exercise FKs and constraints; run the top 5 queries your application will use and note which joins or filters are slow; review every column and ask “what rule forces this value and where is it enforced?” When you repost, include the plain text table definitions and the one-paragraph summary — that will let responders give targeted, practical fixes.

Recommended Answers

All 6 Replies

Member Avatar for trudge

Assuming you are talking about a relational database, what do you need to do? What have you done so far - show us something.

Member Avatar for yaragalla_mural

For sure I will post the attachment by evening.

Member Avatar for yaragalla_mural

Hi me again, I am adding a zip file which contains schema snap, business requirement doc, dbm file(MS Access) which contains all the tables and valid data. It is completly done. Just have a glance and point out the mistakes that i have done. Thanking you all.

datamodel.zip (104.49 KB)
Member Avatar for trudge

I don't use Word or Access so I can't help you there.

Member Avatar for yaragalla_mural

I don't use Word or Access so I can't help you there.

Tell me what is the most acceptable format for you. so that i can post the doc again using that software. Do you use open office? one other thing is even if you dont use Access i will post jpg of schema so that you can have a look at doc and also at the schema.

Member Avatar for trudge

Can you not just export the schema to a text file and post it and a note here describing what your database is supposed to do.

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.