Greetings
I am going to preface this by stating that I have probably created this problem by mixing versions or CR. I am developing new reports for a ASP.net application using CR9 Advanced edition. I have been using this edition for the past several months. My app has over 300 reports that have been created in versions 7-9 over the past several years but all are upgraded to .net or version 9.2. All are created using OLEDB against SQL Server 2000. My server is running CR for visual Studio .net.
The problem which I have just start seeing in the past week involves a new report created in version 9 which contains several sub reports. All reports use stored procedures but some of the subs go directly against the tables. After the application runs for a few hours and a certian report is hit I notice sleeping connections in SQL server begin to pile up. (can be 50 by end of the day) When I look at the connections they all contain the same statement which is the last Sql executed by the sub report. I tried creating a stored procedure for the sub but get the same results. The report in question has four subs but it is always the last sub which leaves the connection hanging. The reports executes as expected and the user gets all data. The app processes 2-3K reports per day and all others clean up as they should.
Has anyone elese noticed this behavior or have any ideas what to look for. The connection data in the report looks the same as all other reports. I can reporduce the effect with another report built with multiple sub reports.
I am going to try installing CR9 advanced on a server next and changing the app to use this version to see if the problem goes away.
Thanks
Regards
Chuck LaRue
ADRS Computer Services
I am going to preface this by stating that I have probably created this problem by mixing versions or CR. I am developing new reports for a ASP.net application using CR9 Advanced edition. I have been using this edition for the past several months. My app has over 300 reports that have been created in versions 7-9 over the past several years but all are upgraded to .net or version 9.2. All are created using OLEDB against SQL Server 2000. My server is running CR for visual Studio .net.
The problem which I have just start seeing in the past week involves a new report created in version 9 which contains several sub reports. All reports use stored procedures but some of the subs go directly against the tables. After the application runs for a few hours and a certian report is hit I notice sleeping connections in SQL server begin to pile up. (can be 50 by end of the day) When I look at the connections they all contain the same statement which is the last Sql executed by the sub report. I tried creating a stored procedure for the sub but get the same results. The report in question has four subs but it is always the last sub which leaves the connection hanging. The reports executes as expected and the user gets all data. The app processes 2-3K reports per day and all others clean up as they should.
Has anyone elese noticed this behavior or have any ideas what to look for. The connection data in the report looks the same as all other reports. I can reporduce the effect with another report built with multiple sub reports.
I am going to try installing CR9 advanced on a server next and changing the app to use this version to see if the problem goes away.
Thanks
Regards
Chuck LaRue
ADRS Computer Services