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,