Explore BrainMass

Develop database tables using a relational database system

This is the problem:

Tom Ashton started Ashton Manufacturing Inc (AMI) several years ago. The Company has grown quickly from a small operation to the mid-sized organization it is today. AMI has an opportunity to take on an additional customer. This arrangement will allow AMI to grow to a large organization operating nearly 24 hours a day / 7 days a week.

Recently AMI has been experiencing significant downtime due to a failing software application written for AMI when the company started. This Access database application is responsible for a key manufacturing process.

Mr. Ashton and his investors are concerned the Company can not grow until the technical infrastructure is in place and functioning properly. AMI has limited funds for IT endeavors but has hired your consulting firm seeking advice.


Prepare a 1-page executive summary including your recommendations to repair or replace the application. Support this summary with a research paper which contains the details behind the summary.

Start by researching Microsoft Access and other prominent RDBMS such as MS SQL Server, Oracle and My SQL. Compare and contrast these systems based on key features such as scalability, ease of implementation (development and support), performance, security and price.

Include a discussion on SQL:

What is SQL?
Who owns SQL?
What are some of the differences in the SQL supported by RDBMS vendors?

© BrainMass Inc. brainmass.com July 20, 2018, 8:57 am ad1c9bdddf

Solution Preview

Th white paper at http://www.microsoft.com/sql/solutions/ssm/access/whenmigrate.mspx (aslo attached) explores the issues related to scaling up Microsoft Access applications to take advantage of the performance, security, and reliability of SQL Server.

Topics in this document discussed include:

? The Value of Access in Your Organization. A brief discussion of how Access provides power and agility to an organization's users.

? Access and SQL Data Architectures. A discussion of the type of data architectures that Access supports.

? Making the Decision: When to Upsize. An evaluation of the criteria to decide whether an application has outgrown the capabilities of Access.

? Upsizing Scenarios. An overview of the approaches to upsizing, and how to determine which one is best for you.

? Planning an Upsizing Project. An

SQL (commonly expanded to Structured Query Language - see History for the term's derivation) is the most popular computer language used to create, modify, retrieve and manipulate data from relational database management systems. The language has evolved beyond its original purpose to support object-relational database management systems. It is an ANSI/ISO standard.

An influential paper, "A Relational Model of Data for Large Shared Data Banks", by Dr. Edgar F. Codd, was published in June, 1970 in the Association for Computing Machinery (ACM) journal, Communications of the ACM. Codd's model became widely accepted as the definitive model for relational database management systems (RDBMS or RDMS).

During the 1970s, a group at IBM's San Jose research center developed a database system "System R" based upon, but not strictly faithful to, Codd's model. Structured English Query Language ("SEQUEL") was designed to manipulate and retrieve data stored in System R. The acronym SEQUEL was later condensed to SQL because the word 'SEQUEL' was held as a trademark by the Hawker-Siddeley aircraft company of the UK. Although SQL was influenced by Codd's work, Donald D. Chamberlin and Raymond F. Boyce at IBM were the authors of the SEQUEL language design.[1]. Their concepts were published to increase interest in SQL.

The first non-commercial, relational, non-SQL database, Ingres, ...