Re: Connection Pooling

Any idea where and how we can limit the number of connections to SQL
Server ? Lets say a request comes for accessing the database and all
the connections are in use. The request needs to wait until a
connection is dropped so it can use it. The idea is to limit the number
of connections to the database to some value for example 5 or 10 etc.
at any point.
Phani


Karl Seguin [MVP] wrote:
> Looks like you have it right :)
>
> Karl
>
> --
> MY ASP.Net tutorials
> http://www.openmymind.net/
>
>
> "Not Me" <not.me@xxxxxxxxxxxx> wrote in message
> news:dr5i34$s1h$1@xxxxxxxxxxxxxxxxxxxx
> > Karl Seguin [MVP] wrote:
> >> Yes, that's what I mean when I say SQL authentication (SQL Server has
> >> it's own authentication capabilities as well as using windows
> >> username/password). I'm not sure which is more secure.
> >>
> >> What I can tell you is:
> >>
> >> If you are using Windows Authentication you may or not has a problem.
> >>
> >> If you are using Windows Authentication with ASP.NET impersonation turned
> >> on, then I don't believe pooling will happen. you can find out by going
> >> into the web.config. If this is a public internet site, then you don't
> >> have impersonation turne don. If it's a private intranet site where all
> >> users are on the same domain, it's possible that you are using
> >> impersonation.
> >>
> >> If you are using Windows Authentication with ASP.NTE impersonation turned
> >> OFF, then pooling will happen. This simply means that you've granted the
> >> ASP.NET account access to your sql server and that each connection will
> >> be made by the ASP.NET account (thus enabling pooling). In the case
> >> mentioned above, the creditials for each request is based on the server,
> >> so if 10 different people access the site, then you'll have 10 different
> >> pools - no ideal.
> >
> > Thanks for trying to clear this up.. so is ASP.net impersonation where it
> > takes the credentials of the machine that is trying to access the page,
> > and uses those details to authenticate against the sql server? This will
> > be a public site so I'm not interested in that.. so hopefully there
> > shouldn't be any issues with the pooling.
> >
> > cheers,
> > Chris

.

Relevant Pages

  • Access 2007->SQL Server2005 "connection was forcibly closed",GNE 1
    ... I have a very big problem connecting an SQL ... changing number of clients using the SQL Server with this frontend at the ... connection pooling or if these connections are separated connections). ...
    (microsoft.public.sqlserver.connect)
  • Re: Q: Named pipes and Windows (integrated) authentication
    ... >By the way, if you don't have SQL Enterprise Manager, there's an MSDE ... >>>his windows authentication to connect to the server. ... >>>Creating databases is only acomplished after you've already connected. ...
    (microsoft.public.sqlserver.connect)
  • Re: What happened with my rows?
    ... session and kills off any connections that are still hanging around, the SQL ... Server automatically performs a ROLLBACK on all uncommitted transactions ...
    (microsoft.public.sqlserver.programming)
  • Re: balancing connections - any idea ?
    ... We are going to add another web server. ... too many connections on the database. ... Links for SQL Server Books Online: ...
    (comp.databases.ms-sqlserver)
  • Re: SQL Server 2005 Express Connection
    ... configuration issues with named pipes and tcp/ip connections. ... An error has ocurred while establishing a connection to the server. ... When connecting to SQL 2005, this failure may be caused by the fact ... that under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.sqlserver.connect)
Loading