ACC97: Using Microsoft Jet with IIS (222135)
The information in this article applies to:
- Microsoft Access 97
- Microsoft Internet Information Server 3.0
- Microsoft Internet Information Server 4.0
- Microsoft Internet Information Server 5.0
This article was previously published under Q222135 Advanced: Requires expert coding, interoperability, and multiuser
skills.
SUMMARY When you need unlimited users, 24x7 support, and ACID
transactions, Microsoft strongly recommends that you use Microsoft SQL Server
with Internet Information Server (IIS). Although Active Server Pages (ASP)
works with any OLEDB and ODBC-compliant database, IIS has been extensively
tested and is designed to work with Microsoft SQL Server when doing high
transaction traffic and unlimited users that can occur in an Internet
scenario.
NOTE: "ACID" is an acronym for the four properties of
transaction-processing systems: Atomicity, Consistency, Isolation, Durability.
ASP also supports using the Microsoft Jet database engine as a valid
data source. The Access ODBC Driver and Microsoft OLE DB Provider for Microsoft
Jet are not intended to be used with high-stress, high-concurrency, 24x7 server
applications, such as web, commerce, transactional, messaging servers, and so
on.
When running Microsoft Jet in an IIS environment, it is
recommended that you use the native Jet OLE DB Provider in place of the
Microsoft Access ODBC driver. The Microsoft Access ODBC driver (Jet ODBC
driver) can have stability issues due to the version of Visual Basic for
Applications that is invoked because the version is not thread safe. As a
result, when multiple concurrent users make requests of a Microsoft Access
database, unpredictable results may occur. The native Jet OLE DB Provider
includes fixes and enhancements for stability, performance, and thread pooling
(including calling a thread-safe version of Visual Basic for Applications).
Both the ODBC driver and OLE DB Provider provide a wrapper around
the Microsoft Jet database engine, which provides the core functionality of
both the Access ODBC driver and Jet OLE DB Provider. While Microsoft Jet is
consciously (and continually) updated with many quality, functional, and
performance improvements, it was not intended (or architected) for the
high-stress performance required by 24x7 scenarios, ACID transactions, or
unlimited users, that is, scenarios where there has to be absolute data
integrity or very high concurrency. Microsoft has performed very robust
Multi-User/Stress scenarios that are designed to verify functionality in the
appropriate usage space of Microsoft Jet, and addresses any issues that may be
revealed. REFERENCES For additional information about using the Microsoft Jet
database engine and the native Jet OLE DB Provider, please see the following
articles in the Microsoft Knowledge Base: 191754 How to Open Secured Microsoft Access Database In ADO 2.0 Through OLE DB
185033 Adoacc.exe Demonstrates Using ADO with MS Access 97
172403 ADOVB.exe Demonstrates How to Use ADO with Visual Basic
Information about Microsoft Jet and the native Jet
OLE DB Provider can also be found in the following documentation:
- "The Microsoft Jet Database Engine Programmer's guide (2nd
Edition)" offers extensive discussion on the tuning, usage, and limitations of
the Microsoft Jet database engine.
- The file, JOLTREAD.TXT, which ships with the products
listed in the "More Information" section earlier in this article.
| Modification Type: | Major | Last Reviewed: | 6/24/2004 |
|---|
| Keywords: | kbhowto KB222135 |
|---|
|