The Concept and Benefits of the Database System - Essay Example

Database Contents Introduction 3 Task 4 Task 2: 10 Task 3: 12 Task 4: 18 Task 5: 22 Conclusion 24 Introduction The database understanding and report are the various criteria that have been achieved in this report. A database scenario is explained to its very length with the entities, attributes, cardinality, assumptions, relationships and input/output screens. The concept and benefits of the database system is explained with detailed analysis of the commercial and non-commercial purposes. Task 1: The E-R-D is as follows: Figure 1 : ERD for SWAPSONGS The above ERD shows the following: Entities – (venue, booked, stall, dealers and fans) Relationships - (is, pay_for, have, book) Cardinality has been shown by symbols – (N, M, 1) The following are the assumptions taken into consideration for the ERD: For entities: Venue is the entity which is linked with dealers as the later books venues, venue is also linked with stalls as it houses stalls, it is also liked with fans as they pay for venues Booked is an entity where the venues are booked and is a demarcation from the available venues Dealers make bookings for the venue and in turn stalls Stall is an entity where the dealers put up their show Fans are ones who pay for the venues they desire to visit for a price For cardinality: Between venue and booked, there is a N:1 relationship, meaning many available venues can be booked however a booked venue is not available Between venue and dealers, the cardinality is N:M, meaning that many venues can be booked by one or more dealers however one or many dealers can book several venues. Between venues and stalls, the cardinality is M:N, meaning that one or many venues can have stalls and one or many stalls have one or many venues. Between venues and fans, the cardinality relationship is M:N, meaning that one or more fans pay for one or many venues and similarly more than one venue can be afforded by a single fan. For relationships: The relationship – “is” – is between venue and booked giving an implication that either a venue is available or booked. The relationship – “book” – is between venue and dealers giving an implication that venues are booked by dealers The relationship – “have” – is between venue and stalls, an implication that venue houses stalls. The relationship – “pay_for” – is between the venue and fans, an implication that fans pay for their admit at the venues. List of tables and attributes for the database: Venue (Vid (PK), name, address, phone, contact, cost_per_day, max_tables_sqfeet_avl, newspapers_for_ads) Booked (Bid (PK), date, sq_ft, total_cost, adverts, cost_of_adverts, cost_paid) Dealer (Did (PK), name, name_and_address, genre, credit_rating, reliability_rating, normal_sqfeet_req) Fans (Fid (PK), name, price) Stall (Sid (PK), name) Book (Vid, Did) Have (Vid, Sid) Pay_for (Fid, Vid) Data dictionary: Table 1: Venue Attributes Data Type Description Vid Number (10) Unique primary key. Name Char (30) Name of the venue Address Char (100) Address of the venue Phone Number (15) Phone number of the venue Contact Char (30) Contact number of the person for consultation. cost_per_day Number (5) Cost of the room per day max_tables_sqfeet_avl Number (5) Maximum number of tables available per square feet newspapers_for_ads Char (200) Newspapers for the advertsements Table 2: Booked Attributes Data Type Description Bid Number (10) Unique primary key. Date DATE Date of the booking Sq_ft Number (100) Square feet booked Deposit paid Number (15) Advance paid for the booking Adverts Char (200) Adverts for the booking Cost_paid Number (5) Cost paid until now Table 3: Dealer Attributes Data Type Description Did Number (10) Unique primary key. Name Char (30) Name of the dealer Name_and_address Char (200) Complete details Genre Char (20) Genre played by the dealer Credit_rating Char (200) Credit rating of the dealer Normal_sqfeet_req Number (5) Square feet required Reliability_rating Char (30) Reliability rating of the dealer Table 4: Fans Attributes Data Type Description Fid Number (10) Unique primary key. Name Char (30) Name of the dealer Price Number (5) Price paid for the venue Table 5: Stall Attributes Data Type Description Sid Number (10) Unique primary key. Name Char (30) Name of the stall Table 6: Book Attributes Data Type Description Vid Number (10) Unique primary key. Did Number (10) Unique primary key. Table 7: Have Attributes Data Type Description Vid Number (10) Unique primary key. Sid Number (10) Unique primary key. Table 6: Book Attributes Data Type Description Vid Number (10) Unique primary key. Did Number (10) Unique primary key. Table 7: Pay_for Attributes Data Type Description Vid Number (10) Unique primary key. Fid Number (10) Unique primary key. Task 2: To produce a database implementation for the SWAPSONGS, the following are the various tasks undertaken: The tables are normalized up to 3NF with all the attributes and the necessary relationships The input and output screens are depicted as follows: The input screens are as follows: Figure 2 : Login screen Figure 3 : Dealer entry form Output screens are as follows: Figure 4 : Outstanding bills for dealers Task 3: Navathe (2003) defines database as a collection of programs that enables users to create and maintain a database. It can also be defined as general purpose software for defining, creating, fetching and sharing databases among various users. Features of a database are as follows: Security: It ensures multilevel security capabilities to protect access of data. It can control access based on data sensitivity, quite easy to implement and enforce compliance (Navathe, 2003). Advanced security features: The blend of network and data encryption make sit quite strong to secure its users and enforce privacy of data (Navathe, 2003). Large control factor: It is able to store and manage large documents and files in an efficient manner so that one is able to properly utilize for meeting the demands of a large enterprise (Navathe, 2003). The further benefits can be summarized as follows: Information access is centralized Development and administrative costs are low Mining of data: It increase productivity and make sure that the database would be used for deriving a new value for futuristic predictions and trend analysis (Navathe, 2003). Business intelligence: It enables standards to grow with the enterprises growth and expansion and proper analysis of the users are kept in mind in making good a situation (Navathe, 2003). OLAP: It facilitates planning, budgeting, forecasting and sales. Optimization of queries are done to access multi-dimensional data. It can allow providing decision makers with access to data in a faster and with lower costs (Korth, 2003). Partitioning: It develops manageability, performance and availability. It can greatly simplify common admin tasks. It allows the database administrator to manage large scale information (Korth, 2003). RAC allows multiple computers to access a single database simultaneously; it addresses several areas of database management. The benefits and of a database in a commercial and non-commercial are the following: Provides resourceful maintenance of cross-platform issues Recovery manager: The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following: The target database to be backed up The RMAN client, which interprets backup and recovery commands, directs server sessions to execute those commands, and records your backup and recovery activity in the target database control file. Some environments will also use these optional components: A flash recovery area, a disk location in which the database can store and manage files related to backup and recovery (Navathe, 2003). Media management software, required for RMAN to interface with backup devices such as tape drives A recovery catalog database, a separate database schema used to record RMAN activity against one or more target databases Facilitates efficient support for updatable views and strict mode. The facility of independent storage engines Support for SSL Full text indexing and searching Provides support for pluggable storage engine API Event scheduling The library cache is facilitated to storage of shared SQL and it scans the parse tree and execution plan for all SQL statement. Efficient data dictionary for strong user information, integrity constraints, names and data types, space allocation sizes It monitors job queue processes, log writer processes, remote file server and shared server techniques Offers an efficient recovery manager Provides for guarding of data and sense the high availability Quite economical in prices and development methods for encompassing the organizational data and taking care of various updations and changes in the business environment. The transaction management is quite efficient in the manner that if a transaction is not able to complete it is roll backed so that changes can be reversed. In that manner data integrity is maintained. The concurrency control is quite effective and it ensures data integrity. It facilitates replication which ensures that proper synchronization is done for the information in the databases. It also facilities merge and snapshot replication Monitoring, logging, and performance tuning additions More control over creating and dropping objects Table inheritance relationships can be defined for and removed from pre-existing tables Task 4: Presentation of the database and its interpretation of the above. Staff Training: The planning done to help an organization ensure its planned database is accepted by users and administrative alike, functional for all major constituency groups and continually reassessed for improvement is as follows: Access privileges and user spaces: The planned database must ensure that all the users are classified into groups, users and others and give them respective privileges to access information and perform database functions. The login credentials make sure that the intended user gets to access according to their credentials. Database documentation: The extensive documentation produced as “technical understanding document” and “business understanding document” makes the entire database clear in its constructs and definition. The variables, database environment and user details are focused in the document. Separate business workflow design: The database must illustrate the business processes it wishes to cover and make sure the exact position where the database if utilized by the business process for storing information and retrieval of further knowledge from the database for performing database functions and swift flow of the process. Penetration of the database: The various relationships of the database with internal and external systems must be stated clearly so that the connections can be made useful to the users and make them aware of its vast nature of uses and accessibility. Keeping in touch with modification document: The database modification document must be published to all the users and stakeholders of the database so that any user is able to ascertain the state and current position of the database at any given point of time. Performance reports and database tuning: They are required to keep in synchronization with changing environment and organization flexibility to adopt and diversify into higher avenues (Navathe, 2002). The plan for getting the users trained for a database environment is as follows: Create a plan to measure the users background and their privileges for access Evaluate their comfort level to handle the database operations Create a documentation to feature step by step action and guidance Preparing agendas for short discussions for background to the database and the related organization Creating online and help tutorials so that one is able to consult when required Create a detail document for all errors and expected feedbacks which the system is built up Giving full knowledge to confirmation screens when adding, modifying or deleting data from databases Understanding the roles of the users and security and user tracking details Ethics document must be shared to make users aware not to share their passwords, exercise ethical process to determine use and change of databases Understanding the role of database administrator and the privileges that are to be enforced Providing further telephonic and web support for al users at all times The above plan is suitable to train all the users of the system. Task 5: The primary method for doing this assignment is as follows: The database concepts were revised and checked with the various books The case scenario was studied carefully Entities were noted secondly Association between the entities were taken care to map the relationships Cardinality among the entities were taken care according to the assumptions ERD was constructed and revised by cross checking the ERD and the case scenario Data dictionary was successfully developed form the attached files Database concepts were extensively used for making the entire task successful. Conclusion Exposure to a case study has finalized the database concepts that are required in a business scenario to capture the information and make good of all the aligning features and technologies provided by the database management systems in order to learn and master the concepts for future benefits to emerge as a database designer. References/ Bibliography Korth, F. Henry (2003). Database Management systems. McGraw Hill. Navathe, Elmasri (2003). Fundamentals of Database systems, Singapore: Pearson Education. Read More