-2

I am trying to create an Inventory Database. There are four receipts used in our warehouse, namely

  1. Issue Ticket ,Used to Issue items other than spare parts (Vehicles)
  2. Shipping Ticket,Used to transfer items to other locations
  3. Parts Requisition and Issue Ticket,Used to issue spare parts
  4. Receiving Ticket, used to receive items and add to the warehouse inventory

PartsRequisitionAndIssueTicket
ShippingTicket
ReceivingTicket
IssueTicket

The tickets have almost similar structure.

Should I create a different table for each ticket or is there a way to use a single table to store transactions?

philipxy
  • 14,867
  • 6
  • 39
  • 83
sorsa mele
  • 19
  • 4
  • [Why should I not upload images of code/data/errors when asking a question?](https://meta.stackoverflow.com/q/285551/3404097) – philipxy Mar 21 '23 at 07:43
  • Please before considering posting: Pin down code issues via [mre]. Read manuals/references & google error messages & many clear, concise & precise phrasings of your question/problem/goal, with & without your particular names/strings/numbers, 'site:stackoverflow.com' & tags; read many answers. SO/SE search is poor & literal & unusual, read the help. Google re googling/searching, including Q&A at [meta] & [meta.se]. [How much research effort is expected of Stack Overflow users?](https://meta.stackoverflow.com/q/261592/3404097) [ask] [Help] Reflect research in posts. – philipxy Mar 21 '23 at 07:45

1 Answers1

-1

as i see that these 4 data is different it terms of its structure and metadata i would suggest to create different tables for these info and there should be a primary-foreign relation between these tables to make sure they are consistent. Also I am assuming the new data will mostly be new records and minor updates to the rows and they evolve.

Keeping it in once single table will not be feasible on a wrong run and query performance will take a hit.

Karthik Gopalaswamy
  • 11
  • 3