more mystery on (local) vs localhost

Hi,
There are known issues and bugs filed against the use of 'localhost'.
You should always use '(local)' in your connection string.
Is there any specific reason to use '(local)' instead of 'localhost'?
Thanks in advance,
PI
PING PING !!!
ipramod@.gmail.com wrote:
> Hi,
> There are known issues and bugs filed against the use of 'localhost'.
> You should always use '(local)' in your connection string.
> Is there any specific reason to use '(local)' instead of 'localhost'?
> Thanks in advance,
> PI

more mystery on (local) vs localhost

Hi,
There are known issues and bugs filed against the use of 'localhost'.
You should always use '(local)' in your connection string.
Is there any specific reason to use '(local)' instead of 'localhost'?
Thanks in advance,
PIPING PING !!!
ipramod@.gmail.com wrote:
> Hi,
> There are known issues and bugs filed against the use of 'localhost'.
> You should always use '(local)' in your connection string.
> Is there any specific reason to use '(local)' instead of 'localhost'?
> Thanks in advance,
> PI

more mystery on (local) vs localhost

Hi,
There are known issues and bugs filed against the use of 'localhost'.
You should always use '(local)' in your connection string.
Is there any specific reason to use '(local)' instead of 'localhost'?
Thanks in advance,
PIPING PING !!!
ipramod@.gmail.com wrote:
> Hi,
> There are known issues and bugs filed against the use of 'localhost'.
> You should always use '(local)' in your connection string.
> Is there any specific reason to use '(local)' instead of 'localhost'?
> Thanks in advance,
> PI

Monitoring Database hits

In any asp.net application, whats the simplest way to monitor how many times a page hits the database (opens and closes a connection)?

JontyMC:

In any asp.net application, whats the simplest way to monitor how many times a page hits the database (opens and closes a connection)?

If you are using a data access layer, you can write some code to log when the data is connection/executed. You can log this to a text file, or a database, or any other external data source.

monitoring connections and pooling

Hi
I have a problem with an aspnet app taking >30 seconds to
open a connection to a sql server.
Which tools could I use to monitor what connections are
open/available in the pool?
Are there any references/articles recommended using these?
Thanks
AdamIf you use OLE DB, I don't think there are any MS tools to
monitor the session pooling. If you use ODBC, you can enable
the counters for Perf Mon by following the steps in this
article:
How to Enable ODBC Connection Pooling Performance Counters
http://support.microsoft.com?id=216950
-Sue
On Wed, 13 Aug 2003 20:55:01 -0700, "adam" <adam@.twv.org>
wrote:
>Hi
>I have a problem with an aspnet app taking >30 seconds to
>open a connection to a sql server.
>Which tools could I use to monitor what connections are
>open/available in the pool?
>Are there any references/articles recommended using these?
>Thanks
>Adam|||Unfortunately I am using OLEDB from a C# web app
>--Original Message--
>If you use OLE DB, I don't think there are any MS tools
to
>monitor the session pooling. If you use ODBC, you can
enable
>the counters for Perf Mon by following the steps in this
>article:
>How to Enable ODBC Connection Pooling Performance
Counters
>http://support.microsoft.com?id=216950
>-Sue
>On Wed, 13 Aug 2003 20:55:01 -0700, "adam" <adam@.twv.org>
>wrote:
>>Hi
>>I have a problem with an aspnet app taking >30 seconds
to
>>open a connection to a sql server.
>>Which tools could I use to monitor what connections are
>>open/available in the pool?
>>Are there any references/articles recommended using
these?
>>Thanks
>>Adam
>.
>|||The problem seems to be that if a connection is request
within 2-3 minutes of the previous one, it is returned
instantly (presumably from the pool). But if it has been
more than this time, it takes 30 seconds to get one. I am
assured that the SqlServer cluster is not overloaded and
none of the other apps accessing it are having problems.
When run the same timing code on my development laptop it
obtains a connection (from a sqlserver on the same box)
in 0ms. When the same laptop tries to get one from the
production SqlServer, it takes about 32s, which leads me
to think it is a problem with the production server.
At the moment I have had to hack it so that the web app
makes a small request to the webserver every 2 mins, just
to keep a connection in the pool, so at least there is
always one connection available quickly, but this is
clearly not ideal.
How can I further elucidate the nature of this problem,
and why the server is taking so long to return a
connection.
Adam
>Hi
>I have a problem with an aspnet app taking >30 seconds
to
>open a connection to a sql server.
>
>Adam
>.
>

Monitor Connection sessions etc.

Hey all!

i've got SQL 2000 on a server with 1GB ram. JSP & CF code is accessing this server & DB's. We are finding that a lot of connections are staying persistant for a long time (especially with the JAVA Apps).

I'm currently able to monitor this using sp_who2, performance monitor and the following SQL call:

SELECT * FROM master..sysperfinfo
WHERE
(object_name = 'SQLServer:General Statistics' and counter_name = 'User Connections') OR
(object_name = 'SQLServer:Memory Manager' and counter_name = 'Connection Memory (KB)')

My questions are:

Is there a better way to monitor this?
Is there a way to terminate a session and how can i tell it's idle time?

Any performance tweaks you can offer as well would be MOST appreciated.another note here. i came into work this morning and had 108 connections to the SQL server. and it was useing abou 300KB of mem. currently it's at 103 connections and 2920 KB of mem. I've got a dual processor system with 1 GB of ram and my applications are dragging.. it only gets this way when my connections get above 100. any ideas?