· Jack Young · Education  · 2 min read

Unit 18 (P2): Designing a Relational Database

This database is for an IT Support company who helps their clients with IT related issues. The database will need a ticket system where the client can make a ticket on the problem that they have which is assigned to an employee to solve.

This database is for an IT Support company who helps their clients with IT related issues. The database will need a ticket system where the client can make a ticket on the problem that they have which is assigned to an employee to solve.

Design a relational database for a specified user need (P2)

This database is for an IT Support company who helps their clients with IT related issues. The database will need a ticket system where the client can make a ticket on the problem that they have which is assigned to an employee to solve.

Relationships

This relationship represents the connection between the tables. The ClientCompanyT has a one-to-one relationship with the client as each company is related to each individual client. The client can submit many tickets to our IT Support ticket system which is why ClientT has a one-to-many relationship with TicketT. There can only be one department code upon the many codes which can link to many different employees as each employee in the IT Support Company specialises in one department. For example, one employee might specialise in Internet Issues and if the client submits a ticket that has the department code related to internet issues, than that employee will be assigned to complete the ticket. Having said that, each individual employee has a one-to-many relationship with TicketT as the employee can be assigned to multiple tickets. Also, there only can be one department that a ticket is linked to so this means that it has to be a one-to-one relationship.

Tables

I will have five tables in my relational database which are the following:

ClientT

Field NameData TypeField SizeValidation Rule
ClientID (PK)AutoNumberN/AN/A
FirstNameShort Text15N/A
LastNameShort Text15N/A
GenderShort Text6”Male” Or “Female”
CompanyID (FK)NumberN/AN/A
PhoneShort Text11N/A

ClientCompanyT

Field NameData TypeField SizeValidation Rule
CompanyID (PK)AutoNumberN/AN/A
CompanyNameShort Text30N/A
AddressShort Text30N/A
CityShort Text20N/A
CountyShort Text20N/A
PostalCodeShort Text8N/A
PhoneShort Text11N/A
EmailHyperlinkN/AN/A
WebsiteHyperlinkN/AN/A

EmployeeT

Field NameData TypeField SizeValidation Rule
EmployeeID (PK)AutoNumberN/AN/A
FirstNameShort Text15N/A
LastNameShort Text15N/A
GenderShort Text6”Male” Or “Female”
DOBDate/TimeN/AN/A
CityShort Text20N/A
CountyShort Text20N/A
PostalCodeShort Text8N/A
PhoneShort Text11N/A
EmailHyperlinkN/AN/A
DepartmentCode (FK)Short Text5>“IT000”
isWorkingYes/NoN/AN/A

DepartmentT

Field NameData TypeField SizeValidation Rule
DepartmentCode (PK)Short Text5>“IT000”
DepartmentNameShort Text20N/A

TicketT

Field NameData TypeField SizeValidation Rule
TicketID (PK)AutoNumberN/AN/A
ClientID (FK)NumberN/AN/A
DepartmentCode (FK)Short Text5>“IT000”
DescriptionShort Text255N/A
DateCreatedDate/TimeN/ADefault Value = Date()
DateCompletedDate/TimeN/AN/A
EmployeeID (FK)NumberN/AN/A
isCompletedYes/NoN/AN/A

Data Entry Forms

These are the layouts of the forms that I will create in the database for each table so that users can easily add, delete and save records without tampering with the database itself.

ClientT

ClientCompanyT

EmployeeT

DepartmentT

TicketT

Design Documentation

Data Flow Diagram

Entity Relationship Diagram

Back to Blog

Related Posts

View All Posts »
Unit 18 (P1, M1, D1): Relational Databases

Unit 18 (P1, M1, D1): Relational Databases

A relationship is a defined connection between the rows of two tables. This connection is general determined by values in selected columns from the parent table that correspond to values in the child table.