Skip to content

Commit 5aa1208

Browse files
author
Bruce Hamilton
committed
added/updated ms.workload metadata values
1 parent da309c3 commit 5aa1208

1,019 files changed

Lines changed: 37272 additions & 36254 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/odbc/admin/about-drivers-and-data-sources.md‎

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,18 +16,19 @@ caps.latest.revision: 5
1616
author: "MightyPen"
1717
ms.author: "genemi"
1818
manager: "jhubbard"
19+
ms.workload: "On Demand"
1920
---
2021
# About Drivers and Data Sources
21-
*Drivers* are the components that process ODBC requests and return data to the application. If necessary, drivers modify an application's request into a form that is understood by the data source. You must use the driver's setup program to add or delete a driver from your computer.
22-
23-
*Data sources* are the databases or files accessed by a driver and are identified by a data source name (DSN). Use the ODBC Data Source Administrator to add, configure, and delete data sources from your system. The types of data sources that can be used are described in the following table.
24-
25-
|Data source|Description|
26-
|-----------------|-----------------|
27-
|User|User DSNs are local to a computer and can be used only by the current user. They are registered in the HKEY_CURRENT_USER registry subtree.|
28-
|System|System DSNs are local to a computer rather than dedicated to a user. The system or any user with privileges can use a data source set up with a system DSN. System DSNs are registered in the HKEY_LOCAL_MACHINE registry subtree.|
29-
|File|File DSNs are file-based sources that can be shared among all users who have the same drivers installed and therefore have access to the database. These data sources need not be dedicated to a user nor be local to a computer. File data source names are not identified by dedicated registry entries; instead, they are identified by a file name with a .dsn extension.|
30-
31-
User and system data sources are collectively known as *machine* data sources because they are local to a computer.
32-
33-
Each of these data sources has a tab in the **ODBC Data Source Administrator** dialog box. For more information about data sources, see [Data Sources](../../odbc/reference/data-sources.md).
22+
*Drivers* are the components that process ODBC requests and return data to the application. If necessary, drivers modify an application's request into a form that is understood by the data source. You must use the driver's setup program to add or delete a driver from your computer.
23+
24+
*Data sources* are the databases or files accessed by a driver and are identified by a data source name (DSN). Use the ODBC Data Source Administrator to add, configure, and delete data sources from your system. The types of data sources that can be used are described in the following table.
25+
26+
|Data source|Description|
27+
|-----------------|-----------------|
28+
|User|User DSNs are local to a computer and can be used only by the current user. They are registered in the HKEY_CURRENT_USER registry subtree.|
29+
|System|System DSNs are local to a computer rather than dedicated to a user. The system or any user with privileges can use a data source set up with a system DSN. System DSNs are registered in the HKEY_LOCAL_MACHINE registry subtree.|
30+
|File|File DSNs are file-based sources that can be shared among all users who have the same drivers installed and therefore have access to the database. These data sources need not be dedicated to a user nor be local to a computer. File data source names are not identified by dedicated registry entries; instead, they are identified by a file name with a .dsn extension.|
31+
32+
User and system data sources are collectively known as *machine* data sources because they are local to a computer.
33+
34+
Each of these data sources has a tab in the **ODBC Data Source Administrator** dialog box. For more information about data sources, see [Data Sources](../../odbc/reference/data-sources.md).

‎docs/odbc/admin/managing-data-sources.md‎

Lines changed: 26 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -20,30 +20,31 @@ caps.latest.revision: 11
2020
author: "MightyPen"
2121
ms.author: "genemi"
2222
manager: "jhubbard"
23+
ms.workload: "On Demand"
2324
---
2425
# Managing Data Sources
25-
After you have installed an ODBC driver from the driver's setup program, you can define one or more data sources for it. The data source name (DSN) should provide a unique description of the data; for example, *Payroll* or *Accounts Payable*. The user and system data sources that are defined for all currently installed drivers are listed in the **User DSN** or **System DSN** tabs of the **ODBC Data Source Administrator** dialog box. The file data sources in a given directory are listed in the **File DSN** tab; the directory to be shown is entered in the **Look in** box in the **File DSN** tab.
26-
27-
> [!NOTE]
28-
> To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe. To manage a data source that connects to a 64-bit driver, use c:\windows\system32\odbcad32.exe. In **Administrative Tools** on a 64-bit Windows 8 operating system, there are icons for both the 32-bit and 64-bit **ODBC Data Source Administrator** dialog box.
29-
30-
If you use the 64-bit odbcad32.exe to configure or remove a DSN that connects to a 32-bit driver, for example, **Driver do Microsoft Access (\*.mdb)**, you will receive the following error message:
31-
32-
```
33-
The specified DSN contains an architecture mismatch between the Driver and Application
34-
```
35-
36-
To resolve this error, use the 32-bit odbcad32.exe to configure or remove the DSN.
37-
38-
A data source associates a particular ODBC driver with the data you want to access through that driver. For example, you might create a data source to use the ODBC dBASE driver to access one or more dBASE files found in a specific directory on your hard disk or a network drive. Using the ODBC Data Source Administrator, you can add, modify, and delete data sources, as described in the following table.
39-
40-
|Action|Description|
41-
|------------|-----------------|
42-
|Adding data sources|It is possible to add multiple data sources, each one associating a driver with some data you want to access by using that driver. Give each data source a name that uniquely identifies that data source. For example, if you create a data source for a set of dBASE files that contain customer information, you might name the data source "Customers." Applications typically display data source names for users to choose from.<br /><br /> Adding a file data source is slightly different from adding user or system data sources. For more information, see the ODBC Data Source Administrator help file.|
43-
|Modifying data sources|Depending on your requirements, you might find it necessary to reconfigure data sources. You can reset options by clicking **Configure** in any driver setup dialog box.|
44-
|Deleting data sources|Click **Remove** after selecting a data source.|
45-
46-
For more information about file data sources, see [Connecting Using File Data Sources](../../odbc/reference/develop-app/connecting-using-file-data-sources.md) or the [SQLDriverConnect Function](../../odbc/reference/syntax/sqldriverconnect-function.md).
47-
48-
## See Also
49-
[ODBC Data Source Administrator](../../odbc/admin/odbc-data-source-administrator.md)
26+
After you have installed an ODBC driver from the driver's setup program, you can define one or more data sources for it. The data source name (DSN) should provide a unique description of the data; for example, *Payroll* or *Accounts Payable*. The user and system data sources that are defined for all currently installed drivers are listed in the **User DSN** or **System DSN** tabs of the **ODBC Data Source Administrator** dialog box. The file data sources in a given directory are listed in the **File DSN** tab; the directory to be shown is entered in the **Look in** box in the **File DSN** tab.
27+
28+
> [!NOTE]
29+
> To manage a data source that connects to a 32-bit driver under 64-bit platform, use c:\windows\sysWOW64\odbcad32.exe. To manage a data source that connects to a 64-bit driver, use c:\windows\system32\odbcad32.exe. In **Administrative Tools** on a 64-bit Windows 8 operating system, there are icons for both the 32-bit and 64-bit **ODBC Data Source Administrator** dialog box.
30+
31+
If you use the 64-bit odbcad32.exe to configure or remove a DSN that connects to a 32-bit driver, for example, **Driver do Microsoft Access (\*.mdb)**, you will receive the following error message:
32+
33+
```
34+
The specified DSN contains an architecture mismatch between the Driver and Application
35+
```
36+
37+
To resolve this error, use the 32-bit odbcad32.exe to configure or remove the DSN.
38+
39+
A data source associates a particular ODBC driver with the data you want to access through that driver. For example, you might create a data source to use the ODBC dBASE driver to access one or more dBASE files found in a specific directory on your hard disk or a network drive. Using the ODBC Data Source Administrator, you can add, modify, and delete data sources, as described in the following table.
40+
41+
|Action|Description|
42+
|------------|-----------------|
43+
|Adding data sources|It is possible to add multiple data sources, each one associating a driver with some data you want to access by using that driver. Give each data source a name that uniquely identifies that data source. For example, if you create a data source for a set of dBASE files that contain customer information, you might name the data source "Customers." Applications typically display data source names for users to choose from.<br /><br /> Adding a file data source is slightly different from adding user or system data sources. For more information, see the ODBC Data Source Administrator help file.|
44+
|Modifying data sources|Depending on your requirements, you might find it necessary to reconfigure data sources. You can reset options by clicking **Configure** in any driver setup dialog box.|
45+
|Deleting data sources|Click **Remove** after selecting a data source.|
46+
47+
For more information about file data sources, see [Connecting Using File Data Sources](../../odbc/reference/develop-app/connecting-using-file-data-sources.md) or the [SQLDriverConnect Function](../../odbc/reference/syntax/sqldriverconnect-function.md).
48+
49+
## See Also
50+
[ODBC Data Source Administrator](../../odbc/admin/odbc-data-source-administrator.md)

‎docs/odbc/admin/odbc-data-source-administrator.md‎

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -17,22 +17,23 @@ caps.latest.revision: 10
1717
author: "MightyPen"
1818
ms.author: "genemi"
1919
manager: "jhubbard"
20+
ms.workload: "Active"
2021
---
2122
# ODBC Data Source Administrator
22-
The Microsoft® ODBC Data Source Administrator manages database drivers and data sources. This application is located in the Windows Control Panel under **Administrative Tools**. Beginning in Windows 8, the icon is named **ODBC Data Sources**, and on 64-bit operating systems there is a 32-bit and 64-bit version.
23-
24-
For information about detailed ODBC Administrator procedures, open the [ODBC Data Source Administrator](http://msdn.microsoft.com/en-us/eea94d94-f53b-4289-ae75-9ccccde15333) dialog box and click **Help**.
25-
26-
You can use PowerShell commands to manage drivers and data sources. For more information about these PowerShell commands, see [Windows Data Access Components PowerShell commands](https://msdn.microsoft.com/library/windows/desktop/jj134064.aspx).
27-
28-
This section contains the following topics.
29-
30-
- [About Drivers and Data Sources](../../odbc/admin/about-drivers-and-data-sources.md)
31-
32-
- [Managing Data Sources](../../odbc/admin/managing-data-sources.md)
33-
34-
- [Setting Tracing Options](../../odbc/admin/setting-tracing-options.md)
35-
36-
- [Setting ODBC Connection Pooling Options](../../odbc/admin/setting-odbc-connection-pooling-options.md)
37-
38-
- [Viewing Drivers](../../odbc/admin/viewing-drivers.md)
23+
The Microsoft® ODBC Data Source Administrator manages database drivers and data sources. This application is located in the Windows Control Panel under **Administrative Tools**. Beginning in Windows 8, the icon is named **ODBC Data Sources**, and on 64-bit operating systems there is a 32-bit and 64-bit version.
24+
25+
For information about detailed ODBC Administrator procedures, open the [ODBC Data Source Administrator](http://msdn.microsoft.com/en-us/eea94d94-f53b-4289-ae75-9ccccde15333) dialog box and click **Help**.
26+
27+
You can use PowerShell commands to manage drivers and data sources. For more information about these PowerShell commands, see [Windows Data Access Components PowerShell commands](https://msdn.microsoft.com/library/windows/desktop/jj134064.aspx).
28+
29+
This section contains the following topics.
30+
31+
- [About Drivers and Data Sources](../../odbc/admin/about-drivers-and-data-sources.md)
32+
33+
- [Managing Data Sources](../../odbc/admin/managing-data-sources.md)
34+
35+
- [Setting Tracing Options](../../odbc/admin/setting-tracing-options.md)
36+
37+
- [Setting ODBC Connection Pooling Options](../../odbc/admin/setting-odbc-connection-pooling-options.md)
38+
39+
- [Viewing Drivers](../../odbc/admin/viewing-drivers.md)

‎docs/odbc/admin/setting-odbc-connection-pooling-options.md‎

Lines changed: 22 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -18,26 +18,27 @@ caps.latest.revision: 10
1818
author: "MightyPen"
1919
ms.author: "genemi"
2020
manager: "jhubbard"
21+
ms.workload: "On Demand"
2122
---
2223
# Setting ODBC Connection Pooling Options
23-
Connection pooling enables an application to use a connection from a pool of connections that do not need to be reestablished for each use. You can use the **Connection Pooling** tab of the **ODBC Data Source Administrator** dialog box to enable and disable performance monitoring. Double-click a driver name to set the connection time-out period.
24-
25-
At the driver level, connection pooling is enabled by the CPTimeout registry value. This selective per-driver enabling allows a system administrator to enable connection pooling for just the drivers that can support it. It is accomplished by setting the default value of CPTimeout during the driver's setup program. Double-click a driver name to set the connection time-out period.
26-
27-
For more information about connection pooling, see [ODBC Connection Pooling](../../odbc/reference/develop-app/driver-manager-connection-pooling.md).
28-
29-
## Performance Monitoring
30-
Performance monitoring tracks connection performance by recording a variety of statistics. These statistics can be customized by the developer to include items such as the following:
31-
32-
|Counter|Definition|
33-
|-------------|----------------|
34-
|ODBC Hard Connection Counter per Second|The number of actual connections per second that are made to the server. The first time your environment carries a heavy load, this counter will go up very quickly. After a few seconds, it will drop to zero. This is the normal situation when connection pooling is working. When the connections to the server have been established, they will be used and placed in the pool for reuse.|
35-
|ODBC Hard Disconnect Counter per Second|The number of hard disconnects per second issued to the server. These are actual connections to the server that are being released by connection pooling. This value will increase from zero when you stop all clients on the system and the connections start to time out.|
36-
|ODBC Soft Connection Counter per Second|The number of connections satisfied by the pool per second—in other words, connections from that pool that were handed to users. This counter indicates whether pooling is working. Depending on the load on your server, it is not uncommon for this to show 40–60 soft connections per second.|
37-
|ODBC Soft Disconnection Counter per Second|The number of disconnects per second issued by the applications. When the application releases or disconnects, the connection is placed back in the pool.|
38-
|ODBC Current Active Connection Counter|The number of connections in the pool that are currently in use.|
39-
|ODBC Current Free Connection Counter|The current number of free connections available in the pool. These are live connections that are available for use.|
40-
|Pools Currently Active|The number of pools currently active. This counter was added in Windows 8, for drivers that manage connections in the connection pool. For more information, see [Driver-Aware Connection Pooling](../../odbc/reference/develop-app/driver-aware-connection-pooling.md).|
41-
|Pools Created|The number of pools active, including active and removed pools. This counter was added in Windows 8, for drivers that manage connections in the connection pool. For more information, see [Driver-Aware Connection Pooling](../../odbc/reference/develop-app/driver-aware-connection-pooling.md).|
42-
43-
You must specify your own monitoring parameters. Samples for performance monitoring have been included with this version of ODBC.
24+
Connection pooling enables an application to use a connection from a pool of connections that do not need to be reestablished for each use. You can use the **Connection Pooling** tab of the **ODBC Data Source Administrator** dialog box to enable and disable performance monitoring. Double-click a driver name to set the connection time-out period.
25+
26+
At the driver level, connection pooling is enabled by the CPTimeout registry value. This selective per-driver enabling allows a system administrator to enable connection pooling for just the drivers that can support it. It is accomplished by setting the default value of CPTimeout during the driver's setup program. Double-click a driver name to set the connection time-out period.
27+
28+
For more information about connection pooling, see [ODBC Connection Pooling](../../odbc/reference/develop-app/driver-manager-connection-pooling.md).
29+
30+
## Performance Monitoring
31+
Performance monitoring tracks connection performance by recording a variety of statistics. These statistics can be customized by the developer to include items such as the following:
32+
33+
|Counter|Definition|
34+
|-------------|----------------|
35+
|ODBC Hard Connection Counter per Second|The number of actual connections per second that are made to the server. The first time your environment carries a heavy load, this counter will go up very quickly. After a few seconds, it will drop to zero. This is the normal situation when connection pooling is working. When the connections to the server have been established, they will be used and placed in the pool for reuse.|
36+
|ODBC Hard Disconnect Counter per Second|The number of hard disconnects per second issued to the server. These are actual connections to the server that are being released by connection pooling. This value will increase from zero when you stop all clients on the system and the connections start to time out.|
37+
|ODBC Soft Connection Counter per Second|The number of connections satisfied by the pool per second—in other words, connections from that pool that were handed to users. This counter indicates whether pooling is working. Depending on the load on your server, it is not uncommon for this to show 40–60 soft connections per second.|
38+
|ODBC Soft Disconnection Counter per Second|The number of disconnects per second issued by the applications. When the application releases or disconnects, the connection is placed back in the pool.|
39+
|ODBC Current Active Connection Counter|The number of connections in the pool that are currently in use.|
40+
|ODBC Current Free Connection Counter|The current number of free connections available in the pool. These are live connections that are available for use.|
41+
|Pools Currently Active|The number of pools currently active. This counter was added in Windows 8, for drivers that manage connections in the connection pool. For more information, see [Driver-Aware Connection Pooling](../../odbc/reference/develop-app/driver-aware-connection-pooling.md).|
42+
|Pools Created|The number of pools active, including active and removed pools. This counter was added in Windows 8, for drivers that manage connections in the connection pool. For more information, see [Driver-Aware Connection Pooling](../../odbc/reference/develop-app/driver-aware-connection-pooling.md).|
43+
44+
You must specify your own monitoring parameters. Samples for performance monitoring have been included with this version of ODBC.

0 commit comments

Comments
 (0)