IWS_Training_Guide_v.. - FF-Automation

Contents
IWS Training Guide
Another consideration is the ADO.NET Provider to use. Several ADO.NET Providers are included with the
Microsoft Operating System (e.g. Windows XP, 2000, Server 2003, or Vista) or the ADO.NET Provider may
come from a 3 rd party. Some ADO.NET Providers provide connect directly to the database (usually for higher
performance), while others connect to the Microsoft JET OLE-DB Provider or to ODBC. The following contains
a partial list of ADO.NET Data Providers:
ADO.NET Provider Database Supported Source
.NET for SQL Server*
Microsoft SQL Server
Microsoft
(Version 7 or later)
.NET for Oracle
Oracle
Microsoft
(Oracle Client 8.1.7 or later)
.NET for OLE-DB (SQLOLEDB)* Microsoft SQL Server
Microsoft
(Prior to Version 7)
.NET for OLE-DB (MSDAORA)* Oracle
Microsoft
(Oracle Client prior to 8.1.7)
.NET for OLE-DB (Jet 4.0)* Microsoft Access, Excel, CSV Microsoft
.NET for ODBC with SQL Server Microsoft SQL Server
Microsoft
Driver
.NET for ODBC with Oracle Driver Oracle Microsoft
.NET for ODBC with Access Driver Microsoft Access
Microsoft
Download Connector/Net 1.0 MySQL (.NET 1.1) www.mysql.com
Download Connector/Net 5.0 MySQL (.NET 2.0) www.mysql.com
* Required MDAC 2.6 or later
Notes:
• Use the .NET Framework Data Provider for SQL Server if using SQL Server version 7.0 or later
• Use the .NET Framework Data Provider for OLE-DB when using SQL Server 6.5 or earlier, or a singletiered
Microsoft Access database. Using Access for middle-tiered applications is not recommended.
• Use the .NET Framework Data Provider for ODBC for single-tiered and middle-tiered applications that
use ODBC data sources. Note that the ODBC Data Provider was not provided with .NET Framework
version 1.0, but can be downloaded from the Microsoft website at
http://msdn.microsoft.com/downloads.
• Use the .NET Framework Data Provider for Oracle with single-tier and middle-tier applications using
Oracle client software 8.1.17 and later.
• Using a Microsoft Access database (with the Jet engine) as a data source for multi-threaded
applications is not recommended. Microsoft recommends using SQL Server instead.
• If you use Microsoft Excel as a database, you may want to periodically compact the database.
• Microsoft recommends using the direct .NET Providers for SQL Server and Oracle when possible
(based on the version of SQL Server or Oracle being used). These direct .NET Providers have a direct
interface into the respective database and have been optimized for performance. These .NET
Providers do not use OLE-DB or ODBC. This was done to improve transactional efficiency required by
high-demand database server applications
• In addition to Data Providers, Service Providers may be available from Database suppliers. Examples
of Service Providers include:
- Persistence Provider: allows saving of rowset data and metadata to a local file
- Remoting Provider: allows access to remote databases
• Microsoft has announced that they will be “deprecating” (obsoleting) certain legacy database
interfaces, although they are still supported in the current MDAC release (MDAC 2.8). Microsoft wants
you to use ADO.NET instead. The deprecated interfaces include:
- ODBC Provider (MSDASQL)
- Remote Data Services (RDS) Use SOAP instead
- JET DAO (Data Access Objects) and Jet Replication Objects (JRO)
InduSoft Web Studio 19–9