1 / 20

CSIS4310

CSIS4310. Project Deliverables Connectivity (ODBC, ADO). Default Deliverables (may vary depending on the type of project). 1) Project Description PERT or GANNT Chart (put whole chart on 1 page) Draw an E-R Diagram with Entity, Relationships, Cardinalities, Sub-Types

haviva-barnett
Download Presentation

CSIS4310

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSIS4310 Project Deliverables Connectivity (ODBC, ADO)

  2. Default Deliverables (may vary depending on the type of project) 1) Project Description • PERT or GANNT Chart (put whole chart on 1 page) • Draw an E-R Diagram with Entity, Relationships, Cardinalities, Sub-Types 4) Form versus Tables Matrix (optional) 5) Schema with keys indicated 6) DDL (tables, attributes, datatypes) • Source code and Printouts of the screen • Description of Main Difficulties Encountered • Description of Alternatives • Conclusions. What would you have doneDifferently. Self Evaluation.

  3. Relational Schema

  4. For Design & Maintainence

  5. Form versus Table Matrix for DW • For a Datawarehouse, the Form versus matrix should be expanded to Program versus Data/File. Url source file, temporary file and final database table should all appear in this form. Likewise, the program to extract data (even if it was done manually) should appear in this Matrix.

  6. DD for Data Warehouse Includes • Definition of Data at Origin & at Destination • Mapping of Desktop to PDA • Interval of Uploads • Description of Process Used to Bring Data In (p.s project should include Code for Each View)

  7. Front-End to Back-End • OBDC (Open Database Connectivity) is the early standard for relational databases • OLE DB is the Microsoft’s object-oriented interface for relational and other databases • ADO (Active Data Objects) is the Microsoft’s standard providing easier access to OLE DB data for the non-object-oriented programmer

  8. ODBC

  9. OLE DB

  10. ADO

  11. ODBC Components • OBDC consists of data source, application program, drivermanager, and DBMS driver • Data source is the database, its associated DBMS, operating system, and network platform • An ODBC data source can be a relational database or a spreadsheet • Applications program issues requests to create a connection with a data source • Driver manager determines the type of DBMS for a given ODBC data source and loads that driver in memory • DBMS driver processes ODBC requests and submits specific SQL statements to a given type of data source

  12. OLE DB • OLE DB is an implementation of the Microsoft OLE object standard • OLE DB objects are COM objects and support all required interfaces for such objects • OLE DB breaks the features and functions of a DBMS into COM objects, making it easier for vendors to implement portions of functionality • This characteristic overcomes a major disadvantage of ODBC • With ODBC, a vendor must create an ODBC driver for almost all DBMS features and functions in order to participate in ODBC at all

  13. OLE DB Goals • Create object interfaces for DBMS functionality pieces • Query, update, transaction management, etc. • Increase flexibility • Allow data consumers to use only the objects they need • Allow data providers to expose pieces of DBMS functionality • Providers can deliver functionality in multiple interfaces • Interfaces are standardized and extensible • Object interface over any type of data • Relational and non-relational database, ODBC or native, VSAM and other files, Email, etc. • Do not force data to be converted or moved fromwhere it is

  14. Active Data Objects: MS-Visual Studios • ADO (Active Data Objects) characteristics • Simple object model for OLE DB data consumers • Can be used from VBScript, JScript, Visual Basic, Java, C#, C++ • Single Microsoft data access standard • Data access objects are the same for all types of OLE DB data

  15. ADO Object Model

  16. Cursor, RecordSet, Dataset • Cursor in PL/SQL, Embedded SQL = • RecordSet (or ResultSet) in Java = • DataSet in MS-Visual Studios. • It can be basically seen as a File in Memory

  17. Recommendation for Further Studies • MS-Visual Studios -> Walkthroughs • Data Examples • Web Examples

  18. F.A.Q. • Do I have to print the whole source code ? Answer: No. Deliverables can be turned in as hard copy, url links or diskette. It is important for you to highlight the most important part of the source code. 2) Is dataset a client side object or a server side object ? Answer: ALWAYS A CLIENT-SIDE.

More Related