You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ado/ado-glossary.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,18 @@
1
1
---
2
+
description: "ADO Glossary Terms"
2
3
title: "ADO Glossary Terms | Microsoft Docs"
3
4
ms.prod: sql
4
5
ms.prod_service: connectivity
5
-
ms.technology: connectivity
6
+
ms.technology: ado
6
7
ms.custom: ""
7
8
ms.date: 11/08/2018
8
9
ms.reviewer: ""
9
10
ms.topic: conceptual
10
11
helpviewer_keywords:
11
12
- "ADO, glossary"
12
13
ms.assetid: b0478836-4123-4357-969a-c5784fc28be5
13
-
author: MightyPen
14
-
ms.author: genemi
14
+
author: rothja
15
+
ms.author: jroth
15
16
---
16
17
# ADO Glossary Terms
17
18
This topic defines terms relevant to ADO.
@@ -171,14 +172,14 @@ This topic defines terms relevant to ADO.
171
172
hierarchical Recordset
172
173
A **Recordset** that contains another **Recordset**. See also data shaping, chapter.
173
174
174
-
For more information, see [Accessing Rows in a Hierarchical Recordset](../ado/guide/data/accessing-rows-in-a-hierarchical-recordset.md).
175
+
For more information, see [Accessing Rows in a Hierarchical Recordset](./guide/data/accessing-rows-in-a-hierarchical-recordset.md).
175
176
176
177
hierarchy
177
178
In general, a hierarchy is a ranked structure with a top level and subordinate levels. In ADO, hierarchical **Recordsets** are used to represent the parent-child relationship between a record and a chapter. Also in ADO, **Record** and **Stream** objects can be used to access hierarchical tree structures such as a folder and documents. ADO MD also includes **Hierarchy** objects to represent a relationship between the levels of a dimension in an OLAP cube. See also hierarchical Recordsets, parent-child relationship, chapter, tree.
178
179
179
180
## I-L
180
181
ISAPI (Internet Server Application Programming Interface)
181
-
A set of functions for Internet servers, such as a Windows NT® Server/Windows 2000 Server running Microsoft® Internet Information Services (IIS).
182
+
A set of functions for Internet servers, such as a Windows NT® Server/Windows 2000 Server running Microsoft® Internet Information Services (IIS).
182
183
183
184
Key
184
185
A column or columns in a table that uniquely identify a row; often used to index a table.
@@ -286,4 +287,4 @@ This topic defines terms relevant to ADO.
286
287
A structure representing a hierarchical relationship between elements (nodes). There is one node at the top level of a tree (the root). Underneath the root, there can be multiple children. Each child may in turn be the parent of other children, thus branching like a tree. A folder containing documents and other folders is a typical example of a tree structure. See also hierarchy, node, root, child, parent.
287
288
288
289
Web server
289
-
A computer that provides Web services and pages to intranet and Internet users.
290
+
A computer that provides Web services and pages to intranet and Internet users.
@@ -19,65 +20,65 @@ This topic lists the new features introduced by each release of ADO, ADO MD, and
19
20
20
21
## ADO 6.0
21
22
22
-
ADO 6.0 is included in Windows Vista, as a part of the Windows Data Access Components (Windows DAC) 6.0. ADO 6.0 is functionally equivalent to ADO 2.8.
23
+
ADO 6.0 is included in Windows Vista, as a part of the Windows Data Access Components (Windows DAC) 6.0. ADO 6.0 is functionally equivalent to ADO 2.8.
23
24
24
25
## ADO 2.8
25
26
26
-
ADO 2.8 was included in Windows XP and Windows Server 2003, as part of the Microsoft Data Access Components (MDAC) 2.8. A redistributable version of MDAC 2.8 is also available; note that this redistributable version should only be installed on Windows 2000. ADO 2.8 addresses several security-related concerns:
27
+
ADO 2.8 was included in Windows XP and Windows Server 2003, as part of the Microsoft Data Access Components (MDAC) 2.8. A redistributable version of MDAC 2.8 is also available; note that this redistributable version should only be installed on Windows 2000. ADO 2.8 addresses several security-related concerns:
27
28
28
-
*Hard drive access is not allowed outside a trusted zone.*
29
-
In cross-domain scripting involving nontrusted sites, the following operations are disabled: **Stream.SaveToFile**, **Stream.LoadFromFile**, **Recordset.Save**, and **Recordset.Open**, used in conjunction with the **adCmdFile** flag or with the Microsoft OLE DB Persistence Provider (MSPersist).
29
+
*Hard drive access is not allowed outside a trusted zone.*
30
+
In cross-domain scripting involving nontrusted sites, the following operations are disabled: **Stream.SaveToFile**, **Stream.LoadFromFile**, **Recordset.Save**, and **Recordset.Open**, used in conjunction with the **adCmdFile** flag or with the Microsoft OLE DB Persistence Provider (MSPersist).
30
31
31
-
**Recordset.Open**_,_**Recordset.Save**_,_**Stream.SaveToFile**_, and_**Stream.LoadFromFile**_operate on physical files only._
32
-
These methods now verify that file handles point to physical files only.
32
+
**Recordset.Open**_,_**Recordset.Save**_,_**Stream.SaveToFile**_, and_**Stream.LoadFromFile**_operate on physical files only._
33
+
These methods now verify that file handles point to physical files only.
33
34
34
-
**Recordset.ActiveCommand**_returns an error when invoked from an HTML/ASP page._
35
-
This prevents the **Command** object from being misused.
35
+
**Recordset.ActiveCommand**_returns an error when invoked from an HTML/ASP page._
36
+
This prevents the **Command** object from being misused.
36
37
37
-
_The number of_**Recordsets**_returned by a nested_**Shape**_command has an upper bound._
38
-
A nested shape command now returns a maximum of 512 **Recordsets**. This means that a **Shape** command can no longer be nested at any depth. Instead, the maximum level depth is 512, if each command results in a single (child) **Recordset**. If, at any level, a **Shape** command returns multiple **Recordsets**, the maximum level of depth will be less than 512.
38
+
_The number of_**Recordsets**_returned by a nested_**Shape**_command has an upper bound._
39
+
A nested shape command now returns a maximum of 512 **Recordsets**. This means that a **Shape** command can no longer be nested at any depth. Instead, the maximum level depth is 512, if each command results in a single (child) **Recordset**. If, at any level, a **Shape** command returns multiple **Recordsets**, the maximum level of depth will be less than 512.
39
40
40
41
## ADO 2.7
41
42
42
-
*64-bit platform support*
43
-
ADO 2.7 introduces support for 64-bit processors.
43
+
*64-bit platform support*
44
+
ADO 2.7 introduces support for 64-bit processors.
44
45
45
46
## ADO 2.6
46
47
47
-
**CubDef.GetSchemaObject**_Method_
48
-
Starting with ADO 2.6, ADO MD objects can be retrieved using unique names, as specified by the [UniqueName property (ADO MD)](../../ado/reference/ado-md-api/uniquename-property-ado-md.md). The names of parent objects do not need to be known, and parent collections do not need to be populated to retrieve a schema object. See [GetSchemaObject method (ADO MD)](../../ado/reference/ado-md-api/getschemaobject-method-ado-md.md).
48
+
**CubDef.GetSchemaObject**_Method_
49
+
Starting with ADO 2.6, ADO MD objects can be retrieved using unique names, as specified by the [UniqueName property (ADO MD)](../reference/ado-md-api/uniquename-property-ado-md.md). The names of parent objects do not need to be known, and parent collections do not need to be populated to retrieve a schema object. See [GetSchemaObject method (ADO MD)](../reference/ado-md-api/getschemaobject-method-ado-md.md).
49
50
50
-
*Command streams*
51
-
The **Command** object supports commands in stream format as an alternative to using the **CommandText** property. The [CommandStream property (ADO)](../../ado/reference/ado-api/commandstream-property-ado.md) can be used to specify XML Templates or updategrams as the **Command** input with the Microsoft OLE DB Provider for SQL Server.
51
+
*Command streams*
52
+
The **Command** object supports commands in stream format as an alternative to using the **CommandText** property. The [CommandStream property (ADO)](../reference/ado-api/commandstream-property-ado.md) can be used to specify XML Templates or updategrams as the **Command** input with the Microsoft OLE DB Provider for SQL Server.
52
53
53
-
**Dialect**_property_
54
-
[Dialect](../../ado/reference/ado-api/dialect-property.md) is a new property that defines the syntax and general rules that the provider uses to parse the string or stream.
54
+
**Dialect**_property_
55
+
[Dialect](../reference/ado-api/dialect-property.md) is a new property that defines the syntax and general rules that the provider uses to parse the string or stream.
55
56
56
-
**Command.Execute**_method_
57
-
The [Execute method](../../ado/reference/ado-api/execute-method-ado-command.md) of the ADO **Command** object has been enhanced to use streams for input and output.
57
+
**Command.Execute**_method_
58
+
The [Execute method](../reference/ado-api/execute-method-ado-command.md) of the ADO **Command** object has been enhanced to use streams for input and output.
58
59
59
-
*Field statusvalues*
60
-
If the user encounters a DB_E_ERRORSOCCURRED error when modifying a **Field** of a **Recordset**, ADO will now fill the **Field.Status** property with the appropriate status information so that the user will have more information about what went wrong. See [Status Property (ADO Field)](../../ado/reference/ado-api/status-property-ado-field.md).
60
+
*Field statusvalues*
61
+
If the user encounters a DB_E_ERRORSOCCURRED error when modifying a **Field** of a **Recordset**, ADO will now fill the **Field.Status** property with the appropriate status information so that the user will have more information about what went wrong. See [Status Property (ADO Field)](../reference/ado-api/status-property-ado-field.md).
61
62
62
-
**NamedParameters**_property_
63
-
[NamedParameters](../../ado/reference/ado-api/namedparameters-property-ado.md) is a new property of the **Command** object that indicates that the provider should use named parameters.
63
+
**NamedParameters**_property_
64
+
[NamedParameters](../reference/ado-api/namedparameters-property-ado.md) is a new property of the **Command** object that indicates that the provider should use named parameters.
64
65
65
-
*Resultsets in streams*
66
-
ADO can return resultsets from a data source in a **Stream**, rather than a **Recordset** object. Using the latest version of the Microsoft OLE DB Provider for SQL Server, you can get XML results from the provider by executing a "For XML" query. A **Stream** that receives the resultset can be opened with a "For XML" command as the source. See [Retrieving Resultsets into Streams](../../ado/guide/data/retrieving-resultsets-into-streams.md).
66
+
*Resultsets in streams*
67
+
ADO can return result sets from a data source in a **Stream**, rather than a **Recordset** object. Using the latest version of the Microsoft OLE DB Provider for SQL Server, you can get XML results from the provider by executing a "For XML" query. A **Stream** that receives the result set can be opened with a "For XML" command as the source. See [Retrieving Result sets into Streams](./data/retrieving-resultsets-into-streams.md).
67
68
68
-
*Single row resultset*
69
-
The ADO **Record** object can now be opened on a command string or **Command** object that returns one row of data from the provider. This results in improved performance with MDAC 2.6 providers. See [Open Method (ADO Record)](../../ado/reference/ado-api/open-method-ado-record.md).
69
+
*Single row resultset*
70
+
The ADO **Record** object can now be opened on a command string or **Command** object that returns one row of data from the provider. This results in improved performance with MDAC 2.6 providers. See [Open Method (ADO Record)](../reference/ado-api/open-method-ado-record.md).
70
71
71
72
## ADO 2.5
72
73
73
-
**Record**_object_
74
-
ADO 2.5 introduces the **Record** object to represent and manage a row from a **Recordset** or a data provider, or an object encapsulating a semi-structured data, such as a file or directory.
74
+
**Record**_object_
75
+
ADO 2.5 introduces the **Record** object to represent and manage a row from a **Recordset** or a data provider, or an object encapsulating a semi-structured data, such as a file or directory.
75
76
76
-
**Stream**_object_
77
-
ADO 2.5 also introduces the **Stream** object to represent a stream of binary or text data.
77
+
**Stream**_object_
78
+
ADO 2.5 also introduces the *and*Stream** object to represent a stream of binary or text data.
78
79
79
-
*URL binding*
80
-
ADO 2.5 introduces the use of a URL, as an alternative to a connection string and command text, to name data store objects. A URL can be used with the existing **Connection** and **Recordset** objects, as well as with the new **Record** and **Stream** objects.
80
+
*URL binding*
81
+
ADO 2.5 introduces the use of a URL, as an alternative to a connection string and command text, to name data store objects. A URL can be used with the existing **Connection** and **Recordset** objects, as well as with the new **Record** and **Stream** objects.
81
82
82
-
*Data providers supporting URL binding*
83
-
ADO 2.5 supports OLE DB providers that recognize the URL schemes. This includes OLE DB Provider for Internet Publishing, which accesses the Windows 2000 file system and recognizes the existing HTTP scheme.
83
+
*Data providers supporting URL binding*
84
+
ADO 2.5 supports OLE DB providers that recognize the URL schemes. This includes OLE DB Provider for Internet Publishing, which accesses the Windows 2000 file system and recognizes the existing HTTP scheme.
-[ADO Extensions for Data Definition Language and Security (ADOX)](../../ado/guide/extensions/ado-extensions-for-data-definition-language-and-security-adox.md)
30
+
-[ADO Extensions for Data Definition Language and Security (ADOX)](./extensions/ado-extensions-for-data-definition-language-and-security-adox.md)
0 commit comments