DOCSLIB.ORG

Extending the Data Warehouse: an Introduction to OLE DB

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Extending the Data Warehouse: an Introduction to OLE DB Extending the Data Warehouse: An Introduction to OLE DB S David Rlba, JADE Tech Inc CleaNlater, FL INTRODUCTION In 1995, I first presented ODBC: Windows to the Outside World, an introduction to the topiC of Open DataBase Connectivity and how to use it effectively. Since then, ODBC has become a useful tool for many SAS sites for cross application access to data. ABSTRACT However, OOBC has its limitations. To address these limitations, and to provide a more flexible Now that you have your data warehoused, how do means of access to many different types of data, you share that infonnation with others who need Microsoft proposed a new standard for data access access to it? SA~ software provides a variety of technology, OLE DB. tools to access and retrieve data from multidimensional databases (MDDBs). However, At SUGI 24, Thomas Cox presented What's Up with MDDBs are not accessible to non-SAS users in your OLE DB?, which provides an excellent overview of organization. Until now. Starting with Version 7 of OLE DB architecture and concepts. This paper will the SAS System, OLE DB can be used to access attempt to provide some additional background on the infonnation stored in SAS MDDBs and eFO OLE DB, and present some techniques for using Vision FOBs. OLE DB to access both SAS and non-SAS data. OLE DB can be used to access the infonnation WHAT IS WRONG WITH ODSC? stored in ANY multidimensional database that is OLE DB compliant. Starting with the release of ODBe was originally proposed by Microsoft in the Windows 2000 Professional, OLE DB will be early 1990's to solve the problem of accessing installed as part of the operating system. In relational and tabular data on the Microsoft Microsoft Office 2000, all member applications will Windows!!) platfonn. It subsequently was ported to be OLE DB consumers. The same is true for Lotus other platfonns and is now a universal method to SmartSulte member applications. Thus, any OLE share data between non-compatible applications on DB compliant consumer (such as Microsoft Excel, a wide variety of hardware platfonns. Lotus 1-2-3, Knosys ProClarity, and many others) will be able to directly query a SAS MDDB file using The ODBe architecture consisted of four tiers: OLE DB on all major platfonns, including Windows NT, UNIX, and mainframes. { ODBC Driver Manager { ODBe Drivers { Applications This paper will provide an introduction to OLE DB. It { Data Sources defined to ODse will describe OLE DB and how it works. The SAS implementation of OLE DB will be demonstrated, The OOBC Driver Manager is typically supplied by along with other OLE DB consumers such as the operating system vendor (e.g. Microsoft). Microsoft Excel and Lotus 1-2-3. The paper is intended as a beginning paper for the advanced OOBC Drivers are typically supplied by the vendor of user. a specific type of data to be accessed with ODBC (e.g. Oracle, SAS, Lotus, etc.). Data Sources are defined by the end user to identify a speCific type of data to be read or written. However, there are several limitations that affect the use of ODBC. These limitations include: 15 { OOSC uses Sal as the common components, which process and transport data language (for example, query processors and cursor { ODBC Olivers are written to different engines). These components are designed to levels integrate smoothly to help OLE OS component { Oeployment issues vendors quickly bling high-quality OLE OS components to market. OLE OS includes a Since OOSC is based on Sal as the common bridge to OOSC to enable continued support for language for communicating between different types the broad range of OOSC relational database of data, the structure of Sal limits the types of data drivers available today. that can be accessed. Sal is best at accessing relational and tabular data. Sal can not be used OLE DB is intended to be an open standard capable effectively to access hierarchical, multi-dimensional of providing access to any type of data. As such, (MOOS), and free-form data. In addition, there are OLE DB will be useful for: many different interpretations of the SQl language, with differing levels of conformance to the Sal { Relational Data specifications. This can cause problems when trying { MultiDimensional Data (MODS) to construct a Sal query for OOSC. { Non-Relational Data { E-Mail OOSC Olivers are individual OlLs written by { Web Data different software vendors to support their specific { Oirectory Services data structures. However, the OOBC standard { IMS and VSAM data specifies several different levels of OOBC compliance, Core, level 1, and level 2. .Each Since OLE DB is an object oriented interface to OOBC dliver is written to one of these compliance data it is intended for use in thin client (web based) levels based on the features that they support. envi;onments. With OLE DB many different types of data can be accessed in a common manner using Oeployment of OOSC has been a problem at many web browsers, database software, stand alone sites. In order for OOSC to function properly, the applications, etc. server operating system, network transport, client softwa~e, and drivers must all be compatible. If this does not happen, troubleshooting OOBC problems IS OOBC OBSOLETE? can be extremely difficult. In many respects, OLE DB can be considered a superset to OoBC. OLE DB incluC!es all of the WHAT IS OLE DB? functionality of OOBC, adds additional functionality, and is easier to use. In fact, OLE OB ships with an In the Summer of 1996, Microsoft published the first OOBC Provider (more on this later). Thus, OLE DB specifications for OLE OB (Object Unking and can perform all of the functionality previously Embedding for DataBases). OLE OB was intended performed by OOBC, with the additional capabilities to overcome the limitations that had become built into OLE DB. apparent in OOSC. However, OLE DB is not intended to replace OOBC. According to Microsoft: The OOBC technology has matured and is widely used. OOBe is still the best choice when accessing OLE OB is an open specification designed to standard relational databases from a non-OLE build on the success of OOSC by providing an environment. OLE DB is still an evolving standard. open standard for accessing all kinds of data It is important to realize that Microsoft is fully throughout the enterprise. OLE OS is a core integrating OLE DB Into its product line (operating technology supporting universal data access. systems and Office suite) as their solution for Whereas oose was created to access relational universal data access. In addition, other vendors databases, OLE OS is designed for the relational such as SAS Institute are adopting OLE DB as a and nonrelational information sources, such as standard for extemal data access. mail stores, text and graphical data for the Web, directory services, and 'IMS and VSAM data In deciding whether to use OoBe or OLE DB, here stored in the mainframe. OLE OB components are some recommendations: consist of data providers, which expose data; data consumers, which use data; and service 16 { Use ODBC to access standaro relational OLE DB for DATA MINING databases from a non-OLE environment { Use OLE DB for non-SQl data In February, 2000, Microsoft updated a draft of a { Use OLE DB in an OLE environment specification for OLE DB for Data Mining. The { OLE DB is the only option for building specification is currently at Version 0.9. In interoperable database components (COM) cooperation with over 40 vendors in the business intelligence field, the OLE DB for OM specification defines a common interface for data mining UNDERSTANDING OLE DB applications. The goal of this specification is to provide an industry standaro for data mining so that Technologically, there is a fundamental difference in different data mining algorithms from various data the architectures of OOBC and OLE DB. mining vendors can be easily plugged into user applications. { ODBC is a procedural based specification OLE DB for OM specifies the API between data { OLE DB is a component based mining consumers and data mining providers. The specification specification does not add any new OLE DB { OOBC is designed to provide access interfaces. Instead, the specification defines a primarily to relational data using SQl in a simple query language similar to SQl syntax and multiplatfonn environment. specialized schema rowsets so consumer { OLE DB is designed to provide access to applications can communicate with data mining all types of data in an OLE Component providers. Object Model (COM) environment. like OLE DB, this area is still evolving and maturing. OLE DB includes the Structured Query language The OLE DB for OM speCification is currently in (SQl) functionality defined in OOBC, but it also public beta. However, the potential benefits from defines interfaces suitable for gaining access to data OLE DB for Data Mining are significant. other than SQl data. OLE DB Is intended to be an open standard capable of providing access to any type of data. In addition, OLE DB for OLAP (OnUne PROVIDERS AND CONSUMERS Analytical Processing) is Intended to extend the features of OLE DB to OLAP data. OLE DB introduces two new terms to the computer lexicon - ·provider" and ·consumer". These tenns Microsoft intended OLE DB to be the foundation of refer to the application software and how they their Universal Data Access strategy. To accomplish interact with OLE DB. this, OLE DB is tightly coupled with ADO (ActiveX Data Objects). ADO is the application level interface { Providers are applications that implement (API) that provides the Component Object Model OLE DB interfaces (COM) objects.
Load more

Recommended publications
  • Middleware in Action 2007
    Technology Assessment from Ken North Computing, LLC Middleware in Action Industrial Strength Data Access May 2007 Middleware in Action: Industrial Strength Data Access Table of Contents 1.0 Introduction ............................................................................................................. 2 Mature Technology .........................................................................................................3 Scalability, Interoperability, High Availability ...................................................................5 Components, XML and Services-Oriented Architecture..................................................6 Best-of-Breed Middleware...............................................................................................7 Pay Now or Pay Later .....................................................................................................7 2.0 Architectures for Distributed Computing.................................................................. 8 2.1 Leveraging Infrastructure ........................................................................................ 8 2.2 Multi-Tier, N-Tier Architecture ................................................................................. 9 2.3 Persistence, Client-Server Databases, Distributed Data ....................................... 10 Client-Server SQL Processing ......................................................................................10 Client Libraries ..............................................................................................................
    [Show full text]
  • Comparing OLE DB and ODBC This Document Compares the Basic Features of OLE DB to the Basic Features of ODBC (Open Database Connectivity)
    Comparing OLE DB and ODBC This document compares the basic features of OLE DB to the basic features of ODBC (Open Database Connectivity). It is intended to help clarify when to use one over the other. Introduction OLE DB and ODBC are both specifications created by Microsoft to address universal data access. Each is intended as an industry standard that will make access between one vendor's data store and another vendor's data consumer seamless. Microsoft's definition of OLE DB is a strategic system-level programming interface to data across the organization. OLE DB is an open specification designed to build on the success of ODBC by providing an open standard for accessing all kinds of data. And the definition of ODBC is an industry standard and a component of Microsoft® Windows® Open Services Architecture (WOSA). The ODBC interface makes it possible for applications to access data from a variety of database management systems (DBMSs). ODBC permits maximum interoperability—an application can access data in diverse DBMSs through a single interface. Furthermore, that application will be independent of any DBMS from which it accesses data. Users of the application can add software components called drivers, which create an interface between an application and a specific DBMS. The two primary differences between the two are • OLE DB is a component based specification and ODBC is a procedural based specification • SQL is the core of accessing data using ODBC but just one of the means of data access through OLE DB • ODBC is constrained to relational data stores; OLE DB supports all forms of data stores (relational, hierarchical, etc) In general, OLE DB provides a richer and more flexible interface for data access because it is not tightly bound to a command syntax (like SQL in the case of ODBC).
    [Show full text]
  • Dot Net Programming CLASS: TYBBA(CA) V SEM (2013 PATTERN)
    DNYANSAGAR ARTS AND COMMERCE COLLEGE, BALEWADI, PUNE – 45 Subject: 503 : Dot Net Programming CLASS: TYBBA(CA) V SEM (2013 PATTERN) Unit 1 :Introduction to .Net Framework Introduction to .NET Framework .NET is a software framework which is designed and developed by Microsoft. The first version of the .Net framework was 1.0 which came in the year 2002. In easy words, it is a virtual machine for compiling and executing programs written in different languages like C#, VB.Net etc. It is used to develop Form-based applications, Web-based applications, and Web services. There is a variety of programming languages available on the .Net platform, VB.Net and C# being the most common ones. It is used to build applications for Windows, phone, web, etc. It provides a lot of functionalities and also supports industry standards. .NET Framework supports more than 60 programming languages in which 11 programming languages are designed and developed by Microsoft. The remaining Non-Microsoft Languages which are supported by .NET Framework but not designed and developed by Microsoft. Common Language Runtime(CLR): CLR is the basic and Virtual Machine component of the .NET Framework. It is the run-time environment in the .NET Framework that runs the codes and helps in making the development process easier by providing the various services such as remoting, thread management, type-safety, memory management, robustness, etc.. Basically, it is responsible for managing the execution of .NET programs regardless of any .NET programming language. It also helps in the management of code, as code that targets the runtime is known as the Managed Code and code doesn’t target to runtime is known as Unmanaged code.
    [Show full text]
  • Autocad 2008 驱动程序和外围设备手册
    <$nopage>: <$nopage>: <$nopage>, <$nopage>: <$nopage>: <$nopage><$nopage>, <$nopage> (DWT) :, <$nopage> (DWT) : , <$nopage> (DWT) :, <$nopage> (DWT) :, <$nopage>, <$nopage>, <$nopage>, <$nopage>: <$nopage>, <$nopage>, <$nopage>: <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>: , <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage> , <$nopage>: <$nopage>: <$nopage>:, <$nopage>:, <$nopage>:: <$nopage>, <$nopage> (UCS): <$nopage>: <$nopage>:, <$nopage>: , <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage> :, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage>:, <$nopage><$nopage>, <$nopage>:, <$nopage>, <$nopage>Intellimouse, AutoCAD 2008 > 10 1 AutoCAD 2008 > > > OPTIONS OPTIONS PAN ZOOM MBUTTONPAN SHORTCUTMENU ZOOMFACTOR AutoCAD 2008 > > > OPTIONS OPTIONS REINIT / TABLET TABMODE <$nopage>D3D <$nopage>OGL AutoCAD 2008 > AutoCAD AutoCAD AutoCAD OpenGL (OGL) Direct 3D (D3D) AutoCAD 2008 > > > 3DCONFIG AutoCAD 2008 > > > 3DCONFIG AutoCAD 2008 > HDIHeidi ® HDI HDI (PC3) PC3 “” PC3 “” PC3 “” (PC3) Windows “” AutoCAD 2008 > > > PLOT PLOTTERMANAGER “” AutoCAD 2008 > > > PAGESETUP PCINWIZARD PCP PC2 “” PLOT PLOTTERMANAGER “” AutoCAD 2008 > > > PLOTTERMANAGER “” AutoCAD 2008 > > PC3 > PC3 PLOTTERMANAGER “” AutoCAD 2008 > > PC3 > PC3 PC3 PMP PMP HDI AutoCAD 2008 > > PC3 > > PLOTTERMANAGER “” AutoCAD 2008 > > PC3 > > PLOTTERMANAGER “” AutoCAD 2008 > > PC3 > > PLOTTERMANAGER “” AutoCAD 2008 > > PC3 > > PLOTTERMANAGER “” AutoCAD 2008 > > PC3 > > PLOTTERMANAGER “”
    [Show full text]
  • Using Unioledb
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\UNIOLEDB\OLDBTITL.fm March 10, 2010 10:42 am Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Using UniOLEDB UDT-720-OLDB-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\UNIOLEDB\OLDBTITL.fm March 10, 2010 10:42 am Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July 2008 Book number: UDT-720-OLDB-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2008. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii Using UniOLEDB The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • Powerbuilder® 2017 R3 for WINDOWS DOCUMENT ID: ADC20231-01-2017-03 LAST REVISED: July 30, 2018 Copyright © 2018 by Appeon Limited
    Release Bulletin for PowerBuilder 2017 R3 PowerBuilder® 2017 R3 FOR WINDOWS DOCUMENT ID: ADC20231-01-2017-03 LAST REVISED: July 30, 2018 Copyright © 2018 by Appeon Limited. All rights reserved. This publication pertains to Appeon software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Appeon Limited. Appeon and other Appeon products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Appeon Limited. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP and SAP affiliate company. Java and all Java-based marks are trademarks or registered trademarks of Oracle and/or its affiliates in the U.S. and other countries. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.
    [Show full text]
  • Programming with Windows Forms
    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
    [Show full text]
  • Release Bulletin Infomaker 11.5.1
    Release Bulletin InfoMaker® 11.5.1 Document ID: DC33824-01-1151-01 Last revised: May 14, 2009 Topic Page 1. Accessing current release bulletin information 2 2. Product summary 2 3. Special installation instructions 3 3.1 Before you install 3 3.2 Updating InfoMaker 11.5 to InfoMaker 11.5.1 3 4. Changed functionality in this version 4 4.1 Deployment support for the Windows 2000 platform 4 4.2 JDK 1.6 support 4 4.3 FIPS 140-2 certification 4 4.4 Support for Microsoft Office 2007 Excel formats 5 4.5 Support for SQL Anywhere 11.0 mirroring 5 4.6 Informix 11.5 Support 5 4.7 Microsoft SQL Server 2008 support 6 5. Known problems 6 5.1 Gradient, transparency and tooltip properties 6 5.2 New 3D graph styles 7 5.3 PNG support issues 8 5.4 Other issues 9 6. Product compatibilities 10 6.1 SQL Anywhere 10 6.2 Ghostscript 10 7. Third-party components and deployment 10 7.1 Apache files 10 7.2 Microsoft files 11 7.3 Sun Microsystems files 12 8. Documentation updates and clarifications 12 Copyright 2009 by Sybase, Inc. All rights reserved. Sybase trademarks can be viewed at the Sybase trademarks page at http://www.sybase.com/detail?id=1011207. Sybase and the marks listed are trademarks of Sybase, Inc. ® indicates registration in the United States of America. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.
    [Show full text]
  • Oracle Provider for OLE DB Developer's Guide, 11G Release 2 (11.2) for Microsoft Windows E17726-03
    Oracle® Provider for OLE DB Developer’s Guide 11g Release 2 (11.2) for Microsoft Windows E17726-03 July 2013 Oracle Provider for OLE DB Developer's Guide, 11g Release 2 (11.2) for Microsoft Windows E17726-03 Copyright © 1999, 2013, Oracle and/or its affiliates. All rights reserved. Contributors: Janis Greenberg, Eric Belden, Riaz Ahmed, Kiminari Akiyama, Neeraj Gupta, Sinclair Hsu, Gopal Kirsur, Sunil Mushran, Rajendra Pingte, Helen Slattery, Valarie Moore, Vikhram Shetty, Sujith Somanathan, Alex Keh, Christian Shay This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • PGNP Native OLE DB Provider for Postgresql, Greenplum, Redshift Developer’S Manual
    CATA 2021 PGNP Native OLE DB Provider for PostgreSQL, Greenplum, Redshift Developer’s Manual This document contains description of various PGNP features, use cases and programming techniques. It is written for professional developers. Konstantin Izmailov Copyright © 2006-2019. All Rights Reserved. 2/12/2021 This document is property of PGNP team. Neither a part nor the entire document can be reproduced, changed, distributed or published without prior written permission of owners. Please contact us if you have any questions: [email protected]. Page 2 Table of Contents 1 Introduction .................................................................................................................................................................... 6 2 Installation and Product Activation ................................................................................................................................ 7 2.1.1 UI based installation ........................................................................................................................................ 7 2.1.2 Unattended/silent installation ...................................................................................................................... 10 2.1.3 Activation on a computer behind a firewall (in DMZ) .................................................................................. 11 3 Provider’s Features ......................................................................................................................................................
    [Show full text]
  • Developing ADO.NET and OLE DB Applications
    DB2 ® DB2 Version 9 for Linux, UNIX, and Windows Developing ADO.NET and OLE DB Applications SC10-4230-00 DB2 ® DB2 Version 9 for Linux, UNIX, and Windows Developing ADO.NET and OLE DB Applications SC10-4230-00 Before using this information and the product it supports, be sure to read the general information under Notices. 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 www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at 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 International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. ADO.NET development for .NET common language runtime (CLR) routines . .57 Supported .NET CLR routine development software 58 DB2 databases . .1 Support for external routine development in ADO.NET application development .
    [Show full text]
  • Oracle® Provider for OLE DB Developer's Guide
    Oracle® Provider for OLE DB Developer's Guide 19c for Microsoft Windows E96615-01 May 2019 Oracle Provider for OLE DB Developer's Guide, 19c for Microsoft Windows E96615-01 Copyright © 1999, 2019, Oracle and/or its affiliates. All rights reserved. Primary Author: Maitreyee Chaliha Contributing Authors: Janis Greenberg, Alex Keh, Eric Belden, Riaz Ahmed, Kiminari Akiyama, Christian Shay, Valarie Moore, Neeraj Gupta, Sinclair Hsu, Gopal Kirsur, Sunil Mushran, Rajendra Pingte, Helen Slattery, Vikhram Shetty, Sujith Somanathan, Mark Williams This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations.
    [Show full text]