Report on Interior Design Company Database Development

Published:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

You have been sub-contracted to design the database system for Marlowe Interiors. Marlowe Interiors is a medium sized interior design company that does building work and decorating. An initial analysis of Marlowe Interiors has identified the following requirements.

Marlowe Interiors keeps a record of the jobs it performs. Jobs are for particular customers and classified by job type (Single Room, Part-house, Whole-house). The full cost of a job depends on the labour used and the parts used. Records of parts and labour should be kept separately.

Labour costs depend on the type of work done. A job may have different sorts of work and employ one or more types of worker (plumber, labourer, qualified builder, interior designer, electrician). A worker will work on more than one job. The hourly rate of pay for each of these type of worker will vary as shown below:

Type

Rate per Hour

Plumber

£50

Labourer

£20

Qualified Builder

£55

Interior Desigher

£39

Electrician

£50

A job may involve one or more parts. Examples of parts are: sink, bath, pipe, thermostat, wallpaper, decking, door, light-fitting. The costs of these parts will vary and suitable test values should be supplied as part of the initial implementation.

Parts are supplied by various suppliers. The cost of a part could vary depending on the supplier.

A customer record should be kept for the job with all the usual detail such as name, address and phone-number.

Task 1

Draw an Entity Relationship Data model that describe the content and structure of the data held by Marlowe Interiors.

Entity Relationship Diagram

Figure(1.1) Entity Relationship Diagram for Interior Design Company

Representing Entities

Entity: Customer

Description: Any person who add a job at Marlowe Interiors

Identifying Attribute(s): CID

Other Attributes: CName, Address, Phno

Entity: JobType

Description: Type of Job which are classified for the customer

Identifying Attribute(s): JTypeID

Other Attributes: JType

Entity: Labours

Description: Any persons who work at the Marlowe Interiors

Identifying Attribute(s): LID

Other Attributes: LName

Entity: LabourType

Description: Type of Labours which are classified in the Marlowe Interiors

Identifying Attribute(s): LTypeID

Other Attributes: LType, RatePerHour

Entity: Parts

Description: Type of parts may be involved in a job.

Identifying Attribute(s): PID

Other Attributes: PType, ImpCost

Entity: Supplier

Description: Any person who supply various parts

Identifying Attribute(s): SID

Other Attributes: SName, Address, Phno

Entity: Job

Description: Record that perform by the Marlowe Interiors

Identifying Attribute(s): JID, CID

Other Attributes: JTypeID, Date, WorkHour

Entity: JobCost

Description: Parts which are use in a job

Identifying Attribute(s): PID, JID

Other Attributes:

Entity: PartCost

Description: Price of parts buy from the various suppliers

Identifying Attribute(s): PID, SID

Other Attributes: Price

Entity: Post

Description: Post of labours

Identifying Attribute(s): LID, LTypeID

Other Attributes:

Entity: Working

Description: Labours who work on a job

Identifying Attribute(s): LID, JID

Representing Relationships

Relationship ID: R1

Relationship Name(s): addJob, workOfJob

Description: Associates customers with the job they are currently add job

Participating Entity: Customer

Cardinality: one

Optionality: mandatory

Participating Entity: Job

Cardinality: many

Optionality: mandatory

Relationship ID: R2

Relationship Name(s): isWorking, Working

Description: Associate job who is working on

Participating Entity: Job

Cardinality: one

Optionality: mandatory

Participating Entity: Working

Cardinality: many

Optionality: mandatory

Relationship ID: R3

Relationship Name(s): Working, WorkingFor

Description: Associates labours who was working on a job

Participating Entity: Working

Cardinality: many

Optionality: mandatory

Participating Entity: Labours

Cardinality: one

Optionality: mandatory

Relationship ID: R4

Relationship Name(s): occupy, isOccupy

Description: Associate labours with their post

Participating Entity: Labours

Cardinality: one

Optionality: mandatory

Participating Entity: Post

Cardinality: many

Optionality: mandatory

Relationship ID: R5

Relationship Name(s): typeOfLabour, nameOfLabour

Description: Associate post with the labour type

Participating Entity: Post

Cardinality: many

Optionality: mandatory

Participating Entity: LabourType

Cardinality: one

Optionality: mandatory

Relationship ID: R6

Relationship Name(s): typeOfJobWorking, workingJobType

Description: Associate job type with the job

Participating Entity: JobType

Cardinality: one

Optionality: mandatory

Participating Entity: Job

Cardinality: many

Optionality: mandatory

Relationship ID: R7

Relationship Name(s): costOfPartUse, usePart

Description: Associate Job with JobCost for part

Participating Entity: Job

Cardinality: one

Optionality: mandatory

Participating Entity: JobCost

Cardinality: many

Optionality: mandatory

Relationship ID: R8

Relationship Name(s): partType, usePartinJob

Description: Associate JobCost with Parts use in job

Participating Entity: JobCost

Cardinality: many

Optionality: mandatory

Participating Entity: Part

Cardinality: one

Optionality: mandatory

Relationship ID: R9

Relationship Name(s): partCost, partType

Description: Associate part with partcost buy from various suppliers

Participating Entity: Parts

Cardinality: one

Optionality: mandatory

Participating Entity: PartCost

Cardinality: many

Optionality: mandatory

Relationship ID: R10

Relationship Name(s): suppliey, supplyBy

Description: Associate PartCost with suppliers by buying parts

Participating Entity: PartCost

Cardinality: many

Optionality: mandatory

Participating Entity: Supplier

Cardinality: one

Optionality: mandatory

Representing Attributes

Attribute: CID

Description: ID of customer add job

Type: integer {1, 2, 3, 4, 5}

Attribute: CName

Description: Name of customer add job

Type: character {Daw Hla, U Maung Maung, U Ba Taung, Daw Taung Mya, U Thein Myint

Attribute: Address

Description: Address of customer add job

Type: character {Mandalay, Taunggyi, Monywa, Yangon, Mandalay

Attribute: Phno.

Description: Contact phone number of customer

Type: character {0265123, 095215657, 092156784, 01706218, 092050199}

Attribute: JID

Description: ID of job work for customer

Type: integer {1, 2, 3, 4, 5}

Attribute: Date

Description: Start date of job

Type: date {2011-01-01, 2011-01-08, 2011-01-11, 2011-01-11, 2011-01-13}

Attribute: WorkHour

Description: Total hour of work for a job

Type: integer {75, 50, 90, 30, 48}

Attribute: JTypeID

Description: ID of job type

Type: integer {1, 2, 3}

Attribute: JType

Description: Type of job divide in job

Type: character {Single Room, Part-house, Whole-house}

Attribute: LID

Description: ID of each labour work in job

Type: integer {1, 2, 3, 4, 5}

Attribute: LName

Description: Name of labours work in job

Type: character {U Kyaw Saw, U Ba Maung, U Hla Nyein, U Chit Kaung, U Kyaw Soe}

Attribute: LTypeID

Description: ID of worker type divide in job

Type: integer {1, 2, 3, 4, 5}

Attribute: LType

Description: Type of worker divides in the job

Type: character {Plumber, Labourer, Qualified Builder, Interior Designer, Electrician}

Attribute: RatePerHour

Description: money have given to worker for an hour

Type: integer {50, 20, 55, 39, 50}

Attribute: Price

Description: Price of part buys from various suppliers

Type: integer {32, 25, 30, 35, 20, 10,12, 15, 15, 25, 20}

Attribute: PID

Description: ID of parts use in the job

Type: integer {1, 2, 3, 4, 5, 6, 7, 8}

Attribute: PType

Description: Type of parts available in the job

Type: character {Sink, Bath, Pipe, Thermostat, Wallpaper, Decking, Door, Light-fitting}

Attribute: ImpCost

Description: Implementation cost for each part

Type: integer {5,10, 10, 10, 5, 7, 5, 10}

Attribute: SID

Description: ID of supplier who supplied parts

Type: integer {1, 2, 3, 4, 5}

Attribute: SName

Description: Name of supplier who supplied parts

Type: character {U Thet Lwin, Daw Nilar, Daw Shwe Ye, U Aung Min Thant, U Chit Maung}

Attribute: Address

Description: Address of supplier

Type: character {Taunggyi, Mandalay, Yangon, Mandalay, Mandalay}

Attribute: Phno.

Description: Contact phone number of Suppliers

Type: character {08120103, 0272654, 09531246, 0275323, 092003916}

Task 2

Produce the resulting tables clearly indicating the primary and foreign keys.

Customer

Field Name

Data Type

Key

CID

Integer

Primary Key

CName

Varchar(30)

-

Address

Varchar(45)

-

Phno.

Varchar(20)

-

Job

Field Name

Data Type

Key

JID

Integer

Primary Key

CID

Integer

Foreign Key

JTypeID

Integer

Foreign Key

Date

Date

-

WorkHour

Integer

-

JobCost

Field Name

Data Type

Key

PID

Integer

Primary Key

JID

Integer

Primary Key

JobType

Field Name

Data Type

Key

JTypeID

Integer

Primary Key

JType

Varchar(45)

-

Labours

Field Name

Data Type

Key

LID

Integer

Primary Key

LName

Varchar(30)

-

LabourType

Field Name

Data Type

Key

LTypeID

Integer

Primary Key

LType

Varchar(45)

-

RatePerHour

Integer

-

PartCost

Field Name

Data Type

Key

PID

Integer

Primary Key

SID

Integer

Primary Key

Price

Integer

-

Parts

Field Name

Data Type

Key

PID

Integer

Primary Key

PType

Varchar(45)

-

ImpCost

Integer

-

Post

Field Name

Data Type

Key

LID

Integer

Primary Key

LTypeID

Integer

Primary Key

Supplier

Field Name

Data Type

Key

SID

Integer

Primary Key

SName

Varchar(30)

-

Address

Varchar(45)

-

Phno

Varchar(20)

-

Working

Field Name

Data Type

Key

LID

Integer

Primary Key

JID

Integer

Primary Key

Task 3

Using a Database Management System (DBMS) of your choice, set-up all of the above normalized tables, and populate them with well-designed test data (minimum 5 records per table). Provide printouts of all tables.

CREATE SCHEMA IF NOT EXISTS `InteriorDesignCompany` ;

USE `InteriorDesignCompany` ;

Customer

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Customer` (

`CID` INT NOT NULL ,

`CName` VARCHAR(30) NULL ,

`Address` VARCHAR(45) NULL ,

`Phno.` VARCHAR(20) NULL ,

PRIMARY KEY (`CID`) )

JobType

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`JobType` (

`JTypeID` INT NOT NULL ,

`JType` VARCHAR(45) NULL ,

PRIMARY KEY (`JTypeID`) )

Labours

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Labours` (

`LID` INT NOT NULL ,

`LName` VARCHAR(30) NULL ,

PRIMARY KEY (`LID`) )

LabourType

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`LabourType` (

`LTypeID` INT NOT NULL ,

`LType` VARCHAR(45) NULL ,

`RatePerHour` INT NULL ,

PRIMARY KEY (`LTypeID`) )

Parts

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Parts` (

`PID` INT NOT NULL ,

`PType` VARCHAR(45) NULL ,

`ImpCost` VARCHAR(45) NULL ,

PRIMARY KEY (`PID`) )

Supplier

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Supplier` (

`SID` INT NOT NULL ,

`SName` VARCHAR(30) NULL ,

`Address` VARCHAR(45) NULL ,

`Phno.` VARCHAR(20) NULL ,

PRIMARY KEY (`SID`) )

Job

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Job` (

`JID` INT NOT NULL ,

`CID` INT NULL ,

`JTypeID` INT NULL ,

`Date` DATE NULL ,

`WorkHour` DECIMAL(10) NULL ,

PRIMARY KEY (`JID`) ,

INDEX `fk_CID` (`CID` ASC) ,

INDEX `JTypeID` (`JTypeID` ASC) ,

CONSTRAINT `fk_CID`

FOREIGN KEY (`CID` )

REFERENCES `InteriorDesignCompany`.`Customer` (`CID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION,

CONSTRAINT `JTypeID`

FOREIGN KEY (`JTypeID` )

REFERENCES `InteriorDesignCompany`.`JobType` (`JTypeID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION)

JobCost

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`JobCost` (

`PID` INT NOT NULL ,

`JID` INT NOT NULL ,

PRIMARY KEY (`PID`, `JID`) ,

INDEX `fk_JobCost_Job1` (`JID` ASC) ,

CONSTRAINT `fk_JobCost_Parts1`

FOREIGN KEY (`PID` )

REFERENCES `InteriorDesignCompany`.`Parts` (`PID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION,

CONSTRAINT `fk_JobCost_Job1`

FOREIGN KEY (`JID` )

REFERENCES `InteriorDesignCompany`.`Job` (`JID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION)

PartCost

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`PartCost` (

`PID` INT NOT NULL ,

`SID` INT NOT NULL ,

`Price` INT NULL ,

PRIMARY KEY (`PID`, `SID`) ,

INDEX `fk_PartCost_Supplier1` (`SID` ASC) ,

CONSTRAINT `fk_PartCost_Parts1`

FOREIGN KEY (`PID` )

REFERENCES `InteriorDesignCompany`.`Parts` (`PID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION,

CONSTRAINT `fk_PartCost_Supplier1`

FOREIGN KEY (`SID` )

REFERENCES `InteriorDesignCompany`.`Supplier` (`SID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION)

Post

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Post` (

`LID` INT NOT NULL ,

`LTypeID` INT NOT NULL ,

PRIMARY KEY (`LID`, `LTypeID`) ,

INDEX `fk_Post_LabourType1` (`LTypeID` ASC) ,

CONSTRAINT `fk_Post_Labours1`

FOREIGN KEY (`LID` )

REFERENCES `InteriorDesignCompany`.`Labours` (`LID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION,

CONSTRAINT `fk_Post_LabourType1`

FOREIGN KEY (`LTypeID` )

REFERENCES `InteriorDesignCompany`.`LabourType` (`LTypeID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION)

Working

CREATE TABLE IF NOT EXISTS `InteriorDesignCompany`.`Working` (

`LID` INT NOT NULL ,

`JID` INT NOT NULL ,

PRIMARY KEY (`LID`, `JID`) ,

INDEX `fk_Working_Job1` (`JID` ASC) ,

CONSTRAINT `fk_Working_Labours1`

FOREIGN KEY (`LID` )

REFERENCES `InteriorDesignCompany`.`Labours` (`LID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION,

CONSTRAINT `fk_Working_Job1`

FOREIGN KEY (`JID` )

REFERENCES `InteriorDesignCompany`.`Job` (`JID` )

ON DELETE NO ACTION

ON UPDATE NO ACTION)

Task 4

Set-up and test all of the following queries using Structured Query Language (SQL). Provide printouts of SQL code for each query and the output produced when you run the query in the database you have developed:

Display the names and address of the customers of Marlowe Interiors and the Jobs and job types that have been carried out for them.

Display a full record of a job. This should include the name of the customer, the job type, the workers on the jobs and what type they are, the parts included in the job and the final overall cost for the job.

4(a)

SQL View

create view JobOfCustomer as

select c.CName, c.Address, j.JID, j.Date, j.WorkHour, t.JType From Customer c inner join Job j on c.CID = j.CID inner join JobType t on t.JTypeID = j.JTypeID

Figure(4.1) Screen Shot for the result of JobofCustomer in SQL

4(b)

Figure(4.2) Screen Shot for the result

SQL View

CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `fullcostofjob` AS select `customer`.`CName` AS `CName`,`job`.`JID` AS `JID`,`jobtype`.`JType` AS `JType`,`labours`.`LName` AS `LName`,`labourtype`.`LType` AS `LType`,`parts`.`PType` AS `PType`,`job`.`WorkHour` AS `WorkHour`,`labourtype`.`RatePerHour` AS `RatePerHour`,`partcost`.`Price` AS `Price`,`parts`.`ImpCost` AS `ImpCost`,(`parts`.`ImpCost` + `partcost`.`Price`) AS `CostOfPart`,(`job`.`WorkHour` * `labourtype`.`RatePerHour`) AS `LabourCost`,((`job`.`WorkHour` * `labourtype`.`RatePerHour`) + (`parts`.`ImpCost` + `partcost`.`Price`)) AS `TotalCost` from ((`jobtype` join ((`customer` join `job` on((`customer`.`CID` = `job`.`CID`))) join ((`parts` join `jobcost` on((`parts`.`PID` = `jobcost`.`PID`))) join `partcost` on((`parts`.`PID` = `partcost`.`PID`))) on((`job`.`JID` = `jobcost`.`JID`))) on((`jobtype`.`JTypeID` = `job`.`JTypeID`))) join (`labourtype` join ((`labours` join `working` on((`labours`.`LID` = `working`.`LID`))) join `post` on((`labours`.`LID` = `post`.`LID`))) on((`labourtype`.`LTypeID` = `post`.`LTypeID`))) on((`job`.`JID` = `working`.`JID`)));

Resulted Table

Figure(4.3) Screen Shot of the result table

Task 5

Explain any assumption you have made when analyzing, designing and implementing the above database, justify the approach you have taken and explain any alternative approaches you could have taken to any of the above tasks, Discuss any changes you would make to improve your work.

Assumptions for analyzing, designing and implementing

I think the scenario is completeness of giving information, details of required request of system and give point of the system or user requirement request. In Task-1, we make ERD and Data-Dictionary following the scenario. In Task-2, we make tables; it includes field name and data type; then expressed primary key and foreign key. In Task-3, using DBMS we make create table and insert into test data of table. In Task-4, using Structured Query Language (SQL) make question requested, it includes SQL code and output tables of print screen. In the Task-5 make assumption, analyzing, designing, implementing, alternative approaches and to improve my work. But all Tasks can be thinker widely and will be have in this system at drawing tables.

For these assignment, I also have to take four steps which are essential in database development. They are

Requirements elicitation

Conceptual modeling

Logical modelling

Physical modelling

The techniques used in the development process naturally divided into three categories: those concerned with conceptual modeling, those concerned with logical modeling and those concerned with physical modeling. The key input into he development process is a set of requirements for a database system; the key output is the final database and associated functions.

Requirement elicitation involves establishing the key technical requirements for a database system usually through formal and informal interaction between developer and organisational stakeholders such as users. In general terms it involves establishing the structure of data needed and the use of the data in some information systems context. One key aspect of requirements elicitation is the determination of the scope of the 'universe of discourse'(UOD) to be convered by a proposed database system.

Conceptual modeling involves building a model of the real world expressed in terms of the data requirements established. First we discuss the well-established technique of entity-realtionship (E-R) diagramming. This technique can be used to construct and entity model- a representation of a UOD in term of entities, relationships and attributes. An entity may be defined as a thing which and organisation recognizes as being capable of an independent existence and which can be uniquely indentified. A Relationship is some association between entities. Associations between two entities is N-ary relationship. That is, relationships between one, three, four or N entities. Relationship between entities is represented by drawing a line. An entity is characterized by a number of properties of attributes. Values assigned to attributes are used to distinguish one entity from another. We also choose one or more attributes to act as identifiers for instances of an entity. In terms of relational schema the entity identifier will eventually turn into the primary key.

According to this company database, I produce eleven entities. They are customer, job, jobType, working, labours, labourType, post, jobcost, parts, partCost, supplier. Customer and job have add work relation so relationship between them named R1. Job can have many workers and the labour cost is depended on their work done. So there have relations between job and labours and working is link file between them. The relationships between them are named R2 and R3. There are also have many type of worker. So, there have relationship between labours and lobourType. Post link for labours and labourType. Therefore, the relationship between them is R4 and R5. Job can have three type of job. So, job and job type are also have relation and their relationship is named R6. Job can be use many parts and total part cost involve their implementation cost. So, job and part have relation and jobCost is use as link file between them. The relationship between them is R7 and R8. Parts are supplied by many suppliers and their cost are depended on the various suppliers. In their relation, partCost is involved as link file. Their relationship is named R9 and R10. The attributes contain in my system are CID for ID of Customer, CName for customer name, Address and Phno. For contact detail of customer, JTypeID for ID of job type, JType for name of job type, JID for ID of job, Date for start working date, WorkHour for total time for each job, LID for ID of worker, LName for name of workers, LTypeID of ID of labour type, LType and type of labour, RatePerHour for cost for each type of labour in one hour, PID for ID of parts, PType for type of parts, ImpCost for implementation cost of parts, SID for ID of suppliers, SName for supplier's name, Address and Phno for contact detail of supplier.

Logical modeling involves constructing a model of the real world expressed in terms of the principles of some data model. Because of its popularity we focus on the relational data model in our discussing of logical modeling. Entity or an object model may be mapped to a relational schema. The logical database design technique of normalisation. This technique enables us to construct a relational schema free from update problems.

Physical modeling involves constructing a model of the real world expressed in terms of data structures and access mechanisms available in a chosen DBMS. Physical modeling involves two distinct subprocesses: physical database design and database implementation. Physical dataset design comprises the process of annotating a logical model with information pertaining to a particular application such as volume and usage information. The output from the physical dataset design process is a database implementation plans. Database implementation involves taking the output from physical database design and implementing the design decisions contained in the plan in a chosen DBMS.

Data structures declared in a suitable data definition language.

Indexes declared on the data structures.

Clustering data where appropriate.

A set of inherent integrity constraints expressed in some data definition language and a set of additional integrity constraints expressed in some data integrity language.

A distribution strategy for the database system, including a plan for distributing data.

A set of queries optimised for running on some database (Eg. Microsoft Access, MySQL etc)

The traditional requirements elicitation and specification activities of the ID development process take place within system analysis. This corresponds to the data requirements elicitation phase of the database development process plus conceptual modeling. Conceptual modeling, because of its key role in documenting data requirements at a high-level, also overlaps with the traditional idea of systems analysis. Logical modeling corresponds mostly to systems design in the sense of specifying logical schema and the incorporation of physical design decisions. Finally, physical design of database systems is one of the important process relevant to modern- day information systems implementation.

Alternative approach

There are many SQL database management systems to run the queries. Among them, the most commonly use is MySQL and Microsoft SQL. They have different advantages and disadvantages using my system. In my system, I have use MySQL because it is the most suitable for my system. There are some different advantages and disadvantages of MySQL and Microsoft SQL.

Open source vs. proprietary

When it comes to these two databases, the difference in the MySQL open-source start at home against closed, proprietary structural features of SQL Server. MySQL is a scalable, open database storage engine, offers a variety of variations, such as in Berkeley DB, InnoDB, the reactor and MyISAM. On the other hand, Microsoft's products, will be limited to the engine and SYBASE from good and bad moments.

In considering how the seamless integration of MySQL programming languages and other various web-based technology, certainly in compatibility, such as SQL Server is known to work with Microsoft's way better than other products, Microsoft SQL advantage.

Licensing

Contrary to popular belief, the system MySQL is not free. On the other hand, are always cheaper. For both products, licensing fees are based on a two-tier system. And MS SQL, the best way is to buy the Microsoft Developer development permit or license for Microsoft Visual Studio suite. SQL Server provides both growth in use of free licenses. If you want to use in a commercial environment the product, you must purchase a minimum of SQL Server Standard Edition - this time you can set a client connection couples than 1000 U.S. dollars.

Because MySQL is based on open-source GNU General Public License system, developers can use without cost, provided the project is open source. However, if you intend to sell patented products as your software, you must purchase a commercial license, which costs about $ 400 up to nine clients. On your work and the different funds, MySQL may have the advantage here.

Technical differences

Only in the battle of open source vs. proprietary main reason why some choose more than one user to another system. However, there are from a technical point of view, as well as some differences.

For example, MySQL does not provide foreign key, which means it has all the MS SQL, this is a complete relational database features full support for the relationship. Some versions of MySQL stored procedures lack sufficient support - the biggest drawback is that the system MyISAM, it does not support transactions.

Performance

Way through the performance, MySQL is the undisputed leader, mainly because of the default table, MyISAM table format. MyISAM databases leave a small footprint, uses very little disk space, memory and CPU. When the system runs on Windows platform, the implementation of the defects are often not in the Linux and UNIX as good as the other systems. Because of its stability, as Yahoo use MySQL as the backend database, a lot of power on the Internet.

When it comes to performance, strength of Microsoft SQL is packed with more features than other systems may be the biggest disadvantage. Although most of these features is designed to regulate the performance, they are often at the expense of other necessities. Here is the cost and complexity of storage and memory, resulting in poor performance off-road resources. If we lack sufficient knowledge and equipment to support a SQL Server, will work with other database management systems better.

Security

The two database systems almost deadlocked in terms of security. By default, all out appropriate security mechanisms have to obey orders and maintain current security patch. Both the known IP port operations to attract, unfortunately, the intruder's wealth can be attributed to the two products at a disadvantage. The good news is, MySQL, MS SQL allows to change the port by default, just too fragile.

Recovery

The restoration to, SQL Server had a MySQL, a clear advantage, often fall short a little bit of support for MyISAM configuration. UPS system must be MyISAM, because it requires continuous operation. If a power failure should occur, may lead to deterioration and loss of critical data. In SQL Server, data corruption is more likely. The data travel through the checkpoint in your keyboard to the hard disk and passing through the screen. In addition, SQL Server, please follow this process, even if the system shut down unexpectedly.

Although two of these have their various advantages and disadvantages, I have chosen MySQL to run my queries. I think it will be the most suitable with my system to use.

Change to improve my work

I also want to change these little things to improve my work.

Inserting other supplementary system to the exciting system to get a more complete system if possible

Creating the program design more beautiful and complete

Repair this system more effectively and efficient for users.

For the security of my system, making user name and password protection to access the database.

Writing Services

Essay Writing
Service

Find out how the very best essay writing service can help you accomplish more and achieve higher marks today.

Assignment Writing Service

From complicated assignments to tricky tasks, our experts can tackle virtually any question thrown at them.

Dissertation Writing Service

A dissertation (also known as a thesis or research project) is probably the most important piece of work for any student! From full dissertations to individual chapters, we’re on hand to support you.

Coursework Writing Service

Our expert qualified writers can help you get your coursework right first time, every time.

Dissertation Proposal Service

The first step to completing a dissertation is to create a proposal that talks about what you wish to do. Our experts can design suitable methodologies - perfect to help you get started with a dissertation.

Report Writing
Service

Reports for any audience. Perfectly structured, professionally written, and tailored to suit your exact requirements.

Essay Skeleton Answer Service

If you’re just looking for some help to get started on an essay, our outline service provides you with a perfect essay plan.

Marking & Proofreading Service

Not sure if your work is hitting the mark? Struggling to get feedback from your lecturer? Our premium marking service was created just for you - get the feedback you deserve now.

Exam Revision
Service

Exams can be one of the most stressful experiences you’ll ever have! Revision is key, and we’re here to help. With custom created revision notes and exam answers, you’ll never feel underprepared again.