Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian
"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/com...si1203.mspx#EB
AA
Regards
JTC ^..^
|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases.
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>
|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/co...isi1203.mspx#EB
AA
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases.
_0ciq.asp" target="_blank">http://msdn.microsoft.com/library/d...r />
_0ciq.asp
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that acces
s
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The onl
y
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
_0ciq.asp" target="_blank">http://msdn.microsoft.com/library/d...r />
_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that acces
s
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The onl
y
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/community/columns/insider/iisi1203.mspx#EB
AA
--
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>sql

max connections pool reached

Hi,
Can anyone tell me if he ever got this issue and how he get the solution. In my asp.net 2.0 application i close always ma connexions to sqlserver in the finally clause (the open is in the try); I open 1 ou 2 connecxions per aspx page, i close them always (in the finally clause or at the bottum of the form). Sometimes, the application is down with the message
Can not open a new connexion, max pool size is reached !!!!

I host my application on a remote server, i have no performance issues, only this great problem !!!
i cant view the status of connexion on the sqlserver, so what can i do, or how shoud i develop my connection.
thanks in advance to all of yuo who will help me.
Imed.

Please visithttp://www.15seconds.com/issue/040830.htm as it has some connection pool optimization tips.

Hope that helps.

Matrix Dynamic Column problem HELP!

Ill start off by saying that I am an ASP.NET developer and I am self-taught in using SSRS2005. (quite poorly I might add) That being said I am having a problem with a report im building. This report has 10-12 different metrics I am reporting on and I have each of them displayed in their own matrix. The first matrix was created by the report wizard that launches when you add a new report.

To give you an overview of how I am setting up these reports I will describe the structure I am using on nearly all of the matrices. I am reporting on classes that are managed by my company and held at 3rd party locations. My matrix has the 3rd party location in the rows and the quarter the class was held is the column. Matrix setup looks like this:

__|_Quarter
|MetricA|MetricB|MetricC|etc...
LocationA|
LocationB|
LocationC|

The problem Im having is this. All matrices that weren't created by the wizard don't grow dynamically. Say I have 2 quarters of data I am reporting on, Instead of having a column for quarter1 and quarter 2, the report generates separate matrices for each quarter. This is true for each matrix that I created using a matrix control from the toolbox. The matrix that was created by the wizard however, has dynamic columns that grow to the right as expected.

I am populating my datasets using Stored Procedures and the matrix that behaves normally uses a different dataset than the 4 others I have completed thus far which share a dataset.

I have looked everywhere I can think of for a checkbox or a property I need to adjust and I cant find one. Anyone have any ideas?
Well it appears that I had each Matrix in its own List and I assume that there was some configuration of the list that I missed because when I took it out of the list the matrix rendered as I had intended it to. So I guess I better go read up on lists!

master..xp_fixeddrives

I saw an article about monitoring drive usage:
http://www.sqlservercentral.com/columnists/hji/monitoringdiskspaceandsendingalertswithtsql.asp
It relies on the undocumented 'master..xp_fixeddrives' extended procedure in
2000. Now, it's not documented in 2005 either, but I've been reading the
results from a technet search on 'xp_fixeddrives' and it looks like it's in
SQL Server for the long haul.
https://blogs.technet.com/mscom/archive/2007/01/18/keeping-track-of-database-capacity-monitoring-and-planning.aspx
Should I use it?Hi Jay
You could argue that if this is used for an administrative task it is not in
the scope of the critical application functionality and therefore
permissable... but on the other hand any code on a live system could be
deemed as critical!!! Bottom line the choice is up to you, if you do decide
to use it then it should be noted and documented. Any upgrades should
specifically check that this is still available and functions in the same
way. You may want to look at writing your own script such as the perl script
http://support.microsoft.com/default.aspx/kb/318762
John
"Jay" wrote:
> I saw an article about monitoring drive usage:
> http://www.sqlservercentral.com/columnists/hji/monitoringdiskspaceandsendingalertswithtsql.asp
> It relies on the undocumented 'master..xp_fixeddrives' extended procedure in
> 2000. Now, it's not documented in 2005 either, but I've been reading the
> results from a technet search on 'xp_fixeddrives' and it looks like it's in
> SQL Server for the long haul.
> https://blogs.technet.com/mscom/archive/2007/01/18/keeping-track-of-database-capacity-monitoring-and-planning.aspx
> Should I use it?
>
>