DOCSLIB.ORG

Mediator RDD

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mediator RDD Document describes a way of migrating CA-Clipper or (X)Harbour applications to an SQL environment using Mediator RDD. It also contains some hints how to effectively use Mediator and the description of additional functions of the software package. Mediator v.5.0 User’s Guide and Reference © OTC S.A., 2012 Contents I. INTRODUCTION ....................................................................... I-1 1. MEDIATOR ....................................................................................................... I-1 2. The MEDNTX driver ........................................................................................ I-4 3. The MEDCDX driver ........................................................................................ I-4 4. Application migration – the MEDNTX and MEDCDX drivers ....................... I-4 5. Language extensions ..................................................................................... I-5 6. Working in WAN .............................................................................................. I-5 7. Summary ......................................................................................................... I-5 II. GETTING STARTED ................................................................ II-1 1. The necessary components .......................................................................... II-1 2. Preparation of Windows NT/2000/XP server ................................................ II-3 3. Preparation of the database server .............................................................. II-4 a) Preparation of the Oracle server ................................................................................ II-4 b) Preparing the Microsoft SQL Server .......................................................................... II-5 c) Preparing Sybase Adaptive Server Anywhere ........................................................... II-7 d) Preparing PostgreSQL ............................................................................................... II-8 e) Preparing other DBMSs ............................................................................................. II-9 4. Preparing the MEDIATOR server ................................................................ II-10 5. Preparing the CA-Clipper client .................................................................. II-10 6. Setting up the (x)Harbour client ................................................................. II-13 7. Compatibility between the versions of the Mediator client and the server II- 15 III. OPERATING THE MEDIATOR SERVER ............................... III-1 1. Mediator for Windows NT/2k/XP (desktop version) ................................... III-1 a) Starting the server .................................................................................................... III-1 b) Configuration and management ............................................................................... III-1 c) The main panel of the Mediator server for Windows ................................................ III-2 2. Mediator for Windows NT/2k/XP (service version) .................................... III-4 a) Starting the server .................................................................................................... III-4 b) Configuration and management ............................................................................... III-4 3. Mediator for NetWare ................................................................................... III-4 a) Starting the server .................................................................................................... III-4 b) Configuration and management ............................................................................... III-4 c) The main panel of the Mediator server for NetWare ................................................. III-4 4. An external configuration program with a monitor for Mediator servers III-7 a) MMT application console .......................................................................................... III-7 b) Server description (window: Description of...) ........................................................ III-10 c) Editing Mediator server parameters (dialog: Configure Server...) .......................... III-12 d) Defining, editing and deleting users of the Mediator server (dialog: Users of...) .... III-15 e) System monitor ....................................................................................................... III-19 MEDIATOR 5.0. User’s Guide i IV. ADAPTING APPLICATIONS FOR WORK WITH RELATIONAL DATABASE MANAGEMENT SYSTEM .................................. IV-1 1. RDD drivers: MEDNTX and MEDCDX ......................................................... IV-1 2. Planning of application porting .................................................................. IV-1 3. Stages of adapting an application .............................................................. IV-1 4. Stage I: basic porting of an application ..................................................... IV-2 a) Data export ............................................................................................................... IV-2 b) Modification of the application source code .............................................................. IV-5 c) Benefits acquired from first stage of adapting an application ................................... IV-8 5. Stage II: the interface to the RDBMS transaction system ........................ IV-9 a) Introducing transactions ............................................................................................ IV-9 b) Benefits acquired from stage II of adapting an application ..................................... IV-10 6. Stage III: using SQL extensions ............................................................... IV-11 a) Introduction of SQL ................................................................................................. IV-11 b) Benefits acquired from stage III of adapting an application .................................... IV-12 7. Stage IV: integrating an application with other SQL applications ........ IV-12 8. Portability ................................................................................................... IV-13 9. Guidelines for Clip-4-Win users ............................................................... IV-13 V. EXTENSIONS OF THE MEDIATOR PACKAGE ...................... V-1 1. Using objects owned by other users .......................................................... V-1 2. Using non-standard extensions in names of databases and indexes ..... V-1 3. Cooperation of MEDNTX and MEDCDX drivers ......................................... V-2 4. The scope mechanism (SCOPE) ................................................................. V-2 5. Deleting objects from the database ............................................................ V-3 6. Filtering ......................................................................................................... V-3 7. Using SQL ..................................................................................................... V-5 8. Trapping SQL errors ..................................................................................... V-6 9. Transactions ................................................................................................. V-6 10. The record marking subsystem in RDBMS ................................................ V-8 11. Specification of storage parameters for tables and indexes in Oracle .... V-8 12. Locking tables and records ......................................................................... V-9 13. Mediator client in multithreaded applications .......................................... V-10 VI. WORKING WITH UNICODE .................................................... VI-1 VII. FUNCTIONS AND PROCEDURES OF MEDNTX AND MEDCDX DRIVERS ................................................................................ VII-8 1. BEGIN TRANSACTION ................................................................................................... VII-8 2. COMMIT TRANSACTION .............................................................................................. VII-9 3. DROP INDEX .................................................................................................................... VII-9 4. DROP TABLE .................................................................................................................... VII-9 5. MedAdir ............................................................................................................................ VII-10 6. MedChgPwd ..................................................................................................................... VII-11 7. MedChrIdxT ..................................................................................................................... VII-11 8. MedClntId ......................................................................................................................... VII-12 9. MedClpComp ................................................................................................................... VII-12 ii MEDIATOR 5.0. User’s Guide 10. MedClrTbCa .................................................................................................................... VII-12 11. MedClrScpe .....................................................................................................................
Load more

Recommended publications
  • A Genetic Algorithm for Database Index Selection
    GADIS: A Genetic Algorithm for Database Index Selection Priscilla Neuhaus, Julia Couto, Jonatas Wehrmann, Duncan D. Ruiz and Felipe Meneguzzi School of Technology, PUCRS - Pontifícia Universidade Católica do Rio Grande do Sul - Porto Alegre, Brazil Email: [priscilla.neuhaus, julia.couto, jonatas.wehrmann]@edu.pucrs.br, [duncan.ruiz, felipe.meneguzzi]@pucrs.br Abstract—Creating an optimal amount of indexes, taking optimize the query response time by search for faster index into account query performance and database size remains a configurations when compared to the initial one. challenge. In theory, one can speed up query response by creating We perform a set of experiments using TPC-H, a well indexes on the most used columns, although causing slower data insertion and deletion, and requiring a much larger amount of known database benchmark [11], and we compare our results memory for storing the indexing data, but in practice, it is very with three baseline approaches: (i) the initial index configura- important to balance such a trade-off. This is not a trivial task tion; and (ii) indexes derived from a random-search algorithm. that often requires action from the Database Administrator. We Results show that GADIS outperforms the baselines, allowing address this problem by introducing GADIS, A Genetic Algorithm for better index configuration on the optimized database. for Database Index Selection, designed to automatically select the best configuration of indexes adaptable for any database Finally, we observe that our approach is much more prone schema. This method aims to find the fittest individuals for to find a proper solution that the competitive methods.
    [Show full text]
  • Augusto Campos COLUNA Saudades Do EMM386 E Do HIMEM.SYS? É Possível Rodar Sistemas Legados Feitos Para DOS Sem Recorrer a Software Proprietário
    Sistemas legados e Software Livre Augusto Campos COLUNA Saudades do EMM386 e do HIMEM.SYS? É possível rodar sistemas legados feitos para DOS sem recorrer a software proprietário. impressionante quantos programas desenvol- dar um passo a mais e investigar a possibilidade de rodá-lo vidos originalmente para ambientes MS-DOS nativamente no ambiente Linux, usando ferramentas como É ainda podem ser encontrados rodando hoje, em o Harbour [3], o xHarbour [4] ou o Flagship [5], sendo que organizações de todos os portes e perfis. A sensação de apenas os dois primeiros são softwares livres. Um conhecido incongruência não é causada apenas pela abundância meu ganhou um bom dinheiro, há alguns anos, prestando de recursos hoje disponíveis nos sistemas operacionais e exatamente esse serviço para diversas empresas da sua região ambientes correntes, mas principalmente porque já faz 12 – os sistemas funcionam bem, e passam a ter acesso a alguns anos que a Microsoft lançou a última versão stand-alone recursos mais modernos, com pouca ou nenhuma alteração desse sistema operacional que já dominou a computação na sua base de código. pessoal e foi a base da “revolução Clipper” que dominou a automação comercial brasileira no final da década de 80 e começo da de 90. Um conhecido meu Ao longo do meu envolvimento com o Linux e o código aberto, já encontrei diversas situações em que uma organiza- ganhou um bom ção desejava migrar de plataforma, mas tinha como entraves dinheiro prestando alguns sistemas legados, que rodavam em ambiente DOS, e cujo código-fonte há muito foi extraviado ou foi desenvolvido exatamente este em uma linguagem que ninguém mais domina – tornando indesejável ou muito caro portá-lo, e excessivamente com- serviço para plexo desenvolvê-lo de novo.
    [Show full text]
  • Response Time Analysis on Indexing in Relational Databases and Their Impact
    Response time analysis on indexing in relational databases and their impact Sam Pettersson & Martin Borg 18, June, 2020 Dept. Computer Science & Engineering Blekinge Institute of Technology SE–371 79 Karlskrona, Sweden This thesis is submitted to the Faculty of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the bachelor’s degree in software engineering. The thesis is equivalent to 10 weeks of full-time studies. Contact Information: Authors: Martin Borg E-mail: [email protected] Sam Pettersson E-mail: [email protected] University advisor: Associate Professor. Mikael Svahnberg Dept. Computer Science & Engineering Faculty of Computing Internet : www.bth.se Blekinge Institute of Technology Phone : +46 455 38 50 00 SE–371 79 Karlskrona, Sweden Fax : +46 455 38 50 57 Abstract This is a bachelor thesis concerning the response time and CPU effects of indexing in relational databases. Analyzing two popular databases, PostgreSQL and MariaDB with a real-world database structure us- ing randomized entries. The experiment was conducted with Docker and its command-line interface without cached values to ensure fair outcomes. The procedure was done throughout seven different create, read, update and delete queries with multiple volumes of database en- tries to discover their strengths and weaknesses when utilizing indexes. The results indicate that indexing has an overall enhancing effect on almost all of the queries. It is found that join, update and delete op- erations benefits the most from non-clustered indexing. PostgreSQL gains the most from indexes while MariaDB has less of an improvement in the response time reduction.
    [Show full text]
  • Relational Database Index Design
    RReellaattiioonnaall DDaattaabbaassee IInnddeexx DDeessiiggnn Prerequisite for Index Design Workshop Tapio Lahdenmaki April 2004 Copyright Tapio Lahdenmaki, DBTech Pro 1 Relational Database Index Design CHAPTER 1: INTRODUCTION........................................................................................................................4 INADEQUATE INDEXING .......................................................................................................................................4 THE IMPACT OF HARDWARE EVOLUTION ............................................................................................................5 Volatile Columns Should Not Be Indexed – True Or False? ..........................................................................7 Example ..........................................................................................................................................................7 Disk Drive Utilisation.....................................................................................................................................8 SYSTEMATIC INDEX DESIGN ................................................................................................................................9 CHAPTER 2........................................................................................................................................................13 TABLE AND INDEX ORGANIZATION ........................................................................................................13 INTRODUCTION
    [Show full text]
  • IBM DB2 for I Indexing Methods and Strategies Learn How to Use DB2 Indexes to Boost Performance
    IBM DB2 for i indexing methods and strategies Learn how to use DB2 indexes to boost performance Michael Cain Kent Milligan DB2 for i Center of Excellence IBM Systems and Technology Group Lab Services and Training July 2011 © Copyright IBM Corporation, 2011 Table of contents Abstract........................................................................................................................................1 Introduction .................................................................................................................................1 The basics....................................................................................................................................3 Database index introduction .................................................................................................................... 3 DB2 for i indexing technology .................................................................................................................. 4 Radix indexes.................................................................................................................... 4 Encoded vector indexes .................................................................................................... 6 Bitmap indexes - the limitations ....................................................................................................... 6 EVI structure details......................................................................................................................... 7 EVI runtime usage...........................................................................................................................
    [Show full text]
  • Sql Server Index Fragmentation Report
    Sql Server Index Fragmentation Report Reflexive Clayborne miaows, his vibrometer tuck swelled silverly. Improbable Lionello always winches his ironist if Wain is executive or excite incompetently. Cornelius remains noble after Timothy ionizing perceptually or priggings any writes. Fragmentation in DM SQL Diagnostic Manager for SQL Server. Regular indexes rebuild at SQL-Server 200 and higher necessary Posted on Apr 01 2011. This will rejoice you owe determine the upcoming impact should any changes made. You use need to retype it select another editor or in SSMS. Is there something I need to invoke to cause it to be available? Dmf to sql server and reformat them to check index automatically by fragmented, and reorganize operations are. Index operation is not resumable. Httpblogsqlauthoritycom20100112sql-server-fragmentation-detect-fragmentation-and-eli minate-. How to Proactively Gather SQL Server Indexes Fragmentation. Indexes play a vital role in the performance of SQL Server applications Indexes are created on columns in tables or views and objective a quick. DO NOT do this during office hours. Please contact your sql servers that fragmented indexes and reports tab, indexing data published on thresholds to continue browsing experience in one person? Thanks for the code. And server reporting any fragmented indexes optimization was creating storage and easy to report taking into block right on this index for servers are reclaimed on modern frozen meals at that? Just a restore from backup, schools, monitoring and high availability and disaster recovery technologies. Dmdbindexphysicalstats to report fragmentation of bird and indexes for a specified table mountain view Many companies use maintenance plans to work regular.
    [Show full text]
  • Drupalist Resume - 07.27.21 Page 1 of 2 • Review and Test the Work of Developers, Designers, Engineers, and Other Subcontractors
    Sean P. Reiser (347) 321-4338 37-14 192nd Street, Apt 173 [email protected] Flushing, NY 11358 https://seanreiser.com PROFESSIONAL BIOGRAPHY I am an information technologist with over 30 years experience in application and web development. Over the past 15 years I’ve been a Drupalist: building, supporting, managing, and maintaining over 150 websites for Non-Profits, Small Businesses, Digital Agencies, Media Companies and Startups. As a freelancer, I assume a number of roles in my work including: Project Manager, Web Producer, Strategist, Architect, Developer, Themer, Data Architect, Site Builder, and Support Engineer. I am proficient in leading internal or external development teams, liaising with contractors and managing client relationships. SKILLS Drupal - Drupal Versions (4 through 9), Site Building, Responsive Theming, Module Development, Views, Entity API, Forms API, Migrate API, Configuration API, RESTful Web Services API, Paragraphs, Layout Builder, Pantheon, Drupal Administration, Maintenance and Support Web Development - PHP 5/7, TWIG, PHPTemplate, HTML, Javascript, jQuery, CSS, LESS, YML, Bootstrap, Google Analytics Website Infrastructure Management -Linux, Apache, MySql, MariaDB, Varnish, Memcache, Redis, Apache, NGINX, SOLR, Bash, Pantheon, Linode, Cloudflare Project Management - Agile, Waterfall, Scrum, Training, Mentoring, Code Review, Performance Review,Full Project Lifecycle, Requirements Gathering, Use Cases, Build vs. Buy Legacy Technology - Clipper, FoxPro, dBase, Harbour, xHarbour, xBase++, Delphi, Flagship DRUPAL EXPERIENCE Bitmasonry, Inc Small Business Owner / Consultant / Contractor / Drupalist 2006 - Present • Build, support, maintain and manage over 150 websites. Major assignments include: The National Committee on US-China Relations, Pfizer, PBS, Mrs Dash, Bravo TV, Sage Realty, and the Queens Library. • Manage the day to day logistics of web projects.
    [Show full text]
  • Database Performance on AIX in DB2 UDB and Oracle Environments
    Database Performance on AIX in DB2 UDB and Oracle Environments Nigel Griffiths, James Chandler, João Marcos Costa de Souza, Gerhard Müller, Diana Gfroerer International Technical Support Organization www.redbooks.ibm.com SG24-5511-00 SG24-5511-00 International Technical Support Organization Database Performance on AIX in DB2 UDB and Oracle Environments December 1999 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix E, “Special notices” on page 411. First Edition (December 1999) This edition applies to Version 6.1 of DB2 Universal Database - Enterprise Edition, referred to as DB2 UDB; Version 7 of Oracle Enterprise Edition and Release 8.1.5 of Oracle8i Enterprise Edition, referred to as Oracle; for use with AIX Version 4.3.3. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 003 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1999. All rights reserved. Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface...................................................xv How this book is organized .......................................xv The team that wrote this redbook. ..................................xvi Commentswelcome.............................................xix Chapter 1. Introduction to this redbook .........................1 Part 1. RDBMS concepts .................................................3 Chapter 2. Introduction into relational database system concepts....5 2.1WhatisanRDBMS?.......................................5 2.2 What does an RDBMS provide? .
    [Show full text]
  • A Fast, Yet Lightweight, Indexing Scheme for Modern Database Systems
    Two Birds, One Stone: A Fast, yet Lightweight, Indexing Scheme for Modern Database Systems 1Jia Yu 2Mohamed Sarwat School of Computing, Informatics, and Decision Systems Engineering Arizona State University, 699 S. Mill Avenue, Tempe, AZ [email protected], [email protected] ABSTRACT Table 1: Index overhead and storage dollar cost Classic database indexes (e.g., B+-Tree), though speed up + queries, suffer from two main drawbacks: (1) An index usu- (a) B -Tree overhead ally yields 5% to 15% additional storage overhead which re- TPC-H Index size Initialization time Insertion time sults in non-ignorable dollar cost in big data scenarios espe- 2GB 0.25 GB 30 sec 10 sec cially when deployed on modern storage devices. (2) Main- 20 GB 2.51 GB 500 sec 1180 sec taining an index incurs high latency because the DBMS has 200 GB 25 GB 8000 sec 42000 sec to locate and update those index pages affected by the un- derlying table changes. This paper proposes Hippo a fast, (b) Storage dollar cost yet scalable, database indexing approach. It significantly HDD EnterpriseHDD SSD EnterpriseSSD shrinks the index storage and mitigates maintenance over- 0.04 $/GB 0.1 $/GB 0.5 $/GB 1.4 $/GB head without compromising much on the query execution performance. Hippo stores disk page ranges instead of tuple pointers in the indexed table to reduce the storage space oc- table. Even though classic database indexes improve the cupied by the index. It maintains simplified histograms that query response time, they face the following challenges: represent the data distribution and adopts a page group- ing technique that groups contiguous pages into page ranges • Indexing Overhead: Adatabaseindexusually based on the similarity of their index key attribute distri- yields 5% to 15% additional storage overhead.
    [Show full text]
  • A Database Optimization Strategy for Massive Data Based Information System
    Advances in Computer Science Research, volume 93 2nd International Conference on Mathematics, Modeling and Simulation Technologies and Applications (MMSTA 2019) A Database Optimization Strategy for Massive Data Based Information System Qianglai Xie*, Wei Yang and Leiyue Yao Jiangxi University of Technology, China *Corresponding author Abstract—With the rapid arrival of the information support technology for the physical design of the entire explosion era, the amount of data stored in a single table of an database, and the method of range partitioning is mainly used enterprise information management system is getting more and in the SQL Sever databases design [6][7]. more common. Therefore, efficiency optimization of SQL based on the massive data is an essential task to break the bottleneck in The index of the database table structure is an important current enterprise information management systems. This paper factor affecting the database performance. Establishing a proposes single table optimization methods for massive database. reasonable index on the basis of physical optimization will These methods including: physical optimization, index directly affect the efficiency of the entire database access [8,9]. optimization and query statement optimization. Each The pages of SQL server data storage include two types: data optimization method is integrated into the database design pages and index pages. By default, data exists in the data pages, process, and a set of optimization programs for the massive but as long as the index data exists, the indexes will be database design process is proposed. In the test environment, the automatically stored in the index page [10,11]. The index types size of the databases file is over 200G and single table records is include: clustered and non-clustered indexes.
    [Show full text]
  • What Is New in Pdgender 2.0?
    WHAT IS NEW IN PDGENDER 2.0? Male and female identification is essential for businesses and organizations. It allows you to send mail with a personal touch. Gender Coding also allows you to filter, map, and analyze your data based on this critical demographic. The new pdGender 2.0 lets you accomplish this in ways not before possible on this scale. A one-of-a-kind proprietary resource developed and tested in the field over more than 20 years, this package contains a large set of English, Spanish, and international first names and nicknames covering more than 200 languages along with a host of additional features. The full system even incorporates sophisticated fuzzy logic. But what makes this gender coding database truly different are twenty gender coding fields filtered for languages, rare usage by one gender, and other criteria. When a name is one gender in Chinese and another in English, users can have the English identification applied. When a unisex name like Kimberly is called up, users can have the much more common feminine form applied. In addition to its value for businesses and organizations working with lists of names, this product is also fully suitable for students, teachers, and researchers working in the fields of anthroponymy, onomatology, ethnology, linguistics, and related areas. pdGender is available in Pro and Standard editions. PRO EDITION The Pro edition includes over 140,000 gender coding records with name type, origin, and languages of use, plus a sophisticated system of fuzzy logic allowing matches when there are typographical errors or special spelling methods are utilized.
    [Show full text]
  • Introduction to Database Design 1 Indexing
    Introduction to Database Design 1 Indexing RG 8.1, 8.2, 8.3, 8.5 Rasmus Pagh Introduction to Database Design 2 Disk crash course • Relations of large databases are usually stored on hard drives (or SSDs). • Hard drives can store large amounts of data, but work rather slowly compared to the memory of a modern computer: • The time to access a specific piece of data is on the order of 106 (104) times slower. • The rate at which data can be read is on the order of 100 (10) times slower. • Time for accessing disk may be the main performance bottleneck! Introduction to Database Design 3 Parallel data access • Large database systems (and modern SSDs) use several storage units to: – Enable several pieces of data to be fetched in parallel. – Increase the total rate of data from disk. • Systems of several disks are often arranged in so-called RAID systems, with various levels of error resilience. • Even in systems with this kind of parallelism, the time used for accessing data is often the performance bottleneck. Introduction to Database Design 4 Full table scans When a DBMS sees a query of the form !SELECT *! !FROM R! !WHERE <condition>! the obvious thing to do is read through the tuples of R and report those tuples that satisfy the condition. This is called a full table scan. Introduction to Database Design 5 Selective queries Consider the query from before • If we have to report 80% of the tuples in R, it makes sense to do a full table scan. • On the other hand, if the query is very selective, and returns just a small percentage of the tuples, we might hope to do better.
    [Show full text]