The PHLOX project

Very powerful data base management systems (DBMS) now exist which allow medical personnel access to patient record data bases. DBMS's make it easy to retrieve either complete or abbreviated records of patients with similar characteristics. In addition, statistics on data base records are immediately accessible. However, the price of this power is a large computer with the inherent problems of access, response time, and reliability. If a general purpose, time-shared computer is used to get this power, the response time to a request can be either rapid or slow, depending upon loading by other users. Furthermore, if the computer is accessed via dial-up telephone lines, there is competition with other users for telephone ports. If either the DBMS or the host machine is replaced, the medical users, who are typically not sophisticated in computer usage, are forced to learn the new system. Microcomputers, because of their low cost and adaptability, lend themselves to a solution of these problems. A microprocessor-based intelligent terminal has been designed and implemented at the USAF School of Aerospace Medicine to provide a transparent interface between the user and his data base. The intelligent terminal system includes multiple microprocessors, floppy disks, a CRT terminal, and a printer. Users interact with the system at the CRT terminal using menu selection (framing). The system translates the menu selection into the query language of the DBMS and handles all actual communication with the DBMS and its host computer, including telephone dialing and sign on procedures, as well as the actual data base query and response. Retrieved information is stored locally for CRT display, hard copy production, and/or permanent retention. Microprocessor-based communication units provide security for sensitive medical data through encryption/decryption algorithms and high reliability error detection transmission schemes. Highly modular software design permits adapation to a different DBMS and/or host computer with only minor localized software changes. Importantly, this portability is completely transparent to system users. Although the terminal system is independent of the host computer and its DBMS, it has been linked to a UNIVAC 1108 computer supporting MRI's SYSTEM 2000 DBMS.

Organizational culture is an important factor influencing knowledge management processes in small companies. Small entities usually have limited resources, both human and financial, to be able to develop advanced knowledge management systems. However, little research has been done so far to investigate the characteristics of organizational culture in small companies, in terms of knowledge management processes. Therefore, the aim of this research is the examination of organizational culture in small Polish companies with the application of a symbolic-interpretive perspective.

The focus of the present paper is on the data‐knowledge integration problem, whereby data and knowledge can be made radically more useful within the same framework. Most tools for developing knowledge‐based systems do not integrate well with data bases. This lack of integration is usually hampered by slow data base queries or by overly limited data base interfaces. On the other hand, since data base management systems are already well developed, leveraging knowledge‐based systems with data base management systems would provide significant advantages like speed, security, and portability across data formats (e.g. easy conversion between dBase and ASCII formats). In the present paper, we describe a novel approach to the data‐knowledge integration problem. This approach entails the simple but powerful extension of a data base system to increase its ability to represent and manipulate knowledge. We describe Kbase, an environment for developing knowledge‐based systems using facilities and extended constructs of the familiar dBase III data base programming environment. At the end, we use an implemented example, IPDOS, to support our hypothesis.

Introduction. The banking sector assigns high priority to data storage, as it is a critical aspect of business operations. The volume of data in this area is steadily growing. With the increasing volume of data that needs to be stored, processed and analyzed, it is critically important to select a suitable data storage solution and develop the required architecture. The presented research is aimed at filling the gap in the existing knowledge of the data base management system (DBMS) suitable for the banking sector, as well as to suggest ways for a fault-tolerant data storage cluster. The purpose of the work is to analyze the key DBMS for analytical queries, determine the priorities of the DBMS for the banking sector, and develop a fault-tolerant data storage cluster. To meet the performance and scalability requirements, a data storage solution with a fault-tolerant architecture that meets the requirements of the banking sector has been proposed.Materials and Methods. Domain analysis allowed us to create a set of characteristics that a DBMS for analytical queries (OnLine Analytical processing — OLAP) should correspond to, compare some popular DBMS OLAP, and offer a fault-tolerant cluster configuration written in xml, supported by the ClickHouse DBMS. Automation was done using Ansible Playbook. It was integrated with the Gitlab version control system and Jinja templates. Thus, rapid deployment of the configuration on all nodes of the cluster was achieved.Results. For OLAP databases, criteria were developed and several popular systems were compared. As a result, a reliable cluster configuration that met the requirements of analytical queries has been proposed for the banking industry. To increase the reliability and scalability of the DBMS, the deployment process was automated. Detailed diagrams of the cluster configuration were also provided.Discussion and Conclusions. The compiled criteria for the DBMS OLAP allowed us to determine the need for this solution in the organization. Comparison of popular DBMS can be used by organizations to minimize costs when selecting a solution. The proposed configuration of the data warehouse cluster for analytical queries in the banking sector will improve the reliability of the DBMS and meet the requirements for subsequent scalability. Automation of cluster deployment by the mechanism of templating configuration files in Ansible Playbook provides configuring a ready-made cluster on new servers in minutes.

This article discusses data security and controls, primarily in the context of data base management systems (DBMSs), with an emphasis on basic principles and mechanisms that have been successfully used by practitioners in actual products and systems. The general discussion does not focus on particular products, although a later section does review several products to illustrate previously discussed concepts. The discussion of data bases is limited specifically to relational DBMSs, which store data in relations that have specific mathematical properties. All examples given are in SQL. It is assumed that readers are familiar with rudimentary concepts of relational data bases and SQL. This article begins with a review of basic security objectives, followed by a discussion of access controls in the current generation of commercially available DBMSs. The problem of multilevel security is then introduced, including a review of techniques developed specifically for multilevel security.

The architecture of Geographic Information Systems (GISs) is changing: more and more systems are based on the integrated architecture, i.e. storing geometric data in the Data Base Management System (DBMS) together with administrative data. The first step in building a Geo-DBMS is by having data types and operators for simple features (i.e. geometric primitives): point, line and polygon. This has reached a level of standardisation and is now implemented in several commercial DBMSs. The next step is to have support for the topologically structured features in the DBMS, i.e. complex features. The DBMS can then check and guarantee consistency. In addition, complex operations can be executed within the DBMS. Despite the fact that topologically structured models are well known and that it is not difficult to store the topological references, it still remains an unresolved issue as to how to effectively implement these models within a relational DBMS. In this paper, we describe the design and implementation of a topologically structured management at the DBMS level. Our focus is to translate topological structures into geometric primitives. It is then possible to define a DBMS view on a topological primitive, which makes this appear as a geometric primitive. This process supports the best of both worlds: on the one hand there are advantages of the topological structure (no redundancy) and on the other hand the ease of explicit geometric primitives in querying, analysis and presentation is available.

In the past, commercial client/server systems were typically limited to configurations employing a single relational database management system (DBMS). Moreover, both client and server components were either designed by a single vendor, or constructed using one of the many application programming interfaces (API) available, restricting that application for use with the single DBMS for which that API was designed. Since then, customer expectations have grown to include connectivity and interoperability requirements for the heterogeneous mixture of applications and database products which comprise their enterprise: a diverse set of APIs, operating platforms, filetypes, and network operating systems. Middleware products have emerged to provide interoperability for these components via gateways, which map the APIs, data manipulation languages (DML), and database wire protocols of these diverse components. In addition to basic interoperability, the ease-of-use and performance characteristics of the middleware model have begun to change. The distributed database, constructed from middleware technologies, is seen as the means by which the distributed, heterogeneous enterprise computing environment can be integrated as a homogeneous unit. >

: The purpose of IDA Memorandum Report M-459, An Oracle - Ada/SQL implementation, is to identify and describe a version of a software delivery, an Oracle - Ada/SQL (Structured Query Language) implementation, to the WIS Joint Program Management Office. The software system provides a Level 1 Ada/SQL implementation which interacts with the Oracle database management system (DBMS) . It provides the ability to define Ada/SQL Data Definition Language (DDL) and Ada/SQL Data Manipulation Language (DML) which will be converted to the appropriate SQL calls required by the Oracle DBMS. Ada/SQL is a binding between Ada and the database programming language SQL. The software was developed on a VAX 8600, using VAX/VMS version 4.6, and the DEC Ada compiler, version 1.4-33.

This paper describes the data base approach to power system analysis studies, contrasts it with the traditional stand-alone application approach and discusses the issues which should be considered in developing a data base management system. The discussion is based on the experience gained in developing and implementing a power system data base management system at the Electricity Supply Commission (South Africa). The practical use of a central data base management system, together with a library of application programs and an interactive computing environment contributed significantly to the power system planning process in which individual engineers can work efficiently and interact among themselves using common data and analysis tools.

Data base management systems are gaining rapid and widespread use by organizations attempting to improve their data management facilities. Several commercial DBMS's are available and educators are increasingly introducing students to concepts and techniques of data management. An important part of grasping data management concepts is to provide hands-on experience in using a data base management system. The Educational Data Base System is a tool designed to provide this hands-on experience in a teaching environment. It has been used successfully in this capacity for several years and has been distributed to over twenty different organizations in seven countries. This paper briefly describes the system and outlines how it is used at the University of Toronto to augment classroom teaching of data management concepts.

Data base management systems are gaining rapid and widespread use by organizations attempting to improve their data management facilities. Several commercial DBMS's are available and educators are increasingly introducing students to concepts and techniques of data management. An important part of grasping data management concepts is to provide hands-on experience in using a data base management system. The Educational Data Base System is a tool designed to provide this hands-on experience in a teaching environment. It has been used successfully in this capacity for several years and has been distributed to over twenty different organizations in seven countries. This paper briefly describes the system and outlines how it is used at the University of Toronto to augment classroom teaching of data management concepts.

One method for performing exposure assessments is to use mathematical models that predict the transport and transformations of toxic substances in the environment. To run these models, a variety of input data on receiving water‐body properties and water‐quality parameters that define a range of environments and influence the chemical‐specific rate coefficients must be developed. A data base that contains selected hydrologic and water quality parameters has been developed by EPA for 15 major U.S. river basins. Called the Canonical Environments Data Base, the file brings together information developed by public and private organizations on each reach of the rivers as well as individual lakes and reservoirs in the basins. Coupling raw data with a data base management system in this environmental file will facilitate entry into and deletions from the data base and development of data input to the Exposure Analysis Modeling System (EXAMS) and other similar exposure assessment mathematical models. To a...

As data and information fusion technology and application evolves, the need is increasing to cope with large amounts and diverse types of data. Although there would be many benefits to employment of Data Base Management Systems (DBMS) in automated fusion processes the data access throughput requirements of automated fusion processes have vastly exceeded the performance of off-the-shelf DBMS's. The availability of large random access memories is allowing the development of real-time data base management systems. While these are currently being used in financial market and telecommunications applications, their ability to bring DBMS benefits to data fusion applications has yet to be explored. This paper presents results of experimentation with these emergent real-time DBMS's for automated fusion applications. We used algorithms, data characteristics, and scenarios from deployed and R&D systems. The applications-dependent data structures were converted to Entity-Relationship models and generated into real-time and conventional DBMS's.

The development of information technologies requires the processing of an increasing amount of information. A great number of tools and DBMSs for working with big data have been created. Examples of DBMS are: MS SQL Server, Oracle Database, SciDB, VoltDB, PostgreSQL XL, Clusterix, etc. Most systems of the BigData class require serious computing power to ensure acceptable performance. This article discusses the TPC-H test and 22 of its queries, the execution of which allows you to analyze the performance of database management systems (DBMS). PostgreSQL, MySQL, and Microsoft SQL Server DBMS are considered and their performance is investigated based on TPC-H test queries with database (DB) of various sizes in the DbVisualizer Free version 11.0.6.

A comparison of applications of microcomputers in production