Abstract This paper describes various issues to be taken into account when implementing an Oracle database. These include cost, platform, training and database design. It expands on the programming process. The author also explains the importance of choosing the right database for a company.
From the Paper "For most companies today their computer systems form the heart of the business. Web sites, accounting, sales, tracking, manufacturing, human resources and ancillary day-to-day functions all reside on various computer systems that are ..."
Abstract This paper examines the role of the database administrator, why they are necessary in organizations and how a database administrator differs from a knowledge manager. The paper examines the various jobs and functions of database management in large organizations.
From the Paper "Few companies today are able to exist without an information technology department. Whether a large multinational conglomerate or a small retail establishment nearly all companies rely on computers to some degree. Some companies are highly dependent on computer systems while others use them only for accounting and related tasks. Every organization even the smallest company has at least one person whose job entails making sure that the computer system is up and running or at least knowing who to call when the computer system goes ..."
Abstract The paper considers how a relational database can be used to store types of files not normally stored in this manner, such as images. The paper finds that a means of doing so has been developed for art history classes so that the instructor can access information, including images, as needed. The paper demonstrates how relational database management systems provide for relating files, or linking files to one another through a key field. The paper explains how a relational database system has the advantage of allowing a simple database system to grow as needed.
From the Paper "Relational database management systems provide for relating files, or linking files to one another through a key field. A relational database system has the advantage of allowing a simple database system to grow as needed. Data file management is flexible so it can handle integrating new requirements. In order to make a database system work, there are certain design rules that need to be followed. It is important to eliminate any repeating groups of fields and it is necessary to eliminate fields that do not depend entirely on the key field (Dologite 164-165). Databases in the future are likely to be influenced by five factors: developments in telecommunications, scanning and storage improvements, increasing database distribution options, user needs and demands and changes in database production. These are the factors influencing databases today, and they will continue to be the pivotal elements in the future (Tenopir 70-71)."
Abstract This paper discusses the importance of using a database for the efficient running of a modern hospital. The paper describes the uses of a database and what type of information it can store, from patient records to employee information. The paper describes the advantages of an enterprise Database Management System (DBMS) like the recommended MySQL Network that includes advanced customer support, reduces the paper trail and provides data driven applications. The paper includes some lists.
From the Paper "The database and database strategy are vital parts of any modern business. As you would expect in any business involving a large number of clients, computerized databases will play an important role in the data infrastructure. Customer records will be kept in a safe, fast and reliable database to maximize efficiency. This document will recommend a database plan for a hospital including potential uses, advantages and a recommended project plan to develop the database."
Abstract This paper thoroughly explains database normalization and views it as a series of steps designed to deal with ways in which tables can be more complicated than necessary. The paper contends that the purpose of normalization is to reduce the chances for anomalies to occur in a database.
From the Paper "In 1970, Dr. E.F. Codd's seminal paper "A Relational Model for Large Shared Databanks" was published in Communications of the ACM. This paper introduced the topic of data normalization, so-named because, at the time, President Nixon was normalizing relations with China. (Date, 1990)"
At first glance, Database normalization seems fairly simple. It's a technique used to ensure that there is only one way to know a fact. This is done by removing all structures that prove more than one way to know the same fact as represented in a database relation table. So, the goal of database normalization is to control and eliminate redundancy. One of the more complicated topics in the area of database management is the process of normalizing the tables in a relational database."
Abstract This paper covers many complex ideas relating to the way that we view databases in our culture. It proposes that the database will be the canvas of the future for artistic and cultural exploration. This paper also includes many references from leading scholars in the field.
From the Paper "Hail, hail to the menu driven computer interfaces that we have come to expect. These well made navigational systems of logical menus and clearly written labels, three button mice and ergonomic keyboards give us one of the most important technologies of our time the human computer interface (HCI). The HCI and the Graphical User interface (GUI) have been thought about and redefined as every new piece of computer hardware and software have been created. (The terms HCI and GUI will be used interchangeably as we are addressing the notion of interface.) The creation of the HCI has now mostly become the task of the new media artist. This becomes a very limiting constraint on the artist when the interface is the only element of a new media object that has any hope of becoming seen as a relevant area to create art. There are at least two other clearly definable media objects, the data and the database. I will focus here on the database. It is my contention is that a new media art piece can consist solely of a database without the need for the involvement of an interface. "
Abstract This paper discusses the increasing need for easy to operate database management systems and reviews the products currently available in the market. The three main players in this field are IBM, MICROSOFT and ORACLE.
Abstract This paper methodically examines Access SQL, MS SQL Server 2000, Oracle, DB2 and MySQL. The author explains, for example, that MS Access is a relational database management system used on desktop computer to manage information on different levels for different purposes and provides some capabilities for making a database available on the web. The paper continues, for example, that the system requirements for DB2 includes a Microsoft Windows 2000 SP4, Windows XP SP1 or Windows 2003 Server operating system, a Pentium 100 MHz or faster processor, 128MB or more RAM and a hard drive with 75 MB of free disk space with additional space required to store vulnerability information.
Table of Contents
MS Access
System Requirements (Access 2003)
Company
MS SQL Server 2000
System Requirements (with Service Pack 4)
Company
Oracle
System Requirements
Recommended Server Specifications
Minimum Client Specifications
Company
DB2
System Requirements
Company
MySQL
System Requirements
Company
From the Paper "Oracle is a relational database management system. Oracles latest technology, today's system designers and developers can build 21st century enabled applications ranging from critical online transaction processing systems supporting thousand of users to multi-terabyte data warehouses for decision support and also World Wide Web-based applications. Bradmark Technologies is a company that offers database management software used with products from providers including Oracle, Sybase and Microsoft. Customers in a variety of industries use Bradmark's products for tasks such as database monitoring, performance tuning and database administration."
Abstract This paper considers major issues facing database administrators today, including privacy, networking, security, data storage, staff training and staff retention. It includes a technical description of these issues including firewalls protection, data warehousing, need for effective database administration, bounded and unbounded media.
From the Paper "It is difficult to imagine how most companies could operate without databases in today's business environment. Indeed most organizations whether private or public profit or non-profit depend on ..."
Tags:database administration, privacy, data storage, networking, security
Abstract This paper considers heterogenity, openness, scalability, security, concurrency, failure handling and transparency in distributed databases. It defines "distributed databases." The paper provides an analysis of its benefits and looks at productivity gains and security issues.
From the Paper "As its name suggests a distributed database is a collection of data that is located in several different physical locations-that is distributed over several resources-while operating as a single logical database. This provides system managers the ability to distribute the database over multiple systems depending on system resources and to use either local or wide area networks to access the data. When this type of database configuration is used there are obviously many different factors that need to be taken into account ..."
Abstract This document discusses the need for the AIG WarrantyGuard Company to implement a relational database solution in order to reduce human error and increase efficiencies. This solution will also simultaneously impact revenues in a positive manner because invoicing and billing processes will be maximized. Additionally, the paper discusses how customer service quality will also be positively impacted through the facilitation of e-billing strategies enabled through the implementation of a relational database application.
From the Paper "AIG WarrantyGuard, Inc. (AIGWG) is a watch warranty company that accepts, completes and submits watch warranty invoices for warranty work done on behalf of OEMs for their customers. These warranty forms are complicated, time-consuming to complete and often rejected on the basis of simple clerical errors. The entire invoicing and billing procedure consumes substantial resources in terms of human capital spent completing and processing them, submission, and re-processing them if they have been rejected. Additionally, operating revenue is frozen while these invoices for billing are in the approval and payment process which, due to these invoicing clerical type errors, freezes a substantial amount of revenue from application elsewhere."
Abstract The paper states that organizations depend on distributed information systems for discharging routine business needs. The paper then discusses their susceptibility to security compromises increases, although they achieve output and competence. The paper states that methods like electronic signatures and encryptions are presently accessible for safeguarding data at the time of its transmission. The paper further stresses the importance that a practically broad strategy for data protection should cover methods for putting in place access control policies which are dependent on subject qualifications.
Outline:
Introduction
Most Relevant Concepts Underlying the Notion of Database Security
and the Well Known Techniques
Current Challenges for Database Security and Some Preliminary
approaches that Address Some of Chese Challenges
Access Control Systems, and Description of the Key Access Control
Models, Namely, the Discretionary and Mandatory Access Control
Models, and the Role-based Access Control (RBAC) Model
Additional Recommendations
Conclusion
From the Paper "Keeping a repository of centralized data is of utmost significance for the information management. Because of this, it is important to build a database concept which outlines the readiness needed for functioning of the database. It must always cover a database security concept that concentrates on the operation of the database. Improper safeguarding of data might compromise database confidentiality, its availability and integrity. In order to prevent this, it is very important to form a comprehensive 'database security' concept. For ensuring the security of a database, an appropriate database management system -- DBMS is required to be functional. For successful protection, the database management system must compulsory fulfill the necessities stated below.''
Abstract This paper discusses how companies using the Internet can gather and compare massive amounts of data on the consumer, and potentially allows for unethical use of such data. The paper further discusses how keeping this data in a database often serves the customer by allowing for processes such as giving discounts at the checkout stand, sending offers to interested customers and tailoring the product to the needs of the average consumer, the process also has the potential for abuse. This abuse includes invasion of privacy, selling data to other companies and keeping track of customer purchases for questionable reasons.
Abstract This paper examines the concept of abstract authentication in federated database systems and the difficulties presented because the autonomously operated components may not know the identity of federation users. It looks at how one proposed solution is subject switching, where the federation translates the federated users identity to that of an agreed upon component subject and how this translation may be problematic due to not having component subjects with the same accesses requested by federation users. It proposes using proximity measures between requested and provided access and presents two policy neutral algorithms to find proximity minimizing matches between a federation subject and a collection of component subjects. It also explores the concepts relating to federated databases, authorization and access, and proposes some algorithms that will facilitate the subject switching method of reconciling access requirements.
Outline
Section 1
Abstract
Background
Introduction
Characteristics of Federated Databases Homogeneous vs. Heterogeneous Databases Agents
Agents and Meaning
Perspective
Types of Meaning
Semantics Versus Pragmatics
Context
Coverage of Communicative Acts
Mental Versus Social Agency
Section 2
Federated Database Systems and Autonomy
Design Autonomy
Communication Autonomy
Execution Autonomy
Association Autonomy
Authorization Autonomy
Distribution Transparency (i.e., Schema Integration)
Tightly Coupled
Limited Tight Coupling
Loosely Coupled
Federated Database Security
Authorization
Standards for Authentication
Decentralized vs. Centralized Authorization
Access Controls
User Based Access Control (UBAC)
Policy Based Access Control
Content Dependent Access Control (CDAC)
Context Based Access Control (CBAC)
View Based Access Control (VBAC)
Discretionary Access Control (DAC)
Mandatory Access Control (MAC)
Role Based Access Control (RBAC)
Section 3
Subject Switching
Subject Mapping Algorithms
Mapping Process
Federation Mapping Process
Federation Identity
Component Mapping Process
Minimum Disparity Measure
Mapping Algorithm
Create Object Sets
Identify Component Subjects
Evaluate Matching Subjects
Access Disparity Measures
Numerical Disparity Measure
Comparing Disparity Measures to Approximate Measures
Approximate Disparity Measure Comparison
Motivating Example
Access Compatibility Measures and Algorithms
Compatibility of Permissions and their Disparity Measures
Cardinality
Express Specification
Section 4
Metrics
Algorithm 1 (Least Under Permitting Algorithm)
Algorithm 2 (Least Over Permitting Algorithm)
Approximations: Metrics And Mappings
Approximate Mapping Algorithms
Algorithm 3 (Approximate Under Permitting Algorithm)
Algorithm 4 (Approximate Over Permitting Algorithm)
Properties of Algorithms 3 and Algorithm 4
Multilevel Federations
Non-Protected Database Axioms
Deductive Channels Control Theorems
Signalling Channels Control Theorems
Cover Story
Multi-view Databases Languages
Section 5
Conclusions and Ongoing Work
References
From the Paper "Heimbingner and McLeod coined the phrase Federated Database System in 1985, and Seth and Larson later confirmed the formal definition. While the term has been loosely used to refer to several different but related database systems, they more precisely and unanimously define it as a collection of cooperating but autonomous component database systems. [SL90] (According to Oszu 1999, semi-autonomous systems are termed federative DBMS). A federated database system represents a compromise between no integration, wherein users must explicitly interface with multiple autonomous databases, and total integration, where the autonomy of each distinct database is sacrificed in order to allow users access through a single global interface."
