Re: Multiple db connections

Nah, only happens with SQL Server V7 - and (let's be honest!) not always, but only when the data was physically located close (same block or something - can't quite remember).

Frank

Yong Huang wrote:

> Can you explain more about "all other users are going to see the changes
> even before the commit happens"? How can that happen? What should I do to
> make this happen? Thank you.
>
> Yong Huang
> yhuang_at_indigopool.com
>
> Graham Thornton <graham.thornton_at_ln.ssw.abbott.com> wrote in message
> news:39D1EC76.DF184052_at_ln.ssw.abbott.com...
> > bshah_at_sportsmail.com wrote:
> >
> > > Hi,
> > >
> > > We need multiple database connections for a web-server like
> > > architecture. The program we are writing is in pro*c, and we wanted to
> > > know the best (considering both cost and efficiency) to set up the
> > > connection scheme.
> > >
> > > Reading over the documentation, I see that we could use one common
> > > context, shared between threads/connections. However, this context may
> > > not be used by more than thread at a given time. This seems to be a big
> > > limitation if there are thousands of connections.
> >
> > You also run into massive locking problems. If user A is updating the EMP
> > table, then all other users are going to see the changes even before the
> > commit
> > happens. If user A subsequently chooses to rollback, all transactions
> > rollback!
> [snipped]
Received on Tue Oct 03 2000 - 13:19:48 CDT