Finding Some Database Design Reviews

Question

I am currently working on a ticketing system that allows our users to send tickets based on their own needs. those. if Department A sends a ticket, it may have certain types of problem categories (such as Deliveries or Printer) along with details related to the selected category. I outlined a partial db design, and I was looking for some feedback on this. I never built a system from scratch, so I'm a little nervous.

here is my draft version of my db design

Problem table

Id | CreatedBy | CreateDate | Status | Owner | AssignedTo | AssignmentDate | 
-----------------------------------------------------------------------------

EquipmentIssueDetails Table

Id | IssueId | Serial # | Make | Model | ....
---------------------------------------------

SupplyIssueDetails table

Id | IssueId | SupplyId | ItemId | QTY | UnitOfMeasurement
-------------------------------------------------------------

NetworkIssueDetails table

Id | IssueId | Supervisor |  Details | 
-------------------------------------------------------------

Note table

Id | IssueId | Note | CreatedBy | CreateDate
-------------------------------------------------------------

Thanks in advance

Answer 1

, . , IssueTypeId

Id, IssueTypeId, , CreateDate, ,

IssueTypes

Id,

Id, IssueId, AssignedTo, AssignmentDate,

, . , . : 1: , 2: , 3:

, , , "" / , Ikke, .

Answer 2

. , , .

, , /. , , . . !

. , , .

, . , , . .

, , .

OG . , . , , .

Answer 3

, . , .

. , .

, . , .

Answer 4

, . , , , ( , , ( ), ( ). - ? , ? , , , , , , , - ? , , ? s, nitty gritty .

By the way, do not let anyone tell you in the store of key values, this is the worst way to store data in a relational database. You not only have performance problems, but you also lose the ability to correctly set field restrictions (for example, whether they are needed or not), and you are forced to use fuzzy data types for some information that requires frequent conversions for the correct data type to perform functions.