 - ActiveX Data Objects (ADO) is an application program interface from Microsoft that lets a programmer writing Windows applications get access to a relational or non-relational database from both Microsoft and other database providers. For example, if you wanted to write a program that would provide users of your Web site with data from an IBM DB2 database or an Oracle database, you could include ADO program statements in an HTML file that you then identified as an Active Server Page. Then, when a user requested the page from the Web site, the page sent back would include appropriate data from a database, obtained using ADO code.
Like Microsoft's other system interfaces, ADO is an object-oriented programming interface. It is also part of an overall data access strategy from Microsoft called Universal Data Access. Microsoft says that rather than trying to build a universal database as IBM and Oracle have suggested, finding a way to provide universal access to various kinds of existing and future databases is a more practical solution. In order for this to work, Microsoft and other database companies provide a "bridge" program between the database and Microsoft's OLE DB, the low-level interface to databases.
OLE DB is the underlying system service that a programmer using ADO is actually using. A feature of ADO, Remote Data Service, supports "data-aware" ActiveX controls in Web pages and efficient client-side caches. As part of ActiveX, ADO is also part of Microsoft's overall Component Object Model (COM), its component-oriented framework for putting programs together.
ADO evolved from an earlier Microsoft data interface, Remote Data Objects (RDO). RDO works with Microsoft's ODBC to access relational databases, but not nonrelational databases such as IBM's ISAM and VSAM.
 |
Learn more about SQL Server Database Modeling and Design |
| SQL Server database design disasters: What not to do: Inspired by what he recently found in some SQL Server shops, database architect Brian Walker shares advice for improved database design – and SQL Server performance. |
| Physical data storage in SQL Server 2005 and 2008: Learn the fundamentals of data storage in SQL Server 2005 and 2008, including tables, views and data types, in this book excerpt. |
| Designing SQL Server non-clustered indexes for query optimization: Optimize SQL Server non-clustered indexes and queries by considering index fields, compound indexes and SQL Server statistics' impact on non-clustered indexes. |
  |
Creating SQL Server tables and columns: Quick tips to know: Improve performance of SQL Server tables and columns by defining data types, indexes, keys, partitions and more. Create SQL Server columns and tables with these best practices. |
| Top 10 SQL Server Tips of 2008: Get the top 10 SQL Server tips of 2008 on topics such as clustered index design, log shipping setup, date/time data conversions and many other aspects of SQL Server. |
| Tutorial: SQL Server indexing tips to improve performance: Significantly improve your SQL Server performance through this tutorial on proper indexing choices. Learn how to design high performing indexes and tune your existing SQL indexes. |
| Tutorial: Learn SQL Server basics from A-Z: If you're new to SQL Server of simply want a refresher on some fundamentals, check out this tutorial on topics from security and performance to SSIS and using native tools. |
| Supertype and subtype tables in SQL Server: Learn how to physically implement supertype and subtype tables on a SQL Server in this book excerpt. |
| SQL Server and data manipulation in T-SQL: Learn about stored procedures, parameters, triggers and other T-SQL code functions in this book excerpt. |
| LAST UPDATED: |
10 Jul 2006
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
