Re: Emergency! Too Busy A Connection!
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Wed, 31 Aug 2005 10:15:11 -0700
It's too bad you didn't do more research before you committed to using a
home/small office database to implement a serious application. You're trying
to deliver coal with a bicycle. Jet was never designed to be used in an ASP
environment. The problems you face now during testing will pale in
comparison to the problems you (and your customers) will face when you go
into production. It's true that a JET database file can be accessed by many
users--a number of users far less than SQL Server or any serious DBMS.
However, every aspect of the application needs to be written to take JET's
limitations into account. You can't (for example) fetch all of the rows of
the table(s) or expect the engine to perform complex JOIN operations and
still support multiple users. Actually, JET was designed to support multiple
users by permitting each user to have their own JET engine running on the
client system. In an ASP application, you have one JET database that's asked
to perform operations on its own. Because (by default) JET delays writing to
the database file until it's idle, when the load picks up it's never idle.
If you disable this feature, JET blocks all operations while writing thus
slowing down or stopping other access.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Ehsan" <Ehsan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2FC987C2-3B0A-4BB4-9C76-199059A8344D@xxxxxxxxxxxxxxxx
> Thank you guys.
>
> I can't redesign my app because it is nearly finished and everything is
> now
> designed to work with Access.
> What I really wanted was a way to understand when the connection is
> becoming
> available again. It is true that multiple threads can't load from an mdb
> database
> at the same time, but I was thinking about putting all my requests in a
> queue and
> considering them one by one. Is there anyway to see if the connection is
> availabe?
> I tried the connection's StateChanged event, but it doesn't tell me if I
> can
> continue my operation. (By the way, it seems that the connection's State
> property currently can only report whether the connection is open or
> closed,
> not anything else, is that right?)
> Thank you again.
>
.
- Follow-Ups:
- Re: Emergency! Too Busy A Connection!
- From: Ehsan
- Re: Emergency! Too Busy A Connection!
- Prev by Date: Re: I would learn ADO.NET 2.0 - There are Tutorials or online books?
- Next by Date: Re: MSDE help
- Previous by thread: Re: I would learn ADO.NET 2.0 - There are Tutorials or online books?
- Next by thread: Re: Emergency! Too Busy A Connection!
- Index(es):
Relevant Pages
|