Hi @Srinivas Naraipeddi ,
Thank you for your reaching out and welcome to Microsoft Q&A!
During database design, the master tables are designed first. Since the purpose of master tables is to capture the system. The design of the master tables i.e. its columns and constraints describe the entities in the system. For example, user, account, customer etc. Generally, entities of the system are mapped to master tables.
A transaction is an activity performed by entities (master tables) within the system. These activities are captured in transaction tables and usually, these transaction entries have foreign keys to master records.
These events are associated with master records to ensure normalization. Because the transactions can quickly grow in large numbers. The analytics tools, OLTP, partitioning are applied on transaction tables. Most of the querying is done on transaction tables.
The Pie charts, line charts, and graphs are drawn using transaction tables. The design of transaction tables.
The following criteria helps us identify whether a table should be classified as master or transaction.
I hope this helps! If you have any more issues or need further assistance, feel free to share with us!
Best regards,
Lucy Chen
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
https://docs.microsoft.com/en-us/answers/support/email-notifications