Project part 2 completed

Project part 2 completed - Page | 1 TABLE: CUSTOMER...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
P a g e | 1 TABLE: CUSTOMER Business Rules : If a customer’s issue with an item cannot be resolved by the customer service representative then the representative is to involve a manager. If a customer makes more than $150 in beach accessories they will get 5% off their next purchase. Customers are given punch cards to be given to the sales representative when they are rung up at the register. Data Structure: CUSTOMER( CustomerID , CustomerFirstName, CustomerLastName , CustomerStreet, CustomerCity, CustomerState, CustomerCreditLimit, CustomerCurrentBalance, CallID (fk to call) ) Table Structure: Column Name Data Type Allow Nulls? Comments: CustomerID Integer NO Unique, Primary Key,and indexed CustomerFirstName Varchar (25) NO CustomerLastName Varchar (25) NO CustomerStreet Varchar (25) NO CustomerCity Varchar (25) NO CustomerState Varchar (5) NO CustomerCreditLimit money NO CustomerCurrentBalanc e money NO CallID Integer NO FK References CallId in Call Physical Design Issues: Data Volume Data Volatility and Throughput Additional Considerations 1000 records (est.) 1 update per day, 50 queries per week Increase security for privacy of customers Denormalize the address fields to increase the performance
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
P a g e | 2 TABLE: CALL Business Rules : The representative will stay on the phone with customer until all of the customers issues are resolved. EmployeeID is a foreign key that references the Employee who resolved the call or took the call. Data Structure: CALL(CallId , ProductNumber , CustomerId , Date, CallTime, CallIssue, CallResolution, EmployeeId ) Table Structure: Column Name Data Type Allow Nulls? Comments: CallId Integer NO Pk, indexed and unique ProductNumbe r Integer NO Fk that references ProductNumber in Product CustomerId Integer NO Fk that references CustomerID in Customer CallDate Integer NO CallDate should be prior to todays date unless CallTime Integer NO CallTime needs to be notated in am/pm CallProblem Nvarchar (150) NO CallResolution
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 8

Project part 2 completed - Page | 1 TABLE: CUSTOMER...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online