Object Linking and Embedding Database (OLE DB)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Object Linking and Embedding Database (OLE DB) is a set of Component Object Model (COM) interfaces that provide applications with uniform access to data stored in diverse information sources and that also provide the ability to implement additional database services. These interfaces support the amount of database management system (DBMS) functionality appropriate to the data store, enabling the sharing of data.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v20.10
Decision Date:	10/27/2020
Aliases:	OLE DB
Introduced By:	TRMSP
Standards Body:	Microsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Industry Standard, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.8	08/04/2003
WDAC 6.0	02/27/2008

Current Decision Matrix (10/23/2020)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
<Past	CY2022				CY2023				CY2024				Future>
WDAC 6.0	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Guideline	Object Linking and Embedding Database (OLE DB) Programmer`s Guide		This is the OLE DB Programmer`s Guide.

Standard Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Source	Name	Description
Microsoft	Connection Strings and Data Links	A data link enables users to store connection information within an application or to pass it between applications. The format of a data link is a connection string, which is a string version of the initialization properties needed to connect to a data store. Without a connection string, it would be necessary to store or pass a complex array of structures to access data.
	Provider Extensible Data Link User Interface Application Programming Interface (API)	This section describes the mechanism for implementing provider extensions to the Data Link user interface. The interfaces used are all standard Component Object Model (COM) interfaces for handling property sheets, and detailed reference information can be found in the MSDN Library documentation.
	Root Binder Object	The binding process is managed by the root binder object, which is an Object Linking and Embedding Database (OLE DB) object with a well-known Class Identifier (CLSID). This CLSID, which is defined in Msdasc.h, is CLSID_RootBinder. The root binder object manages the mapping of Uniform Resource Locator (URL) namespaces to OLE DB providers.
	Root Enumerator Object	The Object Linking and Embedding Database (OLE DB) root enumerator object enumerates OLE DB providers and enumerators on a user`s system. The root enumerator traverses the registry searching for provider data source objects and enumerators listed in the registry.
	Row Position Object	The Object Linking and Embedding Database (OLE DB) row position object keeps track of a current hRow so that multiple components can coordinate operations on that row. Consumers create a row position object and set or retrieve the current row position using the IRowPosition interface.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Information Management Technologies Data Management	Object-Oriented DBMS

Technologies/Standards Relationships

Implemented By/Verified With:

Windows Client - (implemented by)
Windows Server - (implemented by)

Comparable Standards:

Open Database Connectivity (ODBC)

Associated Standards:

Open Database Connectivity (ODBC)

General Analysis

Adoption Benefits

This is a mature standard, first released in August 1996.
There are no known Common Vulnerabilities and Exposures (CVEs) associated with this standard at the time of writing.
This standard is designed as a component-based technology. Components can be designed to interact correctly at different levels of functionality without limiting new features or requiring an "all-or-nothing" implementation.
With developers writing Object Linking and Embedding Database (OLE DB), consumers can choose their level of interoperability with OLE DB providers. Consumers may be written to consume a specific provider or written to consume generic providers.
This standard defines the application programming interfaces (APIs), which allow data providers to access data in databases, file systems, message stores, directory services, and workflow and document stores. This provides data interoperability.

Adoption Risks

This standard does not appear to have had any recent development.

Architectural Risks

This standard is only portable across Windows operating systems.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (10/23/2020)

References

Standard Components

VA Categories View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (10/23/2020)

References

Standard Components

VA Categories View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

EMAIL UPDATES