Universal Data Access and OLE DB. Customer Requirements for Data Access Technologies High-Performance access to data Reliability Vendor Commitment Broad.

Slides:



Advertisements
Similar presentations
Connecting to Databases. relational databases tables and relations accessed using SQL database -specific functionality –transaction processing commit.
Advertisements

DIGIDOC A web based tool to Manage Documents. System Overview DigiDoc is a web-based customizable, integrated solution for Business Process Management.
Chapter 10: Designing Databases
Fundamentals, Design, and Implementation, 9/e Chapter 12 ODBC, OLE DB, ADO, and ASP.
Prentice Hall © COS 346 Day Agenda Capstone Progress report due Assignment 9 not corrected yet Assignment 10 posted (last one!!!) –Due.
The ADO Data Control. Universal Data Access Open Database Connectivity (ODBC) –standard for accessing data in databases OLE-DB –allows access to data.
BICS546 Client/Server Database Application Development.
15 Chapter 15 Web Database Development Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
Using Visual Basic 6.0 to Create Web-Based Database Applications
Chapter 12: ADO.NET and ASP.NET Programming with Microsoft Visual Basic.NET, Second Edition.
INTERNET DATABASE Chapter 9. u Basics of Internet, Web, HTTP, HTML, URLs. u Advantages and disadvantages of Web as a database platform. u Approaches for.
Database Management: Getting Data Together Chapter 14.
14 1 Chapter 14 Database Connectivity and Web Development Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Organizing Data & Information
Fundamentals, Design, and Implementation, 9/e COS 346 DAY 22.
INTERNET DATABASE. Internet and E-commerce Internet – a worldwide collection of interconnected computer network Internet – a worldwide collection of interconnected.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 12-1 COS 346 Day 22.
Database Programming (using ADO) Universal Data Access – Microsoft strategy for providing access to information across the enterprise. – UDA provides high-performance.
ASP.NET Programming with C# and SQL Server First Edition Chapter 8 Manipulating SQL Server Databases with ASP.NET.
System Analysis and Design
Chapter 12 Database Connectivity with ASP.NET JavaScript, Third Edition.
Chapter 14 Database Connectivity and Web Technologies
14 Chapter 14 Databases and The Internet Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
Blue Group (ADO) 3/10/98 Universal Data Access with ActiveX Data Objects The Blue Group *Jennifer Kochan *Rebecca Orozco *Chris Papandria *Alicja Stanczak.
Objective In this session we will discuss about : What is ADO. NET ?
Overview of Database Access in.Net Josh Bowen CIS 764-FS2008.
ODBC Open DataBase Connectivity a standard database access method developed by Microsoft to access data from any application regardless of which database.
CIS 764 – Presentation Somil Chandwani.  With Microsoft Data Access Components (MDAC), developers can connect to and use data from a wide variety of.
1 Web Database Processing. Web Database Applications Static Report Publishing a report is prepared from a database application and exported to HTML DB.
Database System Concepts and Architecture Lecture # 3 22 June 2012 National University of Computer and Emerging Sciences.
Architecture Of ASP.NET. What is ASP?  Server-side scripting technology.  Files containing HTML and scripting code.  Access via HTTP requests.  Scripting.
Beyond DHTML So far we have seen and used: CGI programs (using Perl ) and SSI on server side Java Script, VB Script, CSS and DOM on client side. For some.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 12-1 David M. Kroenke’s Chapter Twelve: ODBC, OLE DB, ADO, and ASP Part.
1 ODBC, OLE DB, ADO, and ASP. 2 Introduction  Because database applications today reside in a complicated environment, various standards have been developed.
How to Configure Informix Connect and ODBC James Edmiston Informix DBA Consultant/Quest Information Systems, Inc. Informix User Forum 2005 Moving Forward.
I Copyright © 2004, Oracle. All rights reserved. Introduction.
Web-Enabled Decision Support Systems
Using Visual Basic 6.0 to Create Web-Based Database Applications
11/16/2012ISC329 Isabelle Bichindaritz1 Web Database Application Development.
Fundamentals of Database Chapter 7 Database Technologies.
CS480 Computer Science Seminar Introduction to Microsoft Solutions Framework (MSF)
Tutorial 10 by Sam ine1020 Introduction to Internet Engineering 1 Database & Server-side Scripting Tutorial 10.
File Processing Concepts – Field – combination of 1 or more characters that is the smallest unit of data to be accessed – Record – group of related fields.
Relational Databases Database Driven Applications Retrieving Data Changing Data Analysing Data What is a DBMS An application that holds the data manages.
CSS/417 Introduction to Database Management Systems Workshop 4.
What is database?  Any Method for access info into Application from DataBase?  ODBC is standard for Accessing Data.  Problem with ODBC:  Information.
Lesson Overview 3.1 Components of the DBMS 3.1 Components of the DBMS 3.2 Components of The Database Application 3.2 Components of The Database Application.
IS 325 Notes for Wednesday August 28, Data is the Core of the Enterprise.
3-Tier Client/Server Internet Example. TIER 1 - User interface and navigation Labeled Tier 1 in the following graphic, this layer comprises the entire.
Tutorial 91 Databases A database is an organized collection of related information stored in a file on a disk A database allows companies to store information.
School of Computing and Management Sciences © Sheffield Hallam University Issues of Data Access 101(-ish) ways to access data from a database! ODBC One.
Database Concepts Track 3: Managing Information using Database.
Chapter 5 Introduction To Form Builder. Lesson A Objectives  Display Forms Builder forms in a Web browser  Use a data block form to view, insert, update,
5-1 VISUAL J++ Colorado Technical University IT420 Tim Peterson.
Database Connectivity and Server-Side Scripting Chapter 12.
Database Connectivity with ASP.NET. 2 Introduction Web pages commonly used to: –Gather information stored on a Web server database Most server-side scripting.
Object storage and object interoperability
ODBC : Open Database Connectivity SNU OOPSLA Lab. October 2005.
What’s new in ADO 2.5 Greg Hinkel Program Manager Data Access Group
ASP-2-1 SERVER AND CLIENT SIDE SCRITPING Colorado Technical University IT420 Tim Peterson.
Copyright (c) 2014 Pearson Education, Inc. Introduction to DBMS.
Introduction Because database applications today reside in a complicated environment, various standards have been developed for accessing database servers.
7-1 Active Server and ADO Colorado Technical University IT420 Tim Peterson.
ADO & Recordsets. ADO Description & History  ActiveX Data Objects  History  1991 ODBC  Data Access Objects (DAO) for VB developers (JET)  Remote.
Introduction to SQL Server 2000 Reporting Services Jeff Dumas Technical Specialist Microsoft Corporation
CLIENT SERVER COMPUTING. We have 2 types of n/w architectures – client server and peer to peer. In P2P, each system has equal capabilities and responsibilities.
ADO .NET from. ADO .NET from “ADO .Net” Evolution/History of ADO.NET MICROSOFT .NET “ADO .Net” Evolution/History of ADO.NET History: Most applications.
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
Chapter 10 ADO.
Presentation transcript:

Universal Data Access and OLE DB

Customer Requirements for Data Access Technologies High-Performance access to data Reliability Vendor Commitment Broad industry support

Universal Data Access UDA is a platform for developing multitier enterprise applications that require access to diverse relational or nonrelational data sources across intranets or the Internet. Provides high-performance access to a variety of data and information sources on multiple platforms. it does not require expensive and time-consuming movement of all corporate data into a single data store

Universal Data Access UDA consists of a collection of software components that interact with each other using a common set of system-level interfaces defined by OLE DB.

Universal Data Access

UDA Component Data providersData providers are components that represent diverse sources of data such as SQL databases, indexed-sequential files, spreadsheets, document stores, and mail files. (RowSet) ServicesServices are components that extend the functionality of data providers by implementing extended interfaces where not natively supported by the data store. ConsumersConsumers are components that consume OLE DB data. Examples of consumers include high-level data access models such as ADO. (VB,C++,Java)

Universal Data Access The strength of UDA is it is delivered through a common set of modern, object-oriented interfaces(Component Object Model:COM) –The richest integrated services –The widest choice of tools from multiple vendors using multiple development languages –The largest customer base for customizable applications and reusable components –Proven interoperability with users’ and developers’ existing investments

COM interfaces OLE DBLow level application developmentOLE DB ADOHigh level application developmentADO

OLE DB OLE DB is Microsoft’s strategic 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. OLE DB is designed for relational and nonrelational information sources, including mainframe ISAM/VSAM and hierarchical databases; and file system stores; text, graphical and geographical data; custom business objects; and more.

ActiveX Data Object ADO is application-level programming interface to data and information over OLE DB data. ADO provides consistent, high-performance access to data and supports a variety of development needs, including the creation of front-end database clients and middle-tier business objects, using applications, tools, languages or Internet browsers. ADO is designed to be the one data interface needed for one-to-multitier client/server and Web-based data-driven solution development.

ActiveX Data Object ADO provides an easy-to-use application level interface to OLE DB, which provides the underlying access to data. ADO is implemented with a small footprint, minimal network traffic in key scenarios, and a minimal number of layers between the front end and data source — all to provide a lightweight, high- performance interface. ADO was designed to combine the best features of - and eventually replace - RDO and DAO

ADO provides several advantages to programmers: –Ease of use –Programming language neutral. ADO can be used from languages such as Visual Basic, Java, C++, VBScript, and JScript. –Provider neutral. ADO can access data from any OLE DB source. In addition, ADO adapts gracefully to support less functional OLE DB providers. –No loss of OLE DB functionality. ADO allows C++ programmers access to the underlying OLE DB interfaces. –Extensible. ADO can dynamically expose properties specific to a data provider via collections of provider properties. In addition, it provides type extensibility by allowing access to COM objects exposed as column values.

Design Goal of Microsoft Data Access Component MDAC is a set of redistributable technologies that implement Universal Data Access. MDAC consists of the latest versions of ActiveX Data Objects, OLE DB components and Open Database Connectivity.

Universal Data Access Architecture

Comparison of the ADO and DAO/RDO Architectures

How ADO and OLE DB work over the Internet

OLE DB

ADO Object Model

Connection, Command, and Recordset objects are top-level objects that you can create and destroy independently of each of the other objects. Parameter must be associated with a Command before you can use it. Field, Error, and Property objects each exist only within the context of their parent objects, and can’t be separately created.

ADO Object Model Connection object encapsulates the OLE DB Data Source and Session objects. Represents a single session with the data source. Connection object defines properties of the connection Assigns the scope of local transactions, Provides a central location for retrieving errors, And provides a point for executing schema queries.

ADO Object Model Command object encapsulates the OLE DB Command object. Command specifies the data-definition or data- manipulation statement to be executed –case of a relational provider, this is an SQL statement. Command object allows you to specify parameters and customize the behavior of the statement to be executed. A collection of Parameter objects exposes the parameters

ADO Object Model Recordset object encapsulates the OLE DB Rowset object. Recordset object is the actual interface to the data, whether it is the result of a query or was generated in some other fashion. Recordset object provides control over the –locking mechanism used –the type of cursor to be used –the number of rows to access at a time –and so on.

ADO Object Model Recordset object exposes a collection of Field objects that contain the metadata about the columns in the recordset, such as the name, type, length and so on. Recordset object to navigate through records and change data (assuming the underlying provider is updatable).

ADO Object Model Each of the top-level ADO objects contains a collection of Property objects Property object allows ADO to dynamically expose the capabilities of a specific provider, because not all data providers have the same functionality It is important for the ADO model to allow you to access provider-specific settings in a dynamic way