OSU Systems Support

8/9/2019 OSU Systems Support

1/217

Team 2 Project Milestone

1

MSIS 5643 Advanced Database Management Systems

OSU Systems Support Tool

System Documentation Milestone 1 - 8

By

Team 2

Shreepradha Ravi

Amar Gaikwad


2/217


2

Milestone 7 & 8

System Documentation with User Manual & Prototype Screenshots

User Manual for the OSU System Support Tool

This is a user manual with complete step-by-step details for using the OSU Systems support tool.

Step 1:

Type the following URL on the address bar and you will be directed to the login page

http://courses.msis.okstate.edu/Summer2009/MSIS5643/Team2/Login.aspx

Since the system is a single logon system, there will be only one login common for all the

specialists. Every specialist will have the complete access to all the data.

Once the Specialist login credentials i.e., the username and password are provided, click on

submit.

Username : OSU

Password : OSUSpecialist


3/217


3

If the Specialist enters a wrong username and password, the following error message as shown in

the screenshot below is displayed.

Step 2:Accessing Specialist Information

After the specialist logs in, the following Specialist home page will be displayed. The site map

on the left hand side will help the specialist to navigate to the page he wishes to access.


4/217


4

Step 2.1:

The specialist can access all the specialist information. By clicking on the Show all specialists

button, it gives the list of all the specialist currently employed at the Systems support. This is

shown in the screenshot below.


5/217


5

Additionally can access the information by searching using the specialist ID or by name

a. Searching using the Specialist IDThe required specialist Id is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete specialist details related to that Specialist ID are displayed.


6/217


6

b. Searching using the Specialist nameThe Specialist name is entered in the corresponding text box for name and the FIND button isclicked. The complete details related to the particular specialist are displayed.

Step 3:Accessing User Information

Step 3.1:

If the Specialist wants to view the user specific information, he will click on the Users in the

site map. Then the Users info is clicked to view details and reports of the residential life users

personal information. The following Users screen will be displayed.


7/217


7

In this Users screen, the Specialist can click the Show all Users to view all the Residential Life

Users Personal Information. This is shown in the below screen shot.


8/217


8

Additionally, the specialist can search for the User information based on the User ID or the

Users first name and last name.

a. Searching using the User IDThe required User Id is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete user details related to that User ID are displayed.

b. Searching using the User First Name and Last nameThe user First name is entered in the corresponding text box for First name and User Last nameis entered in the corresponding text box for Last name and the FIND button is clicked. Thecomplete user details related to the particular User are displayed.


9/217


9

Step 3.2:

The Specialist can navigate and view the User System Information with the help of the site map

by clicking on the User-System. This page will show the details of the systems associated with

the Residential Life users. In this screen, the Specialist can either click the Show all Users to

view all the Residential Life Staff System Information. This is shown in the below screen shot.


10/217


10

Additionally, the specialist can search for the User-system information based on the User ID or

the System name.

a. Searching using the User IDThe required User Id is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete system details related to that User ID are displayed.


11/217


11

b. Searching using the System NameThe System name is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete system details along with the associated user information are

displayed.


12/217


12

Step 3.3:

The Specialist can navigate and view the User Printer Information with the help of the site map

by clicking on User-printer. This page will show the details of the printers associated with the

Residential Life users. In this screen, the Specialist can either search using the User first nameand last name or can search using the system name.

a. Searching using the User First Name and Last name

The user First name is entered in the corresponding text box for First name and User Last nameis entered in the corresponding text box for Last name and the FIND button is clicked. Thecomplete printer details related to the particular User are displayed.


13/217


13

b. Searching using the System NameThe System name is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete printer details related to the particular User are displayed.


14/217


14

Step 4:Accessing System Information

Step 4.1

If the Specialist wants to view the system specific information, he will click on the System in

the site map. The following System Hardware screen will be displayed.

This will give the complete details of the hardware components installed in the system. The

Specialist can either search the system hardware information using the User first name and last

name or using the system name.

a. Searching using the User First Name and Last nameThe user First name is entered in the corresponding text box for First name and User Last nameis entered in the corresponding text box for Last name and the FIND button is clicked. The

complete System hardware details related to the particular Users system are displayed.


15/217


15

b. Searching using the System NameThe System name is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete System hardware details related to the particular Users system

are displayed.


16/217


16

Step 4.2

The Specialist can navigate and view the System Software Information with the help of the site

map by clicking on System Software. This page will show the details of the Software installed

in the Residential Life Users Systems. In this screen, the Specialist can either search using the

User first name and last name or can search using the system name.

a. Searching using the User First Name and Last nameThe user First name is entered in the corresponding text box for First name and User Last nameis entered in the corresponding text box for Last name and the FIND button is clicked. Thecomplete System software details installed in the particular Users system are displayed.


17/217


17

b. Searching using the System NameThe System name is chosen from the drop down list and the FIND button is clicked.Correspondingly, the complete System Software details installed in the particular Users system

are displayed.


18/217


18

Step 4.3

The Specialist can navigate and view the System Key application Software Information with the

help of the site map by clicking on System Key Software. This page will show the details of

the Key Software like Judicial Officer and StarRez installed in the Residential Life Users

Systems. In this screen, the Specialist can search by the name of the key application softwareinstalled in the system.

a. Systems in which Judicial Officer is installed


19/217


19

b. Systems in which StarRez is installed

c. Systems in which both Judicial Officer and StarRez is installed.


20/217


20

Step 5:Accessing Vendor Information

Step 5.1

If the Specialist wants to view Vendor information, he will click on Vendors in the site map.

This page will give the complete details of the vendors from whom the hardware components,software and systems are purchased. The Specialist can search for the vendor information using

the Vendor Name. This is shown in the following screen shot.

Step 6:Accessing Inventory Details

Step 6.1

If the Specialist wants to view Inventory details he will click on Inventory in the Site map.This page will give the complete details including warranty information of the components in the

inventory. The Specialist can search for the inventory details either by viewing all the

components in the inventory or by searching using the component name.


21/217


21

a. Viewing details of all components

b. Searching using the component nameThe component name is chosen from the drop down list and the SELECT button is clicked to

display the complete warranty details of the component. This is shown in the screen below.


22/217


22

Step 7:Accessing Salvage Information

Step 7.1

If the Specialist wants to view the salvage information, he will click on Salvage in the site

map. The Specialist can then access the System salvage information and component salvageinformation.

System Salvage Information

The Specialist will click on the Salvage Info in the site map. In this page the specialist can

search using the System name to view the details of the salvaged systems.

Step 7.2

Component Salvage Information

The Specialist can navigate and view the Component Salvage Information with the help of the

site map by clicking on Component Salvage. The details of the salvaged hardware components

are searched by the component name. This is shown in the following screenshot.


23/217


23

Step 8:Accessing the Issue Details

Step 8.1

If the Specialist wants to view the Issue details, he will click on Issue in the site map. The

specialist can search the complete details of the issue by selecting the Issue ID from the drop

down box. This is shown in the following screenshot.


24/217


24

The specialist can also edit the details of the issue by clicking on edit option.

Step 8.2

The Specialist can navigate and view the page to search the issue details with the help of the site

map by clicking on Issue Search. The issues can be searched by the following methods

a. Using User IDThe specialist can search for a particular issue by checking the User ID option and by selectingthe User ID from the drop down box. Once the Specialist clicks on the SEARCH button, it will

list the complete Issue details. This is shown in the below screenshot.

b. Using Issue StatusThe specialist can search for a particular issue by checking the Status option and by selecting theIssue status from the drop down box. Once the Specialist clicks on the SEARCH button, it willlist the complete Issue details. This is shown in the below screenshot.


25/217


25

c. Using Issue TypeThe specialist can search for a particular issue by checking the Type option and by selecting theIssue type from the drop down box. Once the Specialist clicks on the SEARCH button, it will

list the complete Issue details. This is shown in the below screenshot.


26/217


26

d. Using SpecialistThe specialist can search for a particular issue by checking the specialist option and by selectingthe Specialist Id from the drop down box. Once the Specialist clicks on the SEARCH button, it

will list the complete Issue details worked by the specific specialist. This is shown in the below

screenshot.

A search based on a combination of the given options can also be done. This is shown is the

screenshot below:


27/217


27

Step 8.3

The Specialist can record details about a new issue that was reported by the users. This is shownis the below screenshots


28/217


28

Step 9:Accessing the Knowledgebase Details

Step 9.1

If the Specialist wants to view the Knowledgebase information, he can navigate through the site

map and can click on Knowledgebase. The specialist can then click on Knowledgebase

details in the site map to view all the knowledgebase information which will contain the

solution for all the resolved issues. The Specialist can click the Show all Knowledgebase Posts

to view all the solution set for all the resolved issue. This is shown in the below screen shot.


29/217


29

Additionally, the specialist can search the knowledgebase based on the Knowledgebase ID

(KBID) or by the knowledgebase title.

a. Search using KBIDThe specialist can search for a particular knowledgebase post by selecting the KBID from the

drop down box. On clicking the FIND button, all the details of the knowledgebase post islisted. This is shown in the below screenshot.


30/217


30

b. Search using Knowledgebase TitleThe specialist can search for a particular knowledgebase post by entering any keyword or phraseof the Knowledgebase title. On clicking the FIND button, the details of all the knowledgebase

posts with the mentioned keyword in their title is listed. This is shown in the below screenshot.

Step 9.2

Creating a new knowledgebase entry

The specialist can create a new knowledgebase entry once an issue is resolved. This is shown in

the screenshots below


31/217


31

Step 10:Accessing the Order Details

Step 10.1

If the Specialist wants to view the Order information, he will click on Orders in the site map.

This will contain the details of all the orders placed with the vendors. The Specialist can view the

order details by the following methods:

a. Search using Order IDThe specialist can search for a particular Order placed by choosing the Order ID option and by

selecting the Order ID from the drop down box. On clicking the FIND button, all the orderdetails corresponding to the mentioned Order ID is listed. This is shown in the below screenshot.


32/217


32

b. Search using Order StatusThe specialist can search for a particular Order placed by choosing the Order Status option and

by selecting the Order Status from the drop down box. On clicking the FIND button, all theorder details corresponding to the mentioned Order Status is listed. This is shown in the below

screenshot.


33/217


33

c. Viewing all OrdersThe specialist can view all the orders placed with the vendors by choosing the Select ALLoption. On clicking the FIND button, all the order details placed with the different vendors are

listed. This is shown in the below screenshot.

Step 10.2

Creating new order information

The specialist can enter the new order information once placed with the vendor. This is shown in

the below screenshots


34/217


34


35/217


35

On clicking the Submit the new order button, it says that the record was inserted successfully

In case if few details required were not listed, then it gives corresponding messages against thespecific field. In the below screen shot, the message is shown against the Comments field.

Step 11: Admin Functionalities - Admin Login


36/217


36

The specialist needs to login as an ADMIN to perform the various Updates in the database. The

following URL on the address bar and you will be directed to the login page.


The Specialist can also navigate to the admin from the site map and can login with the adminUsername and password. This is shown in the screenshot below

Username : OSU

Password : OSUAdmin

Once the login is successful, the specialist is directed to the Admin Home page.


37/217


37

If the Specialist enters a wrong username and password, the following error message as shown in

the screenshot below is displayed.


38/217


38

Step 12:Database Management

The Specialist can perform various database management activities once he had logged on as anadmin. This is shown in the screenshot below:

The Specialist can perform the various activities as listed below

a. Deleting Database


39/217


39

b. Creating Database

c. Database Backup


40/217


40

d. Restoring Database

e. Deleting Backup Database


41/217


41

Step 13:Administering the Specialist Details

The Admin can perform the following tasks for managing the specialist Information

a. InsertTo insert a new record i.e., new specialist information, the new option in the detail

view table is clicked and the information is entered. On clicking the Refresh button, theupdated information is displayed. This is shown in the screenshot below.


42/217


42

b.

Edit

To edit the details about an existing specialist, the specialist ID is chosen from the drop

down list and the Edit option in the detail view table is clicked and the field required tobe updated is changed and the update option is chosen. On clicking the Refresh button,

the updated information is displayed. This is shown in the below screenshot.


43/217


43


44/217


44

c. DeleteTo delete particular specialist information, the specialist ID is chosen from the drop downlist and the delete option is clicked on the specific specialists page. On clicking the

Refresh button, the deleted record is removed.

Step 14:Administering the User Details

a. EditThe user required to be edited is selected and the Edit option is chosen to edit the userdetails. On clicking the Refresh button, the updated information is displayed.


45/217


45


46/217


46


47/217


47

b. InsertTo insert any new user information, any user can be selected and the new option ischosen to insert a new record. On clicking the Refresh button, the updated information

is displayed.


48/217


48

c. DeleteTo delete a particular Users information, the delete option is chosen against the specificuser. On clicking the Refresh button, the deleted record is removed.


49/217


49

Step 15:Administering the Vendor Details

The Admin can perform the following tasks for managing the vendor Information

a. InsertTo insert a new record i.e., new vendor information, the new option in the detail view

table is clicked and the information is entered. On clicking the Refresh button, theupdated information is displayed. This is shown in the screenshot below.

b. EditTo edit the details about an existing vendor, the vendor ID is chosen from the drop down

list and the Edit option in the detail view table is clicked and the field required to beupdated is changed and the update option is chosen. On clicking the Refresh button, the

updated information is displayed. This is shown in the below screenshot.


50/217


50


51/217


51

c. DeleteTo delete particular vendor information, the vendor ID is chosen from the drop down listand the delete option is clicked on the specific vendors page. On clicking the Refresh

button, the deleted record is removed.

Step 16:Administering the System Details

The Admin can perform the following tasks for managing the System Information

a. InsertTo insert a new record i.e., new system information, the new option in the detail viewtable is clicked and the information is entered. On clicking the Refresh button, the

updated information is displayed. This is shown in the screenshot below.


52/217


52

b. EditTo edit the details about an existing System, the system service tag is chosen from the

drop down list and the Edit option in the detail view table is clicked and the fieldrequired to be updated is changed and the update option is chosen. On clicking theRefresh button, the updated information is displayed. This is shown in the below

screenshot.


53/217


53


54/217


54

c. DeleteTo delete particular systems information, the system service tag is chosen from the dropdown list and the delete option is clicked on the specific systems page. On clicking the

Refresh button, the deleted record is removed.

Step 17:Administering the Hardware Component details

The Admin can perform the following tasks for managing the Hardware component Information

a. InsertTo insert a new record i.e., new component information, select any component serialnumber and corresponding vendor id from the drop down box. The new option in thedetail view table is clicked and the information is entered and the insert option is clicked.

On clicking the Refresh button, the new record inserted is displayed. This is shown inthe screenshot below.


55/217


55

b. EditTo edit the details about an existing component, the component serial number andcorresponding vendor id is chosen from the drop down list and the Edit option in the

detail view table is clicked. The field required to be updated is changed and the updateoption is chosen. On clicking the Refresh button, the updated information is displayed.

This is shown in the below screenshot.


56/217


56


57/217


57

c. DeleteTo delete particular hardware components information, the delete option against thespecific component is clicked in the grid. On clicking the Refresh button, the deleted

record is removed. This is shown in the screenshot below.

Step 18:Administering the Systems Hardware Component details

The Admin can manage the mapping of the systems and its corresponding hardware components.

a. InsertTo insert new hardware component information associated with a system, the componentserial no, its corresponding vendor id and the system service tag is chosen from the drop

down box and the Insert button is clicked. This is shown in the screenshot below.


58/217


58

b. DeleteTo delete particular Systems hardware component information, the delete option againstthe specific record is clicked in the grid. This is shown in the screenshot below.


59/217


59

The details cannot be edited as the serial no, vendor id and the system service tag are keycomponents.

Step 19:Administering the Printer details

The Admin can manage the mapping of the systems and its corresponding hardware components.

a. InsertTo insert a new record i.e., new Printers information, the new option in the detail view

table is clicked and the information is entered and the insert option is chosen. On clickingthe Refresh button, the updated information is displayed. This is shown in the

screenshot below.


60/217


61/217


61

c. DeleteTo delete particular printers information, the component serial no and the correspondingvendor id is chosen from the drop down list and the delete option is clicked on the

specific printers page. On clicking the Refresh button, the deleted record is removed.

Step 20:Administering the Software details

The Admin can manage the software information in the following different ways

a. InsertTo insert a new record i.e., new software information, the new option in the detail viewtable is clicked and the information is entered and the insert option is chosen and the

information is updated. This is shown in the screenshot below.


62/217


62

b. EditTo edit the details about an existing Software, the software license no and thecorresponding vendor id is chosen from the drop down list and the Edit option in the

detail view table is clicked. The field required to be updated is changed and the updateoption is chosen and the updated information is displayed. This is shown in the below

screenshot.


63/217


63

c. DeleteTo delete particular software information, the software license no and the correspondingvendor id is chosen from the drop down list and the delete option is clicked on the

specific softwares page and the record is deleted.

Step 21:Administering the Issue details

The Admin can manage the various issue information.

a. InsertTo insert a new record i.e., new issue information, the new option in the detail view

table is clicked and the information is entered and the insert option is chosen. This isshown in the screenshot below.


64/217


64


65/217


65

b. EditTo edit the details about an existing issue, the issue id is chosen from the drop down listand the Edit option in the detail view table is clicked. The field required to be updatedis changed and the update option is chosen. On clicking the Refresh button, the updated

information is displayed. This is shown in the below screenshot.


66/217


66


67/217


67

c. DeleteTo delete particular issue information, the issue id is chosen from the drop down list andthe delete option is clicked on the specific issues page. On clicking the Refresh button,

the record is deleted.

Step 22:Administering the Issues related to the Systems

The Admin can manage the information of the Issues reported on the systems

a. InsertTo insert new issue information associated with a system, the issue id and the

corresponding systems service tag is chosen from the drop down box and the Insert

button is clicked. This is shown in the screenshot below.

b. DeleteTo delete particular Systems issue information, the delete option against the specific

record is clicked in the grid. This is shown in the screenshot below.


68/217


68

The details cannot be edited as the issue id and the system service tag are keycomponents.

Step 23:Administering the Hardware components Issue details

The Admin can manage the information of the Issues reported on the Hardware components

a. InsertTo insert new issue information associated with a HW Component, the component serialno; its corresponding vendor id and the issue id is chosen from the drop down box and

the Insert button is clicked. This is shown in the screenshot below.


69/217


69

b. DeleteTo delete particular HW Components issue information, the delete option against thespecific record is clicked in the grid. This is shown in the screenshot below.


70/217


70

The details cannot be edited as the component serial no; vendor id and issue id are keycomponents.

Step 24:Administering the Softwares Issue details

The Admin can manage the information of the Issues reported on the Software

a. InsertTo insert new issue information associated with a Software, the software licence no; its

corresponding vendor id and the issue id is chosen from the drop down box and theInsert button is clicked. This is shown in the screenshot below.

b. DeleteTo delete particular softwares issue information, the delete option against the specificrecord is clicked in the grid. This is shown in the screenshot below.


71/217


71

The details cannot be edited as the software license no; vendor id and issue id are keycomponents.

Step 25:Administering the Knowledgebase Information

The Admin can manage the knowledgebase information by the following methods.

a. InsertTo insert new knowledgebase entry, the select option is clicked against any existing postand the new option is clicked in the detail view. The details are filled and the insert

option is clicked. On clicking the Refresh button, the inserted record is displayed. Thisis shown in the screenshot below.


72/217


72


73/217


73

b. EditTo edit an existing knowledgebase entry, the select option is clicked against the specificpost and the edit option is clicked in the detail view. The required details are edited and

the update option is clicked. On clicking the Refresh button, the edited details are

displayed. This is shown in the screenshot below.


74/217


74


75/217


75

c. DeleteTo delete particular Knowledgebase entry, the delete option against the specific record isclicked in the grid. On clicking the Refresh button, the record is deleted.


76/217


76

Step 26:Administering the Knowledgebase Issue mapping

The Admin can manage the information of the Knowledgebase posts related to issues

a. InsertTo insert new Knowledgebase information for an issue, the knowledgebase id and the

corresponding issue id is chosen from the drop down box and the Insert button isclicked. This is shown in the screenshot below.

b. DeleteTo delete particular Knowledgebase information for an issue, the delete option against

the specific record is clicked in the grid. This is shown in the screenshot below.


77/217


77

The details cannot be edited as the KBID and the issue id are key components.

Step 27:Administering the Order Details

The Admin can perform the following tasks for managing the Order Information

a. InsertTo insert a new record i.e., new order information, the new option in the detail viewtable is clicked. After the information is entered, the insert option is clicked. On clickingthe Refresh button, the updated information is displayed. This is shown in the

screenshot below.


78/217


78


79/217


79

b. EditTo edit the details about an existing Order, the order id is chosen from the drop down listand the Edit option in the detail view table is clicked. The field required to be updated

is changed and the update option is chosen. On clicking the Refresh button, the updated

information is displayed. This is shown in the below screenshot.


80/217


80

c. DeleteTo delete particular Order information, the order id is chosen from the drop down list andthe delete option is clicked on the specific orders page. On clicking the Refresh button,

the deleted record is removed.


81/217


81

Project Prototype Screenshots

Project link:


Screenshots

Login page


82/217


82

Admin Home Page


83/217


83

Admin-Database Management


84/217


84

Admin User Details Management


85/217


85

Admin - Specialist Details Management


86/217


86

Admin System Details Management


87/217


87

Admin Hardware Component details Management


88/217


88

Admin System Hardware Component Management


89/217


89

Admin Printer Details Management


90/217


90

Admin Software Details Management


91/217


91

Admin Issue Details Management


92/217


92

Admin System Issue Management


93/217


93

Admin Hardware Component Issue Management


94/217


94

Admin Software Issue Management


95/217


95

Admin Knowledgebase Information Management


96/217


96

Admin Knowledgebase Issue Management


97/217


97

Admin Order Details Management


98/217


98

Admin Vendor Details Management


99/217


99

Specialist Home page


100/217


100

Specialist Information


101/217


101

User Information


102/217


102

User System Information


103/217


103

User Printer Information


104/217


104

System Hardware Information


105/217


106/217


106

System Key Application Software Information


107/217


107

Vendor Information


108/217


108

Inventory Information


109/217


109

System Salvage Information


110/217


110

Component Salvage Information


111/217


111

Issue Information


112/217


112

Issue Search Page


113/217


113

New Issue Information


114/217


114

Knowledgebase Information


115/217


115

New Knowledgebase Information


116/217


116

Order Information


117/217


117

New Order Information


118/217


118

Milestone 6

Database Implementation in MS Access and SQL Server &

Project Stored Procedure

Tables in MS Access


119/217


119


120/217


120


121/217


121


122/217


122


123/217


123

Relationship Diagram in MS Access


124/217


124

Stored Procedure in MS SQL Server 2005:

The following is the Project Stored Procedure from SQL Server 2005. Note that the Identity

Specification has been defined for all the required fields. Additionally, the domain constraints for

various attributes have been defined.

The Stored Procedures are listed in the following order

1. Delete Database2. Create Tables3. Insert Data4. Create Database5. Delete Backup Database6. Create Backup Database7. Restore Database

USE [Summer2009_MSIS5643_Team2]

GO

/****** Object: StoredProcedure [dbo].[Delete_DB] Script Date: 07/19/2009

20:40:51 ******/

SETANSI_NULLSON

GO

SETQUOTED_IDENTIFIERON

GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Delete_DB]

AS

ALTERTABLE ResSystem DROPCONSTRAINT FK_ResSystem_ResUser;

ALTERTABLE HWComponent DROPCONSTRAINT FK_HWComponent_Vendor;


125/217


125

ALTERTABLE Printer DROPCONSTRAINT FK_Printer_HWComponent;

ALTERTABLE HWComponentSystem DROPCONSTRAINT

FK_HWComponentSystem_HWComponent;

ALTERTABLE HWComponentSystem DROPCONSTRAINT FK_PrinterSystem_System;

ALTERTABLE Software DROPCONSTRAINT FK_Software_System;

ALTERTABLE Software DROPCONSTRAINT FK_Software_Vendor;

ALTERTABLE Issue DROPCONSTRAINT FK_Issue_Specialist;

ALTERTABLE Issue DROPCONSTRAINT FK_Issue_User;

ALTERTABLE SystemIssue DROPCONSTRAINT FK_SystemIssue_Issue;

ALTERTABLE SystemIssue DROPCONSTRAINT FK_SystemIssue_System;

ALTERTABLE HWComponentIssue DROPCONSTRAINT

FK_HWCompIssue_HWComponent;

ALTERTABLE HWComponentIssue DROPCONSTRAINT FK_HWCompIssue_Issue;

ALTERTABLE SWIssue DROPCONSTRAINT FK_SWIssue_Issue;

ALTERTABLE SWIssue DROPCONSTRAINT FK_SWIssue_Software;

ALTERTABLE Knowledgebase DROPCONSTRAINT FK_Knowledgebase_Specialist;

ALTERTABLE KBIssue DROPCONSTRAINT FK_KBIssue_Issue;

ALTERTABLE KBIssue DROPCONSTRAINT FK_KBIssue_Knowledgebase;

ALTERTABLE ResOrder DROPCONSTRAINT FK_Order_Issue;

ALTERTABLE ResOrder DROPCONSTRAINT FK_Order_Specialist;

DELETEFROM SystemIssue;

DROPTABLE SystemIssue;

DELETEFROM HWComponentIssue;

DROPTABLE HWComponentIssue;

DELETEFROM SWIssue;

DROPTABLE SWIssue;


126/217


126

DELETEFROM KBIssue;

DROPTABLE KBIssue;

DELETEFROM Knowledgebase;

DROPTABLE Knowledgebase;

DELETEFROM ResSystem;

DROPTABLE ResSystem;

DELETEFROM HWComponentSystem;

DROPTABLE HWComponentSystem;

DELETEFROM HWComponent;

DROPTABLE HWComponent;

DELETEFROM Printer;

DROPTABLE Printer;

DELETEFROM Software;

DROPTABLE Software;

DELETEFROM Vendor;

DROPTABLE Vendor;

DELETEFROM Issue;

DROPTABLE Issue;

DELETEFROM ResUser;


127/217


127

DROPTABLE ResUser;

DELETEFROM ResOrder;

DROPTABLE ResOrder;

DELETEFROM Specialist;

DROPTABLE Specialist;

/* SET NOCOUNT ON */

RETURN


GO

/****** Object: StoredProcedure [dbo].[Create_Table] Script Date:

07/19/2009 20:36:49 ******/

SETANSI_NULLSON

GO


GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Create_Table]

AS

Createtable Specialist

(specialistId smallintIDENTITY(1, 1)NOTNULL,

specialistName nvarchar(50)NOTNULL,


128/217


128

specialistDesignation nvarchar(50)NOTNULLCONSTRAINT

DF_Consultant_consultantLevel DEFAULT((1)),

specialistContactNo numeric(10, 0)NULL,

specialistEmail nvarchar(50)NULL,

CONSTRAINT PK_Specialist PRIMARYKEY(specialistId),

CONSTRAINT SpecialistDesignation CHECK

((specialistDesignation='Specialist'OR specialistDesignation='GA')));

Createtable ResUser

(userId smallintIDENTITY(1, 1)NOTNULL,

userFirstName nvarchar(50)NOTNULL,

userLastName nvarchar(50)NOTNULL,

userEmail nvarchar(50)NOTNULL,

userContactNo numeric(10, 0)NOTNULL,

userLocation nvarchar(50)NOTNULL,

CONSTRAINT PK_ResUser PRIMARYKEY(userId));

Createtable ResSystem

(systemServiceTag nvarchar(50)NOTNULL,

systemName nvarchar(50)NOTNULL,

systemModel nvarchar(50)NOTNULL,

systemIP nvarchar(50)NULL,

systemMAC nvarchar(50)NOTNULL,

systemSalvaged bitNOTNULLCONSTRAINT DF_System_systemSalvaged

DEFAULT((0)),

userId smallintNULL,

CONSTRAINT PK_ReSystem PRIMARYKEY(systemServiceTag),

CONSTRAINT FK_ResSystem_ResUser FOREIGNKEY(userId)REFERENCES ResUser

(userId));


129/217


129

Createtable Vendor

(vendorId smallintIDENTITY(1, 1)NOTNULL,

vendorName nvarchar(50)NOTNULL,

vendorAddress nvarchar(50)NOTNULL,

vendorContactNo numeric(10, 0)NOTNULL,

vendorEmail nvarchar(50)NOTNULL,

CONSTRAINT PK_Vendor PRIMARYKEY(vendorId));

Createtable HWComponent

(compSerial nvarchar(50)NOTNULL,

vendorId smallintNOTNULL,

compName nvarchar(50)NOTNULL,

compDescription nvarchar(50)NOTNULL,

compPrinter bitNOTNULLCONSTRAINT DF_HWComponent_compPrinter

DEFAULT((0)),

compWarrantyEndDate SmalldatetimeNOTNULL,

compSalvaged bitNOTNULLCONSTRAINT DF_HWComponent_compSalvaged

DEFAULT((0)),

CONSTRAINT PK_HWComponent PRIMARYKEY(compSerial, vendorId),

CONSTRAINT FK_HWComponent_Vendor FOREIGNKEY(vendorId)REFERENCES

Vendor (vendorId)ONUPDATECASCADE);

Createtable Printer



compIPAddress nvarchar(50)NULL,

compMACAddress nvarchar(50)NOTNULL,

compLocation nvarchar(50)NULL,

CONSTRAINT PK_Printer PRIMARYKEY(compSerial, vendorId),


130/217


130

CONSTRAINT FK_Printer_HWComponent FOREIGNKEY(compSerial, vendorId)

REFERENCES HWComponent (compSerial, vendorId)ONUPDATECASCADEONDELETE

CASCADE);

Createtable HWComponentSystem



systemServiceTag nvarchar(50)NOTNULL,

CONSTRAINT PK_HWComponentSystem PRIMARYKEY(compSerial, vendorId,

systemServiceTag),

CONSTRAINT FK_HWComponentSystem_HWComponent FOREIGNKEY(compSerial,

vendorId)REFERENCES HWComponent (compSerial, vendorId)ONUPDATECASCADEON

DELETECASCADE,

CONSTRAINT FK_PrinterSystem_System FOREIGNKEY(systemServiceTag)

REFERENCES ResSystem (systemServiceTag)ONUPDATECASCADEONDELETECASCADE);

Createtable Software

(swLicenseNo nvarchar(50)NOTNULL,


swName nvarchar(50)NOTNULL,

swDescription nvarchar(50)NOTNULL,

swLicenseExpiryDate datetimeNOTNULL,

swKA bitNOTNULLCONSTRAINT DF_Software_swKA DEFAULT((0)),

swOS bitNOTNULLCONSTRAINT DF_Software_swOS DEFAULT((0)),

systemServiceTag nvarchar(50)NULL,

CONSTRAINT PK_Software PRIMARYKEY(swLicenseNo, vendorId),

CONSTRAINT FK_Software_System FOREIGNKEY(systemServiceTag)REFERENCES

ResSystem (systemServiceTag)ONUPDATECASCADE,

CONSTRAINT FK_Software_Vendor FOREIGNKEY(vendorId)REFERENCES Vendor

(vendorId)ONUPDATECASCADE);

Createtable Issue


131/217


131

(issueId smallintIDENTITY(1, 1)NOTNULL,

userId smallintNULL,

specialistId smallintNULL,

orderId smallintNULL,

issueReportDate datetimeNOTNULL,

issueCloseDate smalldatetimeNULL,

issuePriority smallintNOTNULLCONSTRAINT DF_Issue_issuePriority

DEFAULT((3)),

issueSource bitNOTNULLCONSTRAINT DF_Issue_issueSource DEFAULT

((1)),

issueType nvarchar(50)NULL,

issueStatus nvarchar(50)NOTNULLCONSTRAINT DF_Issue_issueStatus

DEFAULT('Open'),

issueComments nvarchar(50)NULL,

issueUserTimePreference nvarchar(50)NULL,

CONSTRAINT PK_Issue PRIMARYKEY(issueId),

CONSTRAINT FK_Issue_Specialist FOREIGNKEY(specialistId)REFERENCES

Specialist (specialistId),

CONSTRAINT FK_Issue_User FOREIGNKEY(userId)REFERENCES ResUser

(userId)ONUPDATECASCADE,

CONSTRAINT IssuePriority CHECK ((issuePriority=1 OR issuePriority=2 OR

issuePriority=3 )),

CONSTRAINT IssueType CHECK ((issueType='Hardware'OR

issueType='Software'OR issueType='Network'OR issueType='Training'OR

issueType='Updates')),

CONSTRAINT IssueStatus CHECK ((issueStatus='Open'OR

issueStatus='Working'OR issueStatus='WaitUser'OR issueStatus='WaitVendor'

OR issueStatus='Resolved'OR issueStatus='Closed')));

Createtable SystemIssue

(issueId smallintNOTNULL,

systemServiceTag nvarchar(50)NOTNULL,


132/217


132

CONSTRAINT PK_SystemIssue PRIMARYKEY(issueId, systemServiceTag),

CONSTRAINT FK_SystemIssue_Issue FOREIGNKEY(issueId)REFERENCES Issue

(issueId)ONUPDATECASCADEONDELETECASCADE,

CONSTRAINT FK_SystemIssue_System FOREIGNKEY(systemServiceTag)

REFERENCES ResSystem (systemServiceTag)ONUPDATECASCADEONDELETECASCADE);

Createtable HWComponentIssue



issueId smallintNOTNULL,

CONSTRAINT PK_HWCompIssue PRIMARYKEY(compSerial, vendorId, issueId),

CONSTRAINT FK_HWCompIssue_HWComponent FOREIGNKEY(compSerial,

vendorId)REFERENCES HWComponent (compSerial, vendorId)ONUPDATECASCADE,

CONSTRAINT FK_HWCompIssue_Issue FOREIGNKEY(issueId)REFERENCES Issue

(issueId)ONUPDATECASCADEONDELETECASCADE);

Createtable SWIssue

(swLicenseNo nvarchar(50)NOTNULL,



CONSTRAINT PK_SWIssue PRIMARYKEY(swLicenseNo, vendorId, issueId),

CONSTRAINT FK_SWIssue_Issue FOREIGNKEY(issueId)REFERENCES Issue

(issueId)ONUPDATECASCADEONDELETECASCADE,

CONSTRAINT FK_SWIssue_Software FOREIGNKEY(swLicenseNo, vendorId)

REFERENCES Software (swLicenseNo, vendorId)ONUPDATECASCADE);

CREATETABLE Knowledgebase

(kbId smallintIDENTITY(1, 1)NOTNULL,

kbTitle nvarchar(250)NOTNULL,

kbAuthor smallintNOTNULL,


133/217


133

kbVerified bitNOTNULLCONSTRAINT DF_Knowledgebase_kbVerified

DEFAULT((0)),

kbComponent nvarchar(50)NULL,

kbSw nvarchar(50)NULL,

kbDesc nvarchar(500)NOTNULL,

kbFix nvarchar(250)NOTNULL,

kbDate datetimeNOTNULL,

CONSTRAINT PK_Knowledgebase PRIMARYKEY(kbId),

CONSTRAINT FK_Knowledgebase_Specialist FOREIGNKEY(kbAuthor)

REFERENCES Specialist (specialistId)ONUPDATECASCADE);

CREATETABLE KBIssue

(kbId smallintNOTNULL,


CONSTRAINT PK_KBIssue PRIMARYKEY(kbId, issueId),

CONSTRAINT FK_KBIssue_Issue FOREIGNKEY(issueId)REFERENCES Issue

(issueId)ONUPDATECASCADE,

CONSTRAINT FK_KBIssue_Knowledgebase FOREIGNKEY(kbId)REFERENCES

Knowledgebase (kbId)ONUPDATECASCADEONDELETECASCADE);

CREATETABLE ResOrder

(orderId smallintIDENTITY(1, 1)NOTNULL,

orderReplacement bitNOTNULLCONSTRAINT DF_Order_orderReplacement

DEFAULT((0)),

orderStatus nvarchar(50)NOTNULL,

orderVendorOrderNo nvarchar(50)NULL,

orderExpectedDate datetimeNULL,

specialistId smallintNOTNULL,


issueId smallintNULL,


134/217


134

orderComments nvarchar(50)NULL,

CONSTRAINT PK_Order PRIMARYKEY(orderId),

CONSTRAINT FK_Order_Issue FOREIGNKEY(issueId)REFERENCES Issue

(issueId)ONUPDATECASCADE,

CONSTRAINT FK_Order_Specialist FOREIGNKEY(specialistId)REFERENCES

Specialist (specialistId)ONUPDATECASCADE,

CONSTRAINT OrderStatus CHECK ((orderStatus='Processed'OR

orderStatus='Complete'OR orderStatus='Declined'OR orderStatus='InTransit'

OR orderStatus='Shipped'OR orderStatus='Delivered')));


RETURN


GO

/****** Object: StoredProcedure [dbo].[Insert_Data] Script Date:

07/19/2009 20:37:11 ******/

SETANSI_NULLSON

GO


GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Insert_Data]

AS

INSERTINTO Specialist VALUES('Shree','GA', 76767868,'[email protected]');


135/217


135

INSERTINTO Specialist VALUES('Brad','Specialist', 87878,

'[email protected]');

INSERTINTO Specialist VALUES('Raj','GA', 67967897,'[email protected]');

INSERTINTO Specialist VALUES('Daniel','GA', 6734,'[email protected]');

INSERTINTO Specialist VALUES('Joane','GA', 67343,'[email protected]');

INSERTINTO Specialist VALUES('Preet','GA', 2344354,'[email protected]');

INSERTINTO Specialist VALUES('Amar','Specialist', 7777777,


INSERTINTO Specialist VALUES('Dev','GA', 3543535,'[email protected]');

INSERTINTO Specialist VALUES('Niks','GA', 67565,'[email protected]');

INSERTINTO Specialist VALUES('Shinny','GA', 7677778,


INSERTINTO ResUser VALUES('Shree','Shree','[email protected]', 777667,

'Wentz');

INSERTINTO ResUser VALUES('Brad','Baustert','[email protected]',

989634444,'Wentz');

INSERTINTO ResUser VALUES('Niks','Niks','[email protected]', 36473897,

'IBA');

INSERTINTO ResUser VALUES('Chris','Chris','[email protected]',3423534,'IBA');

INSERTINTO ResUser VALUES('Kevin','Brad','[email protected]', 34324,

'Bennett');

INSERTINTO ResUser VALUES('Michelle','Mascarenhas','[email protected]',

27634736,'Foxrun');

INSERTINTO ResUser VALUES('Amar','Gaikwad','[email protected]', 7777777,

'Foxrun');

INSERTINTO ResSystem VALUES('AAA123','RES-W2','Optiplex 720',

'12.23.44.55','AA:B2:C3:D4:E5','False', 2);

INSERTINTO ResSystem VALUES('ABC123','Res-W1','Optiplex755',

'1.2.3.4','AB:C2:34:44:55','False', 1);

INSERTINTO ResSystem VALUES('ABC124','Res-I1','Optiplex750',

'2.3.4.5','AB:BC:CD:DE:20','False', 3);


136/217


136

INSERTINTO ResSystem VALUES('DEF456','Res-I2','Optiplex007',

'4.5.6.7','BB:BB:BB:BB:BB','False', 4);

INSERTINTO ResSystem VALUES('FED636','Res-B1','Optiplex876',

'4.5.6.2','HH:XX:SS:E1:EE','True',NULL);

INSERTINTO ResSystem VALUES('ZZZ123','Res-F1','Macbook','4.3.2.1','GG:HH:BB:II:YY','False', 6);

INSERTINTO Vendor VALUES('Dell','Dell Inc, CA', 26378267,


INSERTINTO Vendor VALUES('Microsoft','Microsoft Inc, SA', 672346726,


INSERTINTO Vendor VALUES('Apple','Apple Inc, CA', 2732,


INSERTINTO Vendor VALUES('McAfee','McAfee Inc', 234324,


INSERTINTO Vendor VALUES('OSU','OSU Inc OK', 767342,'[email protected]');

INSERTINTO Vendor VALUES('HP','HP Inc, CA', 2345682920,


INSERTINTO Vendor VALUES('Xerox','Xerox Inc, NY', 2378492,


INSERTINTO Vendor VALUES('StarSoft','StarSoft Inc, NJ', 38798290,


INSERTINTO HWComponent VALUES('101010', 7,'Xerox Printer','Xerox

Printer 2005 Model','True','3/20/2008 12:00:00 AM','True');

INSERTINTO HWComponent VALUES('11111', 7,'Xerox Multi purpose

printer','Xerox Multi purpose printer with Scanner & copier','True',

'12/12/2010 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('121212', 7,'Xerox Color Printer',

'Xerox Color Printer 2007 Model','True','12/22/2012 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('1234', 1,'HDD','HDD 160 GB',

'False','9/9/2009 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('123423', 7,'Xerox Printer series 5',

'Xerox color printer series 5','True','12/12/2009 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('12345', 6,'HP Laserjet 4100','HP

Laserjet 4100 2005 Model','True','6/25/2009 12:00:00 AM','True');


137/217


137

INSERTINTO HWComponent VALUES('2345', 2,'Monitor','Monitor LCD

17"','False','12/12/2009 12:00:00 AM','False');


Laserjet 1200 2000 Model','True','10/23/2010 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('2346', 2,'Webcam','Webcam 2.0 MP','False','12/12/2009 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('3333', 6,'HP Inkjet Printer','HP

Inkjet Printer 2006 model','True','12/22/2010 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('363738', 2,'Keyboard','Multimedia

Keyboard','False','12/12/2009 12:00:00 AM','False');


Laserjet 2200 PCL 5 Printer','True','12/12/2010 12:00:00 AM','False');

INSERTINTO HWComponent VALUES('4374637', 3,'RAM','RAM 256MB',

'False','12/12/2009 12:00:00 AM','True');

INSERTINTO HWComponent VALUES('62532', 3,'Monitor','CRT 15"',

'False','12/12/2008 12:00:00 AM','True');

INSERTINTO HWComponent VALUES('728382', 3,'CPU','CPU 3 GHZ',

'False','12/12/2009 12:00:00 AM','False');

INSERTINTO Printer VALUES('101010', 7,'7.8.9.10','B2:C2:D3:D4:AA',

'IBA');

INSERTINTO Printer VALUES('11111', 7,NULL,'A2:B2:C3:D4:F5','Foxrun');

INSERTINTO Printer VALUES('121212', 7,'4.5.6.70','A1:B1:C1:D1:E1',

'Bennett');

INSERTINTO Printer VALUES('12345', 6,'6.7.8.90','A1:BB:C2:D3:E3',

'Wentz');

INSERTINTO Printer VALUES('2345', 6,'2.3.4.50','AA:BB:CC:DD:EE',

'IBA');

INSERTINTO Printer VALUES('3333', 6,'3.4.5.60','ZZ:12:S3:43:DD',

'IBA');

INSERTINTO Printer VALUES('37467936', 1,'1.2.3.40',

'AB:BC:CD:EF:GH','Wentz');

INSERTINTO HWComponentSystem VALUES('11111', 7,'DEF456');


138/217


138

INSERTINTO HWComponentSystem VALUES('37467936', 1,'ABC123');




INSERTINTO HWComponentSystem VALUES('2345', 6,'AAA123');



INSERTINTO HWComponentSystem VALUES('121212', 7,'ZZZ123');

INSERTINTO HWComponentSystem VALUES('121212', 7,'AAA123');

INSERTINTO Software VALUES('10', 4,'McAfee Anti Virus','McAfeeVirus Scan Enterprise','12/12/2012 12:00:00 AM','False','False',

'AAA123');

INSERTINTO Software VALUES('100', 8,'StarRez','StarRez Residence

Management','12/12/2009 12:00:00 AM','True','False','DEF456');

INSERTINTO Software VALUES('20', 8,'StarRez','StarRez Residential

Management Software','12/12/2010 12:00:00 AM','True','False','AAA123');

INSERTINTO Software VALUES('30', 8,'StarRez','StarRez Residential

Software Application','12/12/2010 12:00:00 AM','True','False','ABC123');

INSERTINTO Software VALUES('40', 2,'Windows XP','Windows XP

Operating System','10/30/2012 12:00:00 AM','False','True','AAA123');


Operating System','10/30/2012 12:00:00 AM','False','True','ABC123');

INSERTINTO Software VALUES('60', 5,'Judicial Officer','Judicial

Officer Student Conduct Management','12/12/2010 12:00:00 AM','True',

'False','AAA123');

INSERTINTO Software VALUES('70', 5,'Judicial Officer','Judicial

Officer Student Conduct Management','12/12/2010 12:00:00 AM','True',

'False','DEF456');


operating System','10/22/2010 12:00:00 AM','False','True','ABC124');

INSERTINTO Software VALUES('90', 4,'McAfee Anti Virus','McAfee

Virus Scan Enterprise','2/12/2009 12:00:00 AM','False','False','ZZZ123');


139/217


139

INSERTINTO Issue VALUES(3, 1,NULL,'7/1/2009 12:00:00 AM','7/1/2009

12:00:00 AM', 1,'True','Network','Closed','Share access problem',NULL);

INSERTINTO Issue VALUES(4, 2,NULL,'7/4/2009 12:00:00 AM',NULL, 2,

'True','Network','WaitUser','Unable to login to application.',

'7/5/2009');

INSERTINTO Issue VALUES(5, 7, 1,'6/30/2009 12:00:00 AM',NULL, 2,

'True','Hardware','WaitVendor','Monitor Corrupted',NULL);


'True','Hardware','WaitVendor','Printer Not working',NULL);


'True','Software','Open','StarRez Connection issue',NULL);


'True','Network','Resolved','Share access issue because of IP Subnetting',

NULL);


'True','Hardware','Resolved','Printer not working due to IPSubnettting',

NULL);


12:00:00 AM', 3,'True','Hardware','Closed','Computer Slow',NULL);


12:00:00 AM', 3,'True','Hardware','Closed','Keyboard not working',NULL);


'True','Software','Resolved','Judicial Officer External Lookup problem',NULL);

INSERTINTO Issue VALUES(3, 7,NULL,'6/29/2009 12:00:00 AM',

'6/30/2009 12:00:00 AM', 1,'True','Software','Closed','Windows XP

repair',NULL);


'True','Software','WaitVendor','McAfee Anti Virus Liscence expired',

NULL);

INSERTINTO Issue VALUES(2, 1,NULL,'6/24/2009 12:00:00 AM',

'6/25/2009 12:00:00 AM', 2,'True','Software','Closed','StarRez access

issue',NULL)


'True','Hardware','WaitVendor','Printer Replacement',NULL)

INSERTINTO SystemIssue VALUES(1,'ABC124');


140/217


140

INSERTINTO SystemIssue VALUES(7,'DEF456');

INSERTINTO SystemIssue VALUES(6,'ABC124');

INSERTINTO SystemIssue VALUES(4,'ZZZ123');

INSERTINTO SystemIssue VALUES(2,'DEF456');

INSERTINTO HWComponentIssue VALUES('123423', 7, 14);






INSERTINTO SWIssue VALUES('100', 8, 5);





INSERTINTO Knowledgebase VALUES('Network Access Issue', 2,'True',

NULL,NULL,'Was unable to access the network share','Add the user to the

Reslife Active Directory','7/2/2009 12:00:00 AM');

INSERTINTO Knowledgebase VALUES('Share Access Issue', 1,'True',

NULL,NULL,'Share access issue because of IP Subnetting','Identify changed

IP and change IP information in related places','7/2/2009 12:00:00 AM');

INSERTINTO Knowledgebase VALUES('Printer Issue', 7,'True',

'Printer',NULL,'Printer not working due to IPSubnettting','Determine the

new IP from the Central IP and change the port details in the printer

settings for the system','7/3/2009 12:00:00 AM');

INSERTINTO Knowledgebase VALUES('Computer Slow', 2,'True','256MB SD

RAM',NULL,'Slow Computer processing','Clean the dust, check RAM and

replace if less than 512MB','7/4/2009 12:00:00 AM');


141/217


141

INSERTINTO Knowledgebase VALUES('Keyboard Issue', 1,'True',

'Keyboard',NULL,'Keyboard not working','Check connecting and restaring. If

still not working, then the keyboard is corrupted. Replace keyboard.',

'7/4/2009 12:00:00 AM');

INSERTINTO Knowledgebase VALUES('Judicial Officer Issue', 7,'True',

NULL,'Judicial Officer','Judicial Officer External Lookup problem','Checkfor change of IP and change the information','7/3/2009 12:00:00 AM');

INSERTINTO Knowledgebase VALUES('Windows Issue', 2,'True',NULL,

'Windows XP','Windows XP repair Reinstall','Windows XP and partition and

fragment again','6/30/2009 12:00:00 AM');

INSERTINTO Knowledgebase VALUES('StarRez Issue', 2,'True',NULL,

'StarRez','StarRez access issue','Rerun SnRegDLL from the user machine',

'6/25/2009 12:00:00 AM');

INSERTINTO KBIssue VALUES(1, 1);








INSERTINTO ResOrder VALUES('False','InTransit','Dell1','7/10/2009

12:00:00 AM', 7, 1, 3,'Order placed for New Monitor');

INSERTINTO ResOrder VALUES('False','Processed','HP1','7/20/2009

12:00:00 AM', 1, 6, 4,'Order processed by Printer');

INSERTINTO ResOrder VALUES('False','Shipped','McAfee1','7/10/2009

12:00:00 AM', 7, 4, 12,'Order Completed for McAfee Virus SCan licence');

INSERTINTO ResOrder VALUES('False','Shipped','Dell2','7/12/2009

12:00:00 AM', 2, 1,NULL,'Order shipped for new Dell machines');

INSERTINTO ResOrder VALUES('False','Delivered','Xerox1','7/22/2009

12:00:00 AM', 2, 7,NULL,'Order delivered for new Xerox color printers');

INSERTINTO ResOrder VALUES('True','InTransit','XeroxR1','7/20/2009

12:00:00 AM', 1, 7, 14,'Order for replacement of xerox printer');


142/217


142


RETURN


GO

/****** Object: StoredProcedure [dbo].[Create_DB] Script Date: 07/19/2009

20:37:44 ******/

SETANSI_NULLSON

GO


GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Create_DB]

AS

EXEC Delete_DB;

EXEC Create_Table;

EXEC Insert_Data;


RETURN


GO

/****** Object: StoredProcedure [dbo].[Delete_BackupDB] Script Date:

07/19/2009 20:38:45 ******/


143/217


143

SETANSI_NULLSON

GO


GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Delete_BackupDB]

AS

DELETEFROM SystemIssue_bkp;

DROPTABLE SystemIssue_bkp;

DELETEFROM HWComponentIssue_bkp;

DROPTABLE HWComponentIssue_bkp;

DELETEFROM SWIssue_bkp;

DROPTABLE SWIssue_bkp;

DELETEFROM KBIssue_bkp;

DROPTABLE KBIssue_bkp;

DELETEFROM Knowledgebase_bkp;

DROPTABLE Knowledgebase_bkp;

DELETEFROM ResSystem_bkp;


144/217


145/217


145


RETURN


GO

/****** Object: StoredProcedure [dbo].[Backup_DB] Script Date: 07/19/2009

20:38:59 ******/

SETANSI_NULLSON

GO


GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Backup_DB]

AS

BEGIN

SETNOCOUNTON;

EXEC Delete_BackupDB;

select *into Specialist_bkp from specialist;

select *into ResUser_bkp from ResUser;

select *into ResSystem_bkp from ResSystem;

select *into Vendor_bkp from Vendor;

select *into HWComponent_bkp from HWComponent;


146/217


146

select *into Printer_bkp from Printer;

select *into HWComponentSystem_bkp from HWComponentSystem;

select *into Software_bkp from Software;

select *into Issue_bkp from Issue;

select *into SystemIssue_bkp from SystemIssue;

select *into HWComponentIssue_bkp from HWComponentIssue;

select *into SWIssue_bkp from SWIssue;

select *into Knowledgebase_bkp from Knowledgebase;

select *into KbIssue_bkp from KbIssue;

select *into ResOrder_bkp from ResOrder;

END


GO

/****** Object: StoredProcedure [dbo].[Restore_DB] Script Date:

07/19/2009 20:39:35 ******/

SETANSI_NULLSON

GO


GO

-- =============================================

-- Author:

-- Create date:

-- Description:

-- =============================================

ALTERPROCEDURE [dbo].[Restore_DB]

AS

BEGIN


147/217


147

SETNOCOUNTON;

EXEC Delete_DB;

EXEC Create_Table;

INSERTinto specialist SELECT specialistName, specialistDesignation,

specialistContactNo, specialistEmail from Specialist_bkp;

INSERTinto ResUser SELECT userFirstName, userLastName, userEmail,

userContactNo, userLocation from ResUser_bkp;

INSERTinto ResSystem SELECT*from ResSystem_bkp;

INSERTinto Vendor SELECT vendorName, vendorAddress, vendorContactNo,

vendorEmail from Vendor_bkp;

INSERTinto HWComponent SELECT*from HWComponent_bkp;

INSERTinto Printer SELECT*from Printer_bkp;

INSERTinto HWComponentSystem SELECT*from HWComponentSystem_bkp;

INSERTinto Software SELECT*from Software_bkp;

INSERTinto Issue SELECT userId, specialistId, orderId, issueReportDate,

issueCloseDate, issuePriority, issueSource, issueType, issueStatus,

issueComments, issueUserTimePreference from Issue_bkp;

INSERTinto SystemIssue SELECT*from SystemIssue_bkp;

INSERTinto HWComponentIssue SELECT*from HWComponentIssue_bkp;

INSERTinto SWIssue SELECT*from SWIssue_bkp;

INSERTinto Knowledgebase SELECT kbTitle, kbAuthor, kbVerified, kbComponent,

kbSw, kbDesc, kbFix, kbDate from Knowledgebase_bkp;

INSERTinto KbIssue SELECT*from KbIssue_bkp;

INSERTinto ResOrder SELECT orderReplacement, orderStatus,

orderVendorOrderNo, orderExpectedDate, specialistId, vendorId, issueId,

orderComments from ResOrder_bkp;

END


148/217


148

Milestone 5

Logical Database Design

Normalized Tables created using Logical Design

All the given tables are in Boyce-Codd Normal Form. A relation is in BCNF, if and only if,

every determinant is a candidate key.

Specialist (specialistId, specialistName, specialistDesignation, specialistContactNo,

specialistEmail)

Primary Key: specialistId

Foreign Key: No foreign Key

Explanation: The listedSpecialisttable is in BCNF. From the above table we have only one

candidate key specialistId which determines the other attributes in the table. Hence the above

mentioned table is in BCNF.

ResUser (userId, userFirstName, userLastName, userEmail, userContactNo, userLocation)

Primary Key: userId


The listedResUsertable is in BCNF. From the above table we have only one candidate key

userId which determines the other attributes in the table. Hence the above mentioned table is in

BCNF.

Vendor (vendorId, vendorName, vendorAddress, vendorContactNo, vendorEmail)

Primary Key: vendorId


The listedVendortable is in BCNF. From the above table we have only one candidate key

vendorId which determines the other attributes in the table. Hence the above mentioned table is

in BCNF.


149/217


149

ResSystem (systemServiceTag, systemName, systemModel, userId, systemIP, systemMAC,

systemSalvaged)

Primary Key: systemServiceTag

Foreign Key: userId REFERENCES ResUser (userId)

The listedResSystem table is in BCNF. From the above table we have only one candidate key

systemServiceTag which determines the other attributes in the table. Hence the above mentioned

table is in BCNF.

HWComponent (compSerial, vendorId, compName, compDescription, compPrinter,

compWarrantyEndDate, compSalvaged)

Primary Key: compSerial, vendorId

Foreign Key: vendorId REFERENCES Vendor (vendorId)

The listedHWComponenttable is in BCNF. From the above table we have a composite

candidate key compSerial, vendorId which determines the other attributes in the table. Hence

the above mentioned table is in BCNF.

Printer (compSerial, vendorId, compIPAddress, compMACAddress, compLocation)

Primary Key: compSerial, vendorId

Foreign Key: compSerial, vendorId REFERENCES HWComponent (compSerial, vendorId)

The listedPrintertable is in BCNF. From the above table we have a composite candidate key

compSerial, vendorId which determines the other attributes in the table. Hence the above


HWComponentSystem (compSerial, vendorId, systemServiceTag)

Primary Key: compSerial, vendorId, systemServiceTag


Foreign Key: systemServiceTag REFERENCES ResSystem (systemServiceTag)


150/217


150

The listedHWComponentSystem table is in BCNF. From the above table we have a composite

candidate key compSerial, vendorId, systemServiceTag which uniquely determines each tuple

in the table. Hence the above mentioned table is in BCNF.

Software (swLicenseNo, vendorId, swName, swDescription, swLicenseExpiryDate, swOS,

swKA,systemServiceTag)

Primary Key: swLicenseNo, vendorId



The listedSoftware table is in BCNF. From the above table we have a composite candidate key

swLicenseNo, vendorId which determines the other attributes in the table. Hence the above


Issue (issueId, userId,specialistId, orderId, issueReportDate, issueCloseDate, issuePriority,

issueSource, issueType, issueStatus, issueComments, issueUserTimePreference)

Primary Key: issueId

Foreign Key: userId REFERENCES ResUser (userId)

Foreign Key: specialistId REFERENCES Specialist (specialistId)

Foreign Key: orderId REFERENCES ResOrder (orderId)

The listedIssue table is in BCNF. From the above table we have only one candidate key issueId

which determines the other attributes in the table. Hence the above mentioned table is in BCNF

SystemIssue (issueId, systemServiceTag)

Primary Key: issueId, systemServiceTag

Foreign Key: issueIdREFERENCES Issue (issueId)


The listedSystemIssue table is in BCNF. From the above table we have we have a composite

candidate key issueId, systemServiceTag which uniquely determines each tuple in the table.

Hence the above mentioned table is in BCNF


151/217


151

HWCompIssue (compSerial, vendorId, issueId)

Primary Key: compSerial, vendorId, issueId


Foreign Key: issueId REFERENCES Issue (issueId)

The listedHWCompIssue table is in BCNF. From the above table we have a composite

candidate key compSerial, vendorId, issueId which uniquely determines each tuple in the

table. Hence the above mentioned table is in BCNF.

SWIssue (swLicenseNo, vendorId, issueId)

Primary Key: swLicenseNo, vendorId, issueId

Foreign Key: swLicenseNo, vendorId REFERENCES Software (swLicenseNo, vendorId)


The listedSWIssue table is in BCNF. From the above table we have a composite candidate key

swLicenseNo, vendorId, issueId which uniquely determines each tuple in the table. Hence the

above mentioned table is in BCNF.

Knowledgebase (kbId, kbTitle,kbA

uthor, kbVerified, kbComponent, kbSw, kbDesc, kbFix,kbDate, kbUsageCount)

Primary Key: kbId

Foreign Key: kbAuthor REFERENCES Specialist (specialistId)

The listedKnowledgebase table is in BCNF. From the above table we have only one candidate

key kbId which determines the other attributes in the table. Hence the above mentioned table is

in BCNF

KBIssue (kbId, issueId)

Primary Key: kbId, issueId

Foreign Key: kbId REFERENCES Knowledgebase (kbId)



152/217


152

The listedKBIssue table is in BCNF. From the above table we have a composite candidate key

kbId, issueId which uniquely determines each tuple in the table. Hence the above mentioned

table is in BCNF.

ResOrder (orderId, orderReplacement, orderStatus, orderVendorOrderNo, orderExpectedDate,

specialistId, vendorId, issueId, orderComments)

Primary Key: orderId

Foreign Key: specialistId REFERENCES Specialist (specialistId)



The listed ResOrder table is in BCNF. From the above table we have only one candidate keyorderId which determines the other attributes in the table. Hence the above mentioned table is in

BCNF.

Tables for Queries:

The tables from SQL server are listed below in order to show the execution of the queries.

Specialist


153/217


153

ResUser

Vendor

ResSystem


154/217


154

HWComponent

Printer

HWComponentSystem


155/217


155

Software

Issue

SystemIssue


156/217


157/217


157

KBIssue

ResOrder

Transaction Queries

Specialist

1. List the Names and the designation of the Specialists.select specialistName, specialistDesignationfrom Specialist;

Output:


158/217


158

2. How many issues did the each specialist fix in July 09?select specialistName,count(issueId)as TotalIssuesClosedfrom Specialist, IssuewhereSpecialist.specialistId = Issue.specialistId

andissueCloseDate between'07/01/2009'and'07/31/2009'groupby specialistName;

Output:

3. List the issues resolved by a specialistselect issueId as IssuesResolvedfrom IssuewhereIssue.specialistId in

(select specialistIdfrom Specialistwhere specialistName ='Brad')

andissueStatus ='Resolved';

Output:

4. What is the count of issues under each category that is closed by the specialist?select issueType,count(issueId)as IssuesClosedfrom IssuewhereIssue.specialistId in

(select specialistIdfrom Specialistwhere specialistName ='Shree')

andissueStatus ='Closed'


159/217


159

groupby issueType;

Output:

5. List the solutions to the issues posted by a particular specialist in the knowledgebaseselect kbId, kbDesc, kbFixfrom Knowledgebasewhere Knowledgebase.kbAuthor in

(select specialistIdfrom Specialistwhere specialistName ='Amar')

;

Output:

6. List the specialist details who resolved a particular issueselect*from Specialistwhere specialistId in

(select specialistIdfrom Issuewhere issueId = "1")

;

Output:


160/217


160

ResUser

7. List all the user details sorting and displaying in ascending order of the user id.select*

from ResUserorderby userId;

Output:

8. List the System information associated with a particular user idselect ResUser.userId, ResUser.userFirstName, ResUser.userLastName,ResSystem.systemServiceTag, ResSystem.systemName,ResSystem.systemModel, ResSystem.systemIP,ResSystem.systemMAC

from ResUser, ResSystemwhereResUser.userId = ResSystem.userIdandResSystem.userId ='4';

Output:

9. List the printer information associated with a particular user.select*from Printer,

(select HWComponent.compSerial, HWComponent.vendorIdfrom HWComponent,


161/217


161

(select compSerial, vendorIdfrom HWComponentSystemwhere HWComponentSystem.systemServiceTag in

(select systemServiceTagfrom ResSystemwhere ResSystem.userId in

(select userIdfrom ResUserwhere userFirstName ='Brad'and userLastName =

'Baustert'))

) Temp1whereHWComponent.compSerial = Temp1.compSerialandHWComponent.vendorId = Temp1.vendorIdandHWComponent.compPrinter ='True') Temp2

where

Printer.compSerial = Temp2.compSerialandPrinter.vendorId = Temp2.vendorId;

Output:

10.List all the user details with their system information displaying in ascending order of theuser idselect ResUser.userId, ResUser.userFirstName, ResUser.userLastName,ResSystem.systemServiceTag, ResSystem.systemName,ResSystem.systemModel, ResSystem.systemIP,ResSystem.systemMACfrom ResUser, ResSystemwhereResUser.userId = ResSystem.userIdorderby userId Asc;

Output:


162/217


162

11.List the various issues resolved for the particular userselect issueId as IssuesResolvedfrom Issuewhere Issue.userId in

(select userIdfrom ResUserwhere userFirstName ='Brad'and userLastName ='Baustert')

and(issueStatus ='Resolved'orissueStatus ='Closed')

;

Output:

12.What is the status of a particular users issue reported between selected dates?select issueId as IssuesReported, issueStatusfrom Issuewhere Issue.userId in

(select userIdfrom ResUserwhere userFirstName ='Brad'and userLastName ='Baustert')

and

(issueReportDate between'01-01-2009'and'12-31-2009');

Output:

Vendor:

13.List all the vendor details.select*from Vendor;


163/217


163

Output:

14.List the pending orders with a particular vendor along with their expected dates andstatus.

select orderId, orderStatus, orderExpectedDatefrom ResOrderwhere ResOrder.vendorId in

(Select vendorIdfrom Vendorwhere vendorName ='Dell')

and orderStatus !='Delivered';

Output:

ResSystem:

15.List all the software information of a particular user.select swName, swLicenseNo, swLicenseExpiryDatefrom Software,(select systemServiceTag

from ResSystemwhere ResSystem.userId in

(select userIdfrom ResUserwhere userFirstName ='Brad'and userLastName =

'Baustert'))as Tempwhere Software.systemServiceTag = Temp.systemServiceTag;


164/217


164

Output:

16.List all the hardware information of a particular user.select HWComponent.compSerial, HWComponent.compName,HWComponent.compDescription

from HWComponent,(select compSerial, vendorId

from HWComponentSystemwhere HWComponentSystem.systemServiceTag in

(select systemServiceTagfrom ResSystemwhere ResSystem.userId in

(select userIdfrom ResUserwhere userFirstName ='Shree'and userLastName

='Shree'))

) Temp1whereHWComponent.compSerial = Temp1.compSerialandHWComponent.vendorId = Temp1.vendorId

;

Ou

OSU Systems Support

Documents

Transcript of OSU Systems Support