Hi,



I started ASP about 6 months ago, learning by example - form a guy who 

used ODBC connections.



Now, after 'beginning ASP 3.0' and 6 months of varying experience, I've 

reached bigger sites that potentially require many simultaneous 

connections.



Q1: I've been using ACCESS since it is readilly available to me. What 

other solutions should I be looking into?  Would exporting the Access db 

into some other format archieve any benefit?



Q2: Does anybody know factually how many connections are supported by 

ODBC , OLE DB , MSDE & SQL ? (I gather ACCESS supports 256 simultaneous)



I've read many statements: 



Microsoft suggest OLE DB is more performant and has less bugs than ODBC.



My Wrox book,(above mentioned), page 776-7 - implies that MSDE is more 

performant than Jet based solutions.



Q3: Is the following performance order correct? If so, then why would use 

OLE DB or ODBC ??



More performant to less -> SQL, MSDE, OLE DB, ODBC. 



Many, many thanks for any replies.



Luis.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From: "Luis Sanches" <p2p.wrox@s...>

Subject: [access_asp] ODBC - OLE DB - MSDE - SQL ??





: Q1: I've been using ACCESS since it is readilly available to me. What

: other solutions should I be looking into?  Would exporting the Access db

: into some other format archieve any benefit?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Access uses the Jet database engine. The Jet engine was never designed as

anything more than a single user desktop database engine. If you want to

develop larger, multi-user databases, look at something like:

mySQL or FoxPro for medium sized sites, or Microsoft's SQL Server or

Oracle's Oracle 9i for larger sites.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: Q2: Does anybody know factually how many connections

: are supported by ODBC , OLE DB , MSDE & SQL ?

: (I gather ACCESS supports 256 simultaneous)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Access/Jet supports 256 connections, though all operations are single

threaded, ie they will not be processed in parallel. This means that someone

could be waiting a long time for their operation to be performed, and their

webpage or connection might timeout before it is completed.



SQL stands for Structured Query Language, which is a language used to query

and modify database data and structures. It has no "connection limit" as

such.



ODBC and OLEDB are competing database access technologies. ODBC has been

around for longer, but only works with relational data. OLEDB is Microsoft's

newer data access technology and has been designed to work with

non-relational data like Exchange Server catalogs, directories like AD and

so forth, in addition to normal relational data.



MSDE uses the same database engine as Microsoft's SQL Server product, but it

is deliberately engineered to degrade performance wise as soon as a certain

number of connections is reached.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: Microsoft suggest OLE DB is more performant and has less bugs than ODBC.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



OLEDB is a newer technology that Microsoft is pushing as the future of data

access.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: My Wrox book,(above mentioned), page 776-7 - implies that MSDE is more

: performant than Jet based solutions.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



That is correct.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

: Q3: Is the following performance order correct? If so, then why would use

: OLE DB or ODBC ??

:

: More performant to less -> SQL, MSDE, OLE DB, ODBC.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



 Please see answers above.



Cheers

Ken