Re: Monitoring Connections
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Sat, 6 Aug 2005 12:58:54 -0400
You can use sp_who2 to see how many connections are currently existing and
who belongs to each. It will also show status of each connection as well
but since it is a snap shot it may not be truly indicative of the overall
connection. But you should be able to get an idea of if the GCI app has too
many open connections or not at any particular time.
--
Andrew J. Kelly SQL MVP
"Charlie" <Charlie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A5FF4C6F-9E19-4B26-A070-4C0001F4C3EA@xxxxxxxxxxxxxxxx
> Greetings,
>
> I have a CGI web application that is connecting to SQL2k sp3 server using
> a
> system ODBC DSN to display data from tables on a web page.
>
> These tables are being populated by another application that is using .net
> SqlConnection object to insert data.
>
> The problem I am seeing is that after a period of time the .net
> application
> can no longer open a connection to the database. I believe this may be
> because the connections that the CGI application is useing are not being
> properly closed. When I use sp_monitor, I can see the number of
> Connections
> increase each time the CGI application fires. My question here is:
>
> -The BOL indicates that the connections field shown in the results from
> sp_monitor show the 'number of logins or attempted logins'. It is kind of
> difficult for me to understand from this whether or not I am correct in my
> feeling that the CGI application is not closing the ODBC connections. For
> instance, do 'attempted logins' count against the number of 'connections'
> allowed?
>
> Ive also opened a trace using Profiler and I note an Audit logout event
> for
> each Audit Login event that occurs by the CGI Applicaiton, but how can I
> know
> whether this connection has been properly closed so that I can predict
> whether SQL Server will eventually prevent the .net application from
> connecting to insert new data?
>
> This instance in licensed by processor, by the way...
>
> TIA
>
.
- Follow-Ups:
- Re: Monitoring Connections
- From: Charlie
- Re: Monitoring Connections
- References:
- Monitoring Connections
- From: Charlie
- Monitoring Connections
- Prev by Date: Monitoring Connections
- Next by Date: Strange DNS failure
- Previous by thread: Monitoring Connections
- Next by thread: Re: Monitoring Connections
- Index(es):
Relevant Pages
|
