Is it possible - Data Access Layer

[Bernardo Heynemann]

I have multiple users accessing my database at all times.
As i am using today, i have one connection that serves all users (ASP 3.0
Application object).
This works fine since i´m using an oracle database server.
The problem is when there are too many concurrent data requests (selects)
some users get timeouts, since oracle uses a queue for each connection.

Then the first 10 users get their request, but the 11th one gets a timeout
(example).

I want to do a Threaded Data Access Layer in .NET that works at ASP 3.0, VB
6.0 or .NET.

It should work this way:
-When the first user requests data, it creates a thread with a connection.
-The N (parameter) following users go to this thread also.
-When the (n+1) user requests data he should be redirected to the second
thread with another connection.
-If there´s an open spot at any of the previous threads the user should be
redirected to that spot in spite of creating a new thread.

Any hints, sugestions, code would be a LOT useful.

Thanx to all,
Bernardo Heynemann
Developer @ Banco BVA S/A - Rio de Janeiro - Brazil

[David Browne]

Re: Is it possible - Data Access Layer


"Bernardo Heynemann" <bernardo@banco bva.com.br> wrote in message
news:eYjIzRIqDH A.1724@TK2MSFTN GP10.phx.gbl...[color=blue]
> I have multiple users accessing my database at all times.[/color]
.. . .

Don't multi-post.

See thread in .adonet.

David

[Bernardo Heynemann]

Re: Is it possible - Data Access Layer

Sorry, i didn´t mean to...
I tought my message wasn´t posted in ado.net.

Won´t happen again.

Thanx,
Bernardo Heynemann
"David Browne" <davidbaxterbro wne no potted meat@hotmail.co m> escreveu na
mensagem news:%239MYQcIq DHA.2588@tk2msf tngp13.phx.gbl. ..[color=blue]
>
> "Bernardo Heynemann" <bernardo@banco bva.com.br> wrote in message
> news:eYjIzRIqDH A.1724@TK2MSFTN GP10.phx.gbl...[color=green]
> > I have multiple users accessing my database at all times.[/color]
> . . .
>
> Don't multi-post.
>
> See thread in .adonet.
>
> David
>
>[/color]

[Joerg Jooss]

Re: Is it possible - Data Access Layer

"Bernardo Heynemann" wrote:
[color=blue]
> I have multiple users accessing my database at all times.
> As i am using today, i have one connection that serves all users
> (ASP 3.0 Application object).
> This works fine since i´m using an oracle database server.
> The problem is when there are too many concurrent data requests
> (selects) some users get timeouts, since oracle uses a queue for
> each connection.
>
> Then the first 10 users get their request, but the 11th one gets a
> timeout (example).
>
> I want to do a Threaded Data Access Layer in .NET that works at ASP
> 3.0, VB 6.0 or .NET.
>
> It should work this way:
> -When the first user requests data, it creates a thread with a
> connection. -The N (parameter) following users go to this thread
> also. -When the (n+1) user requests data he should be redirected to
> the second thread with another connection.
> -If there´s an open spot at any of the previous threads the user
> should be redirected to that spot in spite of creating a new thread.
>
> Any hints, sugestions, code would be a LOT useful.[/color]

All you really need is a connection pool. Bn the same token, thread
management really belongs into the application server, not application
code.

Cheers,
--
Joerg Jooss
joerg.jooss@gmx .net