|
 |
asptoday_discuss thread: multi user at database
Message #1 by "Steven Van de Weyer" <vandeweyer.s@p...> on Tue, 2 Oct 2001 14:29:19
|
|
Hi,
I know this is a newby question, but you have to start somewhere.
What about if some people connect to your asp page at the same time...
aren't there any conflicts at the database? What if 2 users hit the
database at the sametime? Or does each session have it's own connection?
-So that there are actually several connections from your webserver to the
DB...
I have a somewhat finished applic. but I haven't tested it on multi user
usage (and I have little asp experience).
TIA, Stevie (Belgium).
BTW: for now I set my connectionstring in each page but plan to do this in
an include file (or even in sub session_onstart)
Message #2 by "Cathryn Bennett" <cbennett@n...> on Wed, 10 Oct 2001 18:29:32
|
|
Actually, the database will allow multiple connections - depending on the
database. Some databases do not really support more than a few
connections comfortably (Access), while others can support much larger
numbers of users(SQL). Of course, much of this depends on the type of
access to the database. If it's only read access, you shouldn't
experience any peformance issues - however, adding, changing and deleting
records is another issue entirely. Speed/performance can suffer if more
users are accessing the database than the software can reasonably
accomodate - but other than that, I have not experienced any problems
using Access or SQL.
Cathryn
> Hi,
>
>
> I know this is a newby question, but you have to start somewhere.
> What about if some people connect to your asp page at the same time...
> aren't there any conflicts at the database? What if 2 users hit the
> database at the sametime? Or does each session have it's own connection?
> -So that there are actually several connections from your webserver to
the
> DB...
>
> I have a somewhat finished applic. but I haven't tested it on multi user
> usage (and I have little asp experience).
>
> TIA, Stevie (Belgium).
>
> BTW: for now I set my connectionstring in each page but plan to do this
in
> an include file (or even in sub session_onstart)
>
Message #3 by "R. Sanchez" <rodrigosp@g...> on Wed, 10 Oct 2001 18:18:25 -0700 (PDT)
|
|
For the point to multi user at database, it's fine that you doing a
include file to connecting to DB, SQL Server can manage that without
big problems, only you have care the time of conection, by default is
60 seconds, you can incrementate these using :
Conn.ConnectionTimeout=(multiple of 60 seconds : 60, 120, 180 ... and
so on)
bye.
>Actually, the database will allow multiple connections - depending on the
>database. Some databases do not really support more than a few
>connections comfortably (Access), while others can support much larger
>numbers of users(SQL). Of course, much of this depends on the type of
>access to the database. If it's only read access, you shouldn't
>experience any peformance issues - however, adding, changing and deleting
>records is another issue entirely. Speed/performance can suffer if more
>users are accessing the database than the software can reasonably
>accomodate - but other than that, I have not experienced any problems
>using Access or SQL.
>
>Cathryn
>
>> Hi,
>>
>>
>> I know this is a newby question, but you have to start somewhere.
>> What about if some people connect to your asp page at the same time...
>> aren't there any conflicts at the database? What if 2 users hit the
>> database at the sametime? Or does each session have it's own connection?
>> -So that there are actually several connections from your webserver to
>the
>> DB...
>>
>> I have a somewhat finished applic. but I haven't tested it on multi user
>> usage (and I have little asp experience).
>>
>> TIA, Stevie (Belgium).
>>
>> BTW: for now I set my connectionstring in each page but plan to do this
>in
>> an include file (or even in sub session_onstart)
>
|
|
|
View Cart
