DOCSLIB.ORG

DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2017 Copyright Notice ©2016 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Testing SQL Statements 22 Who Should Read this Guide 1 Error Handling 23 Requirements 1 Chapter 5: Customizing SQL Components 24 Supplied Database Drivers 1 Dynamic SQL Using String Replacement 24 Additional Information 2 Chapter 6: Building Protocols with Multiple Chapter 2: Configuring a Database 3 SQL Components 26 Overview 3 Chapter 7: Calling Database Stored Procedures 27 Pipeline Pilot Data Sources 3 Oracle Stored Procedures 27 Configuring Data Sources 4 Simple Stored Procedure 27 ODBC (PP) Data Sources 5 Simple Function 29 JDBC Data Sources 5 Stored Procedure with Result Sets 29 ODBC (DSN) Data Sources 5 Microsoft SQL Server Stored Procedures 32 MongoDB Data Sources 5 Simple Function 32 Connection Pooling 6 Stored Procedure with Result Sets 33 Configuring Data Source Access Rights 6 MySQL Stored Procedures 35 Authentication 6 Simple Stored Procedure 35 Initializing the Connection 7 Simple Function 37 Additional Information 7 Stored Procedure with Result Sets 37 Query Service Settings 7 Identifying Result Sets 39 Testing Data Source Connections 7 Appendices 41 Configuring an ODBC Data Source on the Server 7 Appendix A: ODBC Server Configuration 41 Support for Molecular Databases 8 Configuring an ODBC Data Source on Linux 44 Remote Access Files 8 Appendix B: Using dates with Oracle based components 45 Chapter 3: SQL Components Overview 9 Database Access 9 SQL Component Parameters 10 Parameter Mapping 10 Selecting a Data Source 12 Sharing SQL Component Connections 13 Batch Size 13 Handling of Date Values 14 Data Source Access Rights 14 Examples 14 View Data Source Rights 15 Use Data Source Rights 16 None Rights 17 Chapter 4: Building SQL Statements 19 Opening the SQL Builder 19 SQL Editing Modes 19 Graphically Building SQL Statements 20 Manually Constructing SQL Statements 21 SQL Editing Guidelines 21 Creating a Data Table 22 Chapter 1: Introduction The Pipeline Pilot Integration collection includes a set of components designed for use with Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers. These drivers allow connections to a variety of compliant databases such as Oracle, SQL Server, and MS Access that reside anywhere on the network. Network databases can be accessed through the SQL components and configured on the server. Connections to these data sources are defined through the Pipeline Pilot Administration Portal. All information for the data source can be specified in the Administration Portal (including the necessary login and password) or this information can be provided from Data Service Names (DSNs) that are defined on the server using the ODBC Administrator tool. Who Should Read this Guide This guide provides information for integrating the SQL components with relational databases. This first chapter explains how to configure a Pipeline Pilot data source on your server (for administrators). The remaining chapters explain how to use SQL components to access data sources on your network (for client users). Requirements To configure an Pipeline Pilot data source, the Administration Portal role must be assigned to you. When using ODBC DSNs to specify the database information, you also need administrator privileges on the Pipeline Pilot server. To use the SQL components, you need some experience writing structured query statements. You also need a valid login and password to access the databases on your network. Supplied Database Drivers ODBC drivers from DataDirect are included with your Pipeline Pilot server installation. These drivers support connections to Oracle, Microsoft SQLServer, MySQL1 and DB2. These DataDirect drivers support faster access using a wire protocol and portability across platforms. No additional drivers or database software needs to be installed by administrators to let Pipeline Pilot communicate with databases using these drivers. In addition, Pipeline Pilot ships with a version of the Oracle JDBC driver for connecting to Oracle databases. To access other ODBC databases, install the appropriate driver on the server and create a DSN. To access other JDBC databases, install the appropriate driver jar file through the Administration Portal and configure the Data Source. Introduction | Page 1 Notes: Pipeline Pilot only officially supports the DataDirect drivers included with your product installation, although other drivers might continue to work. For full compatibility, use the DataDirect drivers for Pipeline Pilot. From the Pipeline Pilot Home Page, you can access documentation for Data Direct drivers that ship with Pipeline Pilot (select the "ODBC Driver Help" link in the Administrators section). Pipeline Pilot Clients cannot query a Microsoft Access database if your server runs on Linux. To use the installed drivers, you need to set up a new Data Source through the Administration Portal. Each Data Source maps a driver to a particular database on your network. Once a data source is defined, it is automatically displayed in Pipeline Pilot's Data Source dialog, allowing you to configure SQL components to read from that particular database. The Oracle ODBC driver from Data Direct does not support reading LOB data from tables which use SECUREFILE storage. If you have LOB data stored in tables that use SECUREFILE storage, you can read it using the supplied Oracle JDBC driver or you can install a different ODBC driver, such as Oracle's own ODBC driver. In the case of an updated ODBC driver on the Linux platform, the included driver replaces your existing version. On Windows you will have the option of continuing to use the previous version. See release notes for more details. In addition, you could use a custom ODBC DSN or a JDBC driver to connect to the database instead of using the latest Data Direct driver. 1The DataDirect drivers only work with the commercial version of MySQL. To connect to the community edition, use a MySQL-provided ODBC or JDBC driver. Additional Information For more information about the Pipeline Pilot Integration collection and other BIOVIA software products, visit https://community.3dsbiovia.com. Page 2 | Pipeline Pilot • Database Integration Guide Chapter 2: Configuring a Database Overview The Pipeline Pilot server can access databases that are ODBC or JDBC compliant (for example, Oracle and SQL Server). It can also read molecular data from ISIS and AEI databases. The server accesses these databases through a standard ODBC or JDBC layer. To communicate with the database, the ODBC layer uses an ODBC driver specific to the database type that is in use (such as, Oracle, DB2, etc.). Database configuration involves installing and configuring the appropriate driver on the server machine. The following diagram illustrates how the server communicates with an Oracle database using a JDBC driver: Pipeline Pilot communication with a database Protocols are edited on the client systems and protocol jobs run on the server. Therefore, the connection is made to a database source from the server. The server is the only machine that needs to be configured to communicate with the database. The client machines do not require configuration. To use the Pipeline Pilot ODBC or JDBC drivers, no additional installation is required. To use another ODBC driver, install the driver on the Pipeline Pilot server. To use a different JDBC driver, use the Administration Portal to upload the jar file to the server. Pipeline Pilot Data Sources To communicate with the database, a driver needs configuration information, such as server name, username, etc. This information is provided when the data sources are configured in the Administration Portal. If a data source has been configured by the Administrator, a user can select this data source on a SQL component in a protocol if the administrator has given the user access to the data source. When the protocol runs, the SQL component accesses the configuration of the data sources, passes this information to the driver software, and makes a connection to the database. The SQL component can then execute commands and retrieve information from this database. You can configure the following types of data source connections for use with Pipeline Pilot's SQL components: ODBC (DSN): ODBC-compliant databases that you configure to work with your own drivers that you install on the Pipeline Pilot server. For example, create a DSN to reference a Microsoft Access database. The data source includes all the information required to connect to the database, or it references the name of an ODBC DSN separately configured on the server. ODBC (PP): Data sources that use Pipeline Pilot's Data Direct drivers. JDBC: JDBC-compliant data sources that use driver JAR files that you install on the Pipeline Pilot server. Configuring a Database | Page 3 MongoDB: Mongo data sources defined in the Admin Portal. Tip: You can also store the username and password with the data source. This is convenient because this information does not need to be specified on each SQL component that uses the data source.
Recommended publications
  • Documents and Attachments 57 Chapter 7: Dbamp Stored Procedure Reference

    Documents and Attachments 57 Chapter 7: Dbamp Stored Procedure Reference

    CData Software, Inc. DBAmp SQL Server Integration with Salesforce.com Version 5.1.6 Copyright © 2021 CData Software, Inc. All rights reserved. Table of Contents Acknowledgments ........................................................................... 7 Chapter 1: Installation/Upgrading ................................................. 8 Upgrading an existing installation ......................................................... 8 Prerequistes ....................................................................................... 9 Running the DBAmp installation file...................................................... 9 Configure the DBAmp provider options ................................................. 9 Connecting DBAmp to SQL Server ...................................................... 10 Verifying the linked server ................................................................. 11 Install the DBAmp Stored Procedures ................................................. 11 Running the DBAmp Configuration Program........................................ 11 Setting up the DBAmp Work Directory ................................................ 12 Enabling xp_cmdshell for DBAmp ....................................................... 13 Pointing DBAmp to your Salesforce Sandbox Instance ......................... 13 Chapter 2: Using DBAMP as a Linked Server ................................ 14 Four Part Object Names .................................................................... 14 SQL versus SOQL .............................................................................
  • Declare Syntax in Pl Sql

    Declare Syntax in Pl Sql

    Declare Syntax In Pl Sql NickieIs Pierre perennates desecrated some or constant stunner afterafter pomiferousprojectional Sydney Alberto appreciatingconfabulate mourningly.so Jewishly? Abused Gordan masons, his hakim barged fasts reparably. Encircled It could write utility it an sql in the original session state in turn off timing command line if it needs to learn about oracle Berkeley electronic form, and os commands, declare syntax in pl sql syntax shows how odi can execute. To select in response times when it declares an assignment statement to change each actual parameter can be open in a declarative part. Sql functions run on a timing vulnerabilities when running oracle pl sql syntax shows how use? To learn how to performance overhead of an object changes made to explain plan chooses by create applications. Have an archaic law that declare subprograms, declaring variables declared collection of declarations and return result set cookies that references or distinct or script? Plus statements that column, it is not oracle pl sql syntax shows no errors have a nested blocks or a recordset. Always nice the highest purity level line a subprogram allows. The script creates the Oracle system parameters, though reception can be changed by the inactive program. If necessary to declare that are declared in trailing spaces cause a declarative part at precompile time. This syntax defines cursors declared in oracle pl sql. Run on that subprograms as columns and you use a variable must be recompiled at any syntax defines cursors. All procedures move forward references to it is executed at runtime engine runs for this frees memory than store.
  • Perl DBI API Reference

    Perl DBI API Reference

    H Perl DBI API Reference This appendix describes the Perl DBI application programming interface. The API consists of a set of methods and attributes for communicating with database servers and accessing databases from Perl scripts. The appendix also describes MySQL-specific extensions to DBI provided by DBD::mysql, the MySQL database driver. I assume here a minimum version of DBI 1.50, although most of the material applies to earlier versions as well. DBI 1.50 requires at least Perl 5.6.0 (with 5.6.1 preferred). As of DBI 1.611, the minimum Perl version is 5.8.1. I also assume a minimum version of DBD::mysql 4.00. To determine your versions of DBI and DBD::mysql (assuming that they are installed), run this program: #!/usr/bin/perl # dbi-version.pl - display DBI and DBD::mysql versions use DBI; print "DBI::VERSION: $DBI::VERSION\n"; use DBD::mysql; print "DBD::mysql::VERSION: $DBD::mysql::VERSION\n"; If you need to install the DBI software, see Appendix A , “Software Required to Use This Book.” Some DBI methods and attributes are not discussed here, either because they do not apply to MySQL or because they are experimental methods that may change as they are developed or may even be dropped. Some MySQL-specific DBD methods are not discussed because they are obsolete. For more information about new or obsolete methods, see the DBI or DBD::mysql documentation, available at http://dbi.perl.org or by running the following commands: % perldoc DBI % perldoc DBI::FAQ % perldoc DBD::mysql The examples in this appendix are only brief code fragments.
  • Operation in Xql______34 4.5 Well-Formedness Rules of Xql ______36 4.6 Summary ______42

    Operation in Xql______34 4.5 Well-Formedness Rules of Xql ______36 4.6 Summary ______42

    Translation of OCL Invariants into SQL:99 Integrity Constraints Master Thesis Submitted by: Veronica N. Tedjasukmana [email protected] Information and Media Technologies Matriculation Number: 29039 Supervised by: Prof. Dr. Ralf MÖLLER STS - TUHH Prof. Dr. Helmut WEBERPALS Institut für Rechnertechnologie – TUHH M.Sc. Miguel GARCIA STS - TUHH Hamburg, Germany 31 August 2006 Declaration I declare that: this work has been prepared by myself, all literally or content-related quotations from other sources are clearly pointed out, and no other sources or aids than the ones that are declared are used. Hamburg, 31 August 2006 Veronica N. Tedjasukmana i Table of Contents Declaration __________________________________________________________________ i Table of Contents _____________________________________________________________ ii 1 Introduction ______________________________________________________________ 1 1.1 Motivation _____________________________________________________________ 1 1.2 Objective ______________________________________________________________ 2 1.3 Structure of the Work ____________________________________________________ 2 2 Constraint Languages ______________________________________________________ 3 2.1 Defining Constraint in OCL _______________________________________________ 3 2.1.1 Types of Constraints ________________________________________________ 4 2.2 Defining Constraints in Database ___________________________________________ 4 2.3 Comparison of Constraint Language_________________________________________
  • DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice

    DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice

    DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice ©2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Testing SQL Statements 22 Who Should Read this Guide 1 Error Handling 23 Requirements 1 Chapter 5: Customizing SQL Components 24 Supplied Database Drivers 1 Dynamic SQL Using String Replacement 24 Additional Information 2 Chapter 6: Building Protocols with Multiple Chapter 2: Configuring
  • Using Proc SQL and ODBC to Manage Data Outside of SAS® Jeff Magouirk, National Jewish Medical and Research Center, Denver, Colorado

    Using Proc SQL and ODBC to Manage Data Outside of SAS® Jeff Magouirk, National Jewish Medical and Research Center, Denver, Colorado

    Using Proc SQL and ODBC to Manage Data outside of SAS® Jeff Magouirk, National Jewish Medical and Research Center, Denver, Colorado ABSTRACT The ability to use Proc SQL and ODBC to manage data outside of SAS is another feature in SAS’s toolbox that programmers use to accomplish many different tasks. The idea of pulling data from sources outside of SAS is behind both of these tools. A key benefit of using ODBC and to a certain amount Proc SQL is the reduction in coding that is written. Another positive aspect of using Proc SQL and ODBC is the ability to manage data across a network. At National Jewish Medical & Research Center ODBC and Proc SQL are used to manage and pull end users data across networks so users can examine their data quickly and efficiently. Since end users can have almost real time access to the collected data it is especially useful for checking the accuracy of the data from patient health studies and clinical trials. Error checks and data handling are done first as the data is collected and put into data tables with SAS and then outputted either with an ODBC connection or Proc SQL. The purpose of this paper is to show users how to set up an ODBC connection, compare the reduction in code when an ODBC is set up and how to use Proc SQL to manage data outside of SAS. INTRODUCTION Open Database Connectivity (ODBC) is an Application Programming Interface (API) that allows a programmer to access data from database management system with a non-native application.
  • Developing Embedded SQL Applications

    Developing Embedded SQL Applications

    IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 IBM DB2 10.1 for Linux, UNIX, and Windows Developing Embedded SQL Applications SC27-3874-00 Note Before using this information and the product it supports, read the general information under Appendix B, “Notices,” on page 209. Edition Notice This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at http://www.ibm.com/shop/publications/ order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at http://www.ibm.com/ planetwide/ To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1993, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Introduction to embedded Include files for COBOL embedded SQL SQL................1 applications .............29 Embedding SQL statements
  • Oracle HTML DB User's Guide Describes How to Use the Oracle HTML DB Development Environment to Build and Deploy Database-Centric Web Applications

    Oracle HTML DB User's Guide Describes How to Use the Oracle HTML DB Development Environment to Build and Deploy Database-Centric Web Applications

    Oracle® HTML DB User’s Guide Release 1.6 Part No. B14303-02 March 2005 Oracle HTML DB User’s Guide, Release 1.6 Part No. B14303-02 Copyright © 2003, 2005, Oracle. All rights reserved. Primary Author: Terri Winters Contributors: Carl Backstrom, Christina Cho, Michael Hichwa Joel Kallman, Sharon Kennedy, Syme Kutz, Sergio Leunissen, Raj Mattamal, Tyler Muth, Kris Rice, Marc Sewtz, Scott Spadafore, Scott Spendolini, and Jason Straub The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
  • Database Language SQL: Integrator of CALS Data Repositories

    Database Language SQL: Integrator of CALS Data Repositories

    Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 NIST Database Language SQL Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 September 1992 U.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary TECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan National Institute of Standards and Technology Information Systems Engineering Division Gaithersburg, MD 20899, USA CALS Status Report on SQL and RDA - Abstract - The Computer-aided Acquisition and Logistic Support (CALS) program of the U.S. Department of Defense requires a logically integrated database of diverse data, (e.g., documents, graphics, alphanumeric records, complex objects, images, voice, video) stored in geographically separated data banks under the management and control of heterogeneous data management systems. An over-riding requirement is that these various data managers be able to communicate with each other and provide shared access to data and
  • The Progress Datadirect for ODBC for SQL Server Wire Protocol User's Guide and Reference

    The Progress Datadirect for ODBC for SQL Server Wire Protocol User's Guide and Reference

    The Progress DataDirect® for ODBC for SQL Server™ Wire Protocol User©s Guide and Reference Release 8.0.2 Copyright © 2020 Progress Software Corporation and/or one of its subsidiaries or affiliates. All rights reserved. These materials and all Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change. Corticon, DataDirect (and design), DataDirect Cloud, DataDirect Connect, DataDirect Connect64, DataDirect XML Converters, DataDirect XQuery, DataRPM, Defrag This, Deliver More Than Expected, Icenium, Ipswitch, iMacros, Kendo UI, Kinvey, MessageWay, MOVEit, NativeChat, NativeScript, OpenEdge, Powered by Progress, Progress, Progress Software Developers Network, SequeLink, Sitefinity (and Design), Sitefinity, SpeedScript, Stylus Studio, TeamPulse, Telerik, Telerik (and Design), Test Studio, WebSpeed, WhatsConfigured, WhatsConnected, WhatsUp, and WS_FTP are registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries. Analytics360, AppServer, BusinessEdge, DataDirect Autonomous REST Connector, DataDirect Spy, SupportLink, DevCraft, Fiddler, iMail, JustAssembly, JustDecompile, JustMock, NativeScript Sidekick, OpenAccess, ProDataSet, Progress Results, Progress Software, ProVision, PSE Pro, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, and WebClient are trademarks or service marks of Progress Software Corporation and/or its subsidiaries or affiliates in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates. Any other marks contained herein may be trademarks of their respective owners.
  • Step by Step Guide: Connecting to Mysql with SAP Crystal Reports 2016 © 2019 SAP AG Or an SAP SAP Allag Or Rightsaffiliate© Company

    Step by Step Guide: Connecting to Mysql with SAP Crystal Reports 2016 © 2019 SAP AG Or an SAP SAP Allag Or Rightsaffiliate© Company

    SAP Crystal Solutions SAP Crystal Reports and SAP Crystal Server Step by Step guide: Connecting to MySQL With SAP Crystal Reports 2016 © 2019 SAP AG or an SAP SAP AllAG or affiliate rights© company. reserved. SAP an 2019 Because of its open source roots, the MySQL database platform is used in many types of applications. Now provided under the umbrella of Oracle corporation as both paid and free products, MySQL can be the source for many types of SAP Crystal Reports projects. Reporting from a MySQL database requires two general preparation steps: * Download and install the MySQL ODBC database driver. * Create an ODBC Data Source. DOWNLOADING A MySQL DRIVER SAP Crystal Reports won’t recognize a MySQL database “out of the box.” You must first download and install a MySQL driver to connect Crystal Reports to the database. While there are many sources for MySQL drivers found in an Internet search, you’ll typically find current drivers at Oracle’s MySQL.com site. You may find options to download individual drivers one at a time, or an all-encompassing installation program that permits you to choose a combination of drivers from a single installation process. Unless you are planning on using multiple components of MySQL products (perhaps installing your own database server, in addition to a driver for Crystal Reports), you’ll probably only need to download the desired ODBC driver. IMPORTANT: Remember that, despite the strong possibility that you are running a 64-bit version of Microsoft Windows, SAP Crystal Reports is a 32-bit application and will only recognize 32-bit database drivers.
  • Essbase SQL Interface Guide, 9.3.1 Copyright © 1998, 2007, Oracle And/Or Its Affiliates

    Essbase SQL Interface Guide, 9.3.1 Copyright © 1998, 2007, Oracle And/Or Its Affiliates

    HYPERION® ESSBASE® – SYSTEM 9 RELEASE 9.3.1 SQL INTERFACE GUIDE Essbase SQL Interface Guide, 9.3.1 Copyright © 1998, 2007, Oracle and/or its affiliates. All rights reserved. Authors: Rosemary Peters The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987).