We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy

See Pricing

What's Your Topic?

Hire a Professional Writer Now

The input space is limited by 250 symbols

What's Your Deadline?

Choose 3 Hours or More.
Back
2/4 steps

How Many Pages?

Back
3/4 steps

Sign Up and See Pricing

"You must agree to out terms of services and privacy policy"
Back
Get Offer

Report on Interior Design Company Database Development

Hire a Professional Writer Now

The input space is limited by 250 symbols

Deadline:2 days left
"You must agree to out terms of services and privacy policy"
Write my paper

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

Marlowe Interiors keeps a record of the occupations it performs. Jobs are for peculiar clients and classified by occupation type ( Single Room, Part-house, Whole-house ) . The full cost of a occupation depends on the labor used and the parts used. Records of parts and labor should be kept individually.

Don't use plagiarized sources. Get Your Custom Essay on
Report on Interior Design Company Database Development
Just from $13,9/Page
Get custom paper

Labor costs depend on the type of work done. A occupation may hold different kinds of work and use one or more types of worker ( plumber, labourer, qualified builder, interior interior decorator, electrician ) . A worker will work on more than one occupation. The hourly rate of wage for each of these type of worker will change as shown below:

Type

Rate per Hour

Plumber

& A ; lb ; 50

Laborer

& A ; lb ; 20

Qualified Builder

& A ; lb ; 55

Interior Desigher

& A ; lb ; 39

Electrician

& A ; lb ; 50

A occupation may affect one or more parts.

Examples of parts are: sink, bath, pipe, thermoregulator, wallpaper, adorning, door, light-fitting. The costs of these parts will change and suited trial values should be supplied as portion of the initial execution.

Partss are supplied by assorted providers. The cost of a portion could change depending on the provider.

A client record should be kept for the occupation with all the usual item such as name, reference and phone-number.

Undertaking 1

Draw an Entity Relationship Data theoretical account that describe the content and construction of the informations held by Marlowe Interiors.

Entity Relationship Diagram

Figure ( 1.1 ) Entity Relationship Diagram for Interior Design Company

Representing Entities

Entity: Customer

Description: Any individual who add a occupation at Marlowe Insides

Identifying Attribute ( s ) : Criminal investigation command

Other Properties: CName, Address, Phno

Entity: JobType

Description: Type of Job which are classified for the client

Identifying Attribute ( s ) : JTypeID

Other Properties: JType

Entity: Labors

Description: Any individuals who work at the Marlowe Insides

Identifying Attribute ( s ) : Eyelid

Other Properties: LName

Entity: LabourType

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

Identifying Attribute ( s ) : LTypeID

Other Properties: LType, RatePerHour

Entity: Partss

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

Identifying Attribute ( s ) : Pelvic inflammatory disease

Other Properties: PType, ImpCost

Entity: Supplier

Description: Any individual who supply assorted parts

Identifying Attribute ( s ) : SID

Other Properties: SName, Address, Phno

Entity: Occupation

Description: Record that perform by the Marlowe Insides

Identifying Attribute ( s ) : JID, CID

Other Properties: JTypeID, Date, WorkHour

Entity: JobCost

Description: Partss which are usage in a occupation

Identifying Attribute ( s ) : Pelvic inflammatory disease, JID

Other Properties:

Entity: PartCost

Description: Monetary value of parts buy from the assorted providers

Identifying Attribute ( s ) : Pelvic inflammatory disease, SID

Other Properties: Monetary value

Entity: Post

Description: Post of labors

Identifying Attribute ( s ) : Eyelid, LTypeID

Other Properties:

Entity: Working

Description: Labors who work on a occupation

Identifying Attribute ( s ) : Eyelid, JID

Representing Relationships

Relationship ID: R1

Relationship Name ( s ) : addJob, workOfJob

Description: Associates clients with the occupation they are presently add occupation

Participating Entity: Customer

Cardinality: 1

Optionality: mandatary

Participating Entity: Occupation

Cardinality: many

Optionality: mandatary

Relationship ID: R2

Relationship Name ( s ) : isWorking, Working

Description: Associate occupation who is working on

Participating Entity: Occupation

Cardinality: 1

Optionality: mandatary

Participating Entity: Working

Cardinality: many

Optionality: mandatary

Relationship ID: R3

Relationship Name ( s ) : Working, WorkingFor

Description: Associates labors who was working on a occupation

Participating Entity: Working

Cardinality: many

Optionality: mandatary

Participating Entity: Labors

Cardinality: 1

Optionality: mandatary

Relationship ID: R4

Relationship Name ( s ) : occupy, isOccupy

Description: Associate labors with their station

Participating Entity: Labors

Cardinality: 1

Optionality: mandatary

Participating Entity: Post

Cardinality: many

Optionality: mandatary

Relationship ID: R5

Relationship Name ( s ) : typeOfLabour, nameOfLabour

Description: Associate station with the labor type

Participating Entity: Post

Cardinality: many

Optionality: mandatary

Participating Entity: LabourType

Cardinality: 1

Optionality: mandatary

Relationship ID: R6

Relationship Name ( s ) : typeOfJobWorking, workingJobType

Description: Associate occupation type with the occupation

Participating Entity: JobType

Cardinality: 1

Optionality: mandatary

Participating Entity: Occupation

Cardinality: many

Optionality: mandatary

Relationship ID: R7

Relationship Name ( s ) : costOfPartUse, usePart

Description: Associate Job with JobCost for portion

Participating Entity: Occupation

Cardinality: 1

Optionality: mandatary

Participating Entity: JobCost

Cardinality: many

Optionality: mandatary

Relationship ID: R8

Relationship Name ( s ) : partType, usePartinJob

Description: Associate JobCost with Parts usage in occupation

Participating Entity: JobCost

Cardinality: many

Optionality: mandatary

Participating Entity: Part

Cardinality: 1

Optionality: mandatary

Relationship ID: R9

Relationship Name ( s ) : partCost, partType

Description: Associate portion with partcost bargain from assorted providers

Participating Entity: Partss

Cardinality: 1

Optionality: mandatary

Participating Entity: PartCost

Cardinality: many

Optionality: mandatary

Relationship ID: R10

Relationship Name ( s ) : suppliey, supplyBy

Description: Associate PartCost with providers by purchasing parts

Participating Entity: PartCost

Cardinality: many

Optionality: mandatary

Participating Entity: Supplier

Cardinality: 1

Optionality: mandatary

Representing Properties

Property: Criminal investigation command

Description: Idaho of client attention deficit disorders occupation

Type: whole number { 1, 2, 3, 4, 5 }

Property: CName

Description: Name of client attention deficit disorders occupation

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

Property: Address

Description: Address of client attention deficit disorders occupation

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

Property: Phno.

Description: Contact phone figure of client

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

Property: JID

Description: ID of occupation work for client

Type: whole number { 1, 2, 3, 4, 5 }

Property: Date

Description: Start day of the month of occupation

Type: day of the month { 2011-01-01, 2011-01-08, 2011-01-11, 2011-01-11, 2011-01-13 }

Property: WorkHour

Description: Entire hr of work for a occupation

Type: whole number { 75, 50, 90, 30, 48 }

Property: JTypeID

Description: ID of occupation type

Type: whole number { 1, 2, 3 }

Property: JType

Description: Type of occupation divide in occupation

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

Property: Eyelid

Description: ID of each labor work in occupation

Type: whole number { 1, 2, 3, 4, 5 }

Property: LName

Description: Name of labours work in occupation

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

Property: LTypeID

Description: ID of worker type divide in occupation

Type: whole number { 1, 2, 3, 4, 5 }

Property: LType

Description: Type of worker divides in the occupation

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

Property: RatePerHour

Description: money hold given to worker for an hr

Type: whole number { 50, 20, 55, 39, 50 }

Property: Monetary value

Description: Monetary value of portion bargains from assorted providers

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

Property: Pelvic inflammatory disease

Description: ID of parts use in the occupation

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

Property: PType

Description: Type of parts available in the occupation

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

Property: ImpCost

Description: Execution cost for each portion

Type: whole number { 5,10, 10, 10, 5, 7, 5, 10 }

Property: SID

Description: ID of provider who supplied parts

Type: whole number { 1, 2, 3, 4, 5 }

Property: SName

Description: Name of provider who supplied parts

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

Property: Address

Description: Address of provider

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

Property: Phno.

Description: Contact phone figure of Suppliers

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

Undertaking 2

Produce the resulting tabular arraies clearly bespeaking the primary and foreign keys.

Customer

Field Name

Data Type

Key

Criminal investigation command

Integer

Primary Key

CName

Varchar ( 30 )

Address

Varchar ( 45 )

Phno.

Varchar ( 20 )

Occupation

Field Name

Data Type

Key

JID

Integer

Primary Key

Criminal investigation command

Integer

Foreign Key

JTypeID

Integer

Foreign Key

Date

Date

WorkHour

Integer

JobCost

Field Name

Data Type

Key

Pelvic inflammatory disease

Integer

Primary Key

JID

Integer

Primary Key

JobType

Field Name

Data Type

Key

JTypeID

Integer

Primary Key

JType

Varchar ( 45 )

Labors

Field Name

Data Type

Key

Eyelid

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

Pelvic inflammatory disease

Integer

Primary Key

SID

Integer

Primary Key

Monetary value

Integer

Partss

Field Name

Data Type

Key

Pelvic inflammatory disease

Integer

Primary Key

PType

Varchar ( 45 )

ImpCost

Integer

Post

Field Name

Data Type

Key

Eyelid

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

Eyelid

Integer

Primary Key

JID

Integer

Primary Key

Undertaking 3

Using a Database Management System ( DBMS ) of your pick, set-up all of the above normalized tabular arraies, and dwell them with well-designed trial informations ( minimal 5 records per tabular array ) . Provide printouts of all tabular arraies.

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` ) )

Labors

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` ) )

Partss

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` ) )

Occupation

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 )

Undertaking 4

Set-up and test all of the undermentioned questions utilizing Structured Query Language ( SQL ) . Provide printouts of SQL codification for each question and the end product produced when you run the question in the database you have developed:

Display the names and reference of the clients of Marlowe Interiors and the Jobs and occupation types that have been carried out for them.

Expose a full record of a occupation. This should include the name of the client, the occupation type, the workers on the occupations and what type they are, the parts included in the occupation and the concluding overall cost for the occupation.

4 ( a )

SQL View

create position JobOfCustomer as

choice c.CName, c.Address, j.JID, j.Date, j.WorkHour, t.JType From Customer degree Celsius inner articulations Job J on c.CID = j.CID inner articulation JobType T on t.JTypeID = j.JTypeID

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

4 ( B )

Figure ( 4.2 ) Screen Shot for the consequence

SQL View

CREATE ALGORITHM=UNDEFINED DEFINER=`root` @ `localhost` SQL SECURITY DEFINER VIEW `fullcostofjob` AS choice `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` articulation ( ( `customer` articulation `job` on ( ( `customer`.`CID` = `job`.`CID` ) ) ) articulation ( ( `parts` articulation `jobcost` on ( ( `parts`.`PID` = `jobcost`.`PID` ) ) ) articulation `partcost` on ( ( `parts`.`PID` = `partcost`.`PID` ) ) ) on ( ( `job`.`JID` = `jobcost`.`JID` ) ) ) on ( ( `jobtype`.`JTypeID` = `job`.`JTypeID` ) ) ) articulation ( `labourtype` articulation ( ( `labours` articulation `working` on ( ( `labours`.`LID` = `working`.`LID` ) ) ) articulation `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 consequence tabular array

Undertaking 5

Explain any premise you have made when analysing, planing and implementing the above database, warrant the attack you have taken and explicate any alternate attacks you could hold taken to any of the above undertakings, Discuss any alterations you would do to better your work.

Premises for analysing, planing and implementing

I think the scenario is completeness of giving information, inside informations of needed petition of system and give point of the system or user demand petition. In Task-1, we make ERD and Data-Dictionary following the scenario. In Task-2, we make tabular arraies ; it includes field name and informations type ; so expressed primary key and foreign key. In Task-3, utilizing DBMS we make create tabular array and insert into trial informations of tabular array. In Task-4, utilizing Structured Query Language ( SQL ) make inquiry requested, it includes SQL codification and end product tabular arraies of print screen. In the Task-5 brand premise, analysing, planing, implementing, alternate attacks and to better my work. But all Tasks can be thinker widely and will be hold in this system at pulling tabular arraies.

For these assignment, I besides have to take four stairss which are indispensable in database development. They are

Requirements evocation

Conceptual mold

Logical modeling

Physical modeling

The techniques used in the development procedure of course divided into three classs: those concerned with conceptual mold, those concerned with logical mold and those concerned with physical mold. The cardinal input into he development procedure is a set of demands for a database system ; the key end product is the concluding database and associated maps.

Requirement evocation involves set uping the key proficient demands for a database system normally through formal and informal interaction between developer and organizational stakeholders such as users. In general footings it involves set uping the construction of informations needed and the usage of the information in some information systems context. One cardinal facet of demands evocation is the finding of the range of the ‘universe of discourse ‘ ( UOD ) to be convered by a proposed database system.

Conceptual mold involves constructing a theoretical account of the existent universe expressed in footings of the information demands established. First we discuss the well-established technique of entity-realtionship ( E-R ) schematization. This technique can be used to build and entity model- a representation of a UOD in term of entities, relationships and properties. An entity may be defined as a thing which and administration recognizes as being capable of an independent being and which can be unambiguously 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 pulling a line. An entity is characterized by a figure of belongingss of properties. Valuess assigned to properties are used to separate one entity from another. We besides choose one or more properties to move as identifiers for cases of an entity. In footings of relational scheme the entity identifier will finally turn into the primary key.

Harmonizing to this company database, I produce 11 entities. They are client, occupation, jobType, working, labors, labourType, station, jobcost, parts, partCost, provider. Customer and occupation have add work relation so relationship between them named R1. Job can hold many workers and the labor cost is depended on their work done. So at that place have dealingss between occupation and labors and working is link file between them. The relationships between them are named R2 and R3. There are besides have many type of worker. So, there have relationship between labors and lobourType. Post nexus for labors and labourType. Therefore, the relationship between them is R4 and R5. Job can hold three type of occupation. So, occupation and occupation type are besides have relation and their relationship is named R6. Job can be use many parts and entire portion cost involve their execution cost. So, occupation and portion have relation and jobCost is use as nexus file between them. The relationship between them is R7 and R8. Partss are supplied by many providers and their cost are depended on the assorted providers. In their relation, partCost is involved as nexus file. Their relationship is named R9 and R10. The properties contain in my system are CID for ID of Customer, CName for client name, Address and Phno. For contact item of client, JTypeID for ID of occupation type, JType for name of occupation type, JID for ID of occupation, Date for start working day of the month, WorkHour for entire clip for each occupation, LID for ID of worker, LName for name of workers, LTypeID of ID of labour type, LType and type of labor, RatePerHour for cost for each type of labor in one hr, PID for ID of parts, PType for type of parts, ImpCost for execution cost of parts, SID for ID of providers, SName for provider ‘s name, Address and Phno for contact item of provider.

Logical patterning involves building a theoretical account of the existent universe expressed in footings of the rules of some informations theoretical account. Because of its popularity we focus on the relational informations theoretical account in our discussing of logical mold. Entity or an object theoretical account may be mapped to a relational scheme. The logical database design technique of standardization. This technique enables us to build a relational scheme free from update jobs.

Physical mold involves building a theoretical account of the existent universe expressed in footings of informations constructions and entree mechanisms available in a chosen DBMS. Physical patterning involves two distinguishable subprocesses: physical database design and database execution. Physical dataset design comprises the procedure of footnoting a logical theoretical account with information refering to a peculiar application such as volume and usage information. The end product from the physical dataset design procedure is a database execution programs. Database execution involves taking the end product from physical database design and implementing the design determinations contained in the program in a chosen DBMS.

Data constructions declared in a suited information definition linguistic communication.

Indexs declared on the information constructions.

Clustering informations where appropriate.

A set of built-in unity restraints expressed in some informations definition linguistic communication and a set of extra unity restraints expressed in some informations unity linguistic communication.

A distribution scheme for the database system, including a program for administering informations.

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

The traditional demands evocation and specification activities of the ID development procedure take topographic point within system analysis. This corresponds to the information demands elicitation stage of the database development procedure plus conceptual mold. Conceptual mold, because of its cardinal function in documenting information demands at a high-level, besides overlaps with the traditional thought of systems analysis. Logical patterning corresponds largely to systems design in the sense of stipulating logical scheme and the incorporation of physical design determinations. Finally, physical design of database systems is one of the of import procedure relevant to modern- twenty-four hours information systems execution.

Alternate attack

There are many SQL database direction systems to run the questions. Among them, the most commonly usage is MySQL and Microsoft SQL. They have different advantages and disadvantages utilizing my system. In my system, I have use MySQL because it is the most suited for my system. There are some different advantages and disadvantages of MySQL and Microsoft SQL.

Open beginning vs. proprietorship

When it comes to these two databases, the difference in the MySQL open-source start at place against closed, proprietary structural characteristics of SQL Server. MySQL is a scalable, unfastened database storage engine, offers a assortment of fluctuations, such as in Berkeley DB, InnoDB, the reactor and MyISAM. On the other manus, Microsoft ‘s merchandises, will be limited to the engine and SYBASE from good and bad minutes.

In sing how the seamless integrating of MySQL programming linguistic communications and other assorted web-based engineering, surely in compatibility, such as SQL Server is known to work with Microsoft ‘s manner better than other merchandises, Microsoft SQL advantage.

Licensing

Contrary to popular belief, the system MySQL is non free. On the other manus, are ever cheaper. For both merchandises, licensing fees are based on a two-tier system. And MS SQL, the best manner is to purchase the Microsoft Developer development license or licence for Microsoft Visual Studio suite. SQL Server provides both growing in usage of free licences. If you want to utilize in a commercial environment the merchandise, you must buy a lower limit of SQL Server Standard Edition – this clip you can put a client connexion twosomes than 1000 U.S. dollars.

Because MySQL is based on open-source GNU General Public License system, developers can utilize without cost, provided the undertaking is unfastened beginning. However, if you intend to sell patented merchandises as your package, you must buy a commercial licence, which costs about $ 400 up to nine clients. On your work and the different financess, MySQL may hold the advantage here.

Technical differences

Merely in the conflict of unfastened beginning vs. proprietary chief ground why some choose more than one user to another system. However, there are from a proficient point of position, every bit good as some differences.

For illustration, MySQL does non supply 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 processs lack sufficient support – the biggest drawback is that the system MyISAM, it does non back up minutess.

Performance

Way through the public presentation, MySQL is the unchallenged leader, chiefly because of the default tabular array, MyISAM table format. MyISAM databases leave a little footmark, uses really small disc infinite, memory and CPU. When the system runs on Windows platform, the execution of the defects are frequently non in the Linux and UNIX every bit good as the other systems. Because of its stableness, as Yahoo usage MySQL as the backend database, a batch of power on the Internet.

When it comes to public presentation, strength of Microsoft SQL is packed with more characteristics than other systems may be the biggest disadvantage. Although most of these characteristics is designed to modulate the public presentation, they are frequently at the disbursal of other necessities. Here is the cost and complexness of storage and memory, ensuing in hapless public presentation off-road resources. If we lack sufficient cognition and equipment to back up a SQL Server, will work with other database direction systems better.

Security

The two database systems about deadlocked in footings of security. By default, all out appropriate security mechanisms have to obey orders and maintain current security spot. Both the known IP port operations to pull, unluckily, the interloper ‘s wealth can be attributed to the two merchandises at a disadvantage. The good intelligence is, MySQL, MS SQL allows to alter the port by default, merely excessively delicate.

Recovery

The Restoration to, SQL Server had a MySQL, a clear advantage, frequently fall short a small spot of support for MyISAM constellation. UPS system must be MyISAM, because it requires uninterrupted operation. If a power failure should happen, may take to impairment and loss of critical informations. In SQL Server, information corruptness is more likely. The information travel through the checkpoint in your keyboard to the difficult disc and passing through the screen. In add-on, SQL Server, delight follow this procedure, even if the system shut down out of the blue.

Although two of these have their assorted advantages and disadvantages, I have chosen MySQL to run my questions. I think it will be the most suited with my system to utilize.

Change to better my work

I besides want to alter these small things to better my work.

Inserting other auxiliary system to the exciting system to acquire a more complete system if possible

Making the plan design more beautiful and complete

Repair this system more efficaciously and efficient for users.

For the security of my system, doing user name and watchword protection to entree the database.

Cite this Report on Interior Design Company Database Development

Report on Interior Design Company Database Development. (2017, Jul 28). Retrieved from https://graduateway.com/report-on-interior-design-company-database-development/

Show less
  • Use multiple resourses when assembling your essay
  • Get help form professional writers when not sure you can do it yourself
  • Use Plagiarism Checker to double check your essay
  • Do not copy and paste free to download essays
Get plagiarism free essay

Search for essay samples now

Haven't found the Essay You Want?

Get my paper now

For Only $13.90/page