closing the database connection

Hi all,
sorry if this is in another post - I did a few searches and found nothing.
We have a custom asp .net ui and are rendering our reports directly to pdf.
We are running sql server stored procedures to populate our reports. What I
have noticed, however, during the course of testing the reports, is that if
you look in SQL Server EM the connections (listed as .Net SQL Client
Provider) seem to stay open for quite some time. This is a concern, and I am
trying to figure out if there is a way that we can close the connection(s) as
soon as the data has been retrieved and the report populated. I believe this
must be the connection from RS directly calling the SP to populate - has
anyone else seen this?
Thanks,Perhaps you can set some timers in the rsconfig.
I've noticed that my oracle connenctions stay open relatively long to;
although it has something to do with congestion on either de DB-server or the
RS-server. I notice that when I automticly rennder a number of reports (to
make chached-reports for all parameter values) the RS-jobs sometimes heap up
and the open connections do also (although there are never more than tree
reports rendered at the same time). The problem solves itself automaticly
thoug, everything slows down and apperantly RS gets time to clean it up.
"Myles" wrote:
> Hi all,
> sorry if this is in another post - I did a few searches and found nothing.
> We have a custom asp .net ui and are rendering our reports directly to pdf.
> We are running sql server stored procedures to populate our reports. What I
> have noticed, however, during the course of testing the reports, is that if
> you look in SQL Server EM the connections (listed as .Net SQL Client
> Provider) seem to stay open for quite some time. This is a concern, and I am
> trying to figure out if there is a way that we can close the connection(s) as
> soon as the data has been retrieved and the report populated. I believe this
> must be the connection from RS directly calling the SP to populate - has
> anyone else seen this?
> Thanks,

client freezes

NEWBIE...We run a custom application that sends
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume?
What could cause this and is there a way to adjust?
Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume?
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve

client freezes

NEWBIE...We run a custom application that sends
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume'
What could cause this and is there a way to adjust?Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
--
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve

client freezes

NEWBIE...We run a custom application that sends
transactions to an SQL server over a WAN. On busy days, at
peak periods, many of the client work stations lock up and
freeze. If we leave it alone, the clients will resume
activity after 15-20 minutes. If we re-set the SQL
database, it unlocks all of the client pc's and resumes.
It seems like there is too much information being sent to
SQL and it cant handle the volume'
What could cause this and is there a way to adjust?Tom
Blocking, locks,bottlenecks.Have you looked at Performance Monitor?
CPU,Memory usage.
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||What do you mean by lock up and freeze? Are you saying the entire PC locks
up, or just a SQL Server application running on the client. I can't think of
a server side reason that would cause the entire client PC to lock up like
this. Server side blocking, waits, etc... would not be likley to do it.
If the entire PC is freezing, can you check the CPU utilization as it's
happening? Is it 100%?
Brian
"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?|||"Tom" <tomcdp@.aol.com> wrote in message
news:a32b01c4794c$8a8e3f30$a501280a@.phx.gbl...
> NEWBIE...We run a custom application that sends
> transactions to an SQL server over a WAN. On busy days, at
> peak periods, many of the client work stations lock up and
> freeze. If we leave it alone, the clients will resume
> activity after 15-20 minutes. If we re-set the SQL
> database, it unlocks all of the client pc's and resumes.
> It seems like there is too much information being sent to
> SQL and it cant handle the volume'
> What could cause this and is there a way to adjust?
Do you have database "auto grow" enabled? If so, is the db pausing to expand
the size of either the data or log portion? I've seen this setting cause
some odd client side behavior...
Steve