[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 587
  • Last Modified:

Application Pools, Pooling=false & Best practice

We have a web application that is causing dramas at the moment and we are trying to get to the bottom of it. Any help would be greatly appreciated.

Scenario:

The Server is Windows 2003 SBS running IIS6

We have created a Dedicated Application Pool for the Web App

We set and open 1 connection in the Global.asax in the Session_Start

This connection is used for creating Datatables, Sending Insert,Update,Delete SQL Strings to the database, creating Datasources for Telerik Radgrids

Everything we create, we dispose of.

Issue

After about an hour the application falls over. We recycle the App Pool and it all starts working again.

We would love some advice on how we can get to the bottom of this. Having read just about everything out there on this ...
0
lawso
Asked:
lawso
  • 2
1 Solution
 
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Youv'e read lots. In order to help we need to know what youv'e done. Not that you searched and read alot.

Thos said, roll up your sleeves case well probably get dirty.

Have you
Examined the SQL Errorlog
Examined event logs application and system
Examined IIS logs

Run performance monitor to capture OS Health
Run profiler to see whats going on in the sql.

What languages does the web use, is it a third party application (name if youre allowed to share that information), or something being developed by your firm/consultants.

Do you have any suspicious thoughts, has the application ever worked. When did it stop performing. Was there any upgrades in the application, MS patches or Servicepacks?

Please provide as much onformation you can.

Regards Marten
0
 
Ted BouskillSenior Software DeveloperCommented:
OK, you are using the wrong strategy for managing the SQL connection especially when using ADO.NET and the SQL .NET provider.

Turning off the SQL database pooling is going to kill performance and is likely causing concurrency issues when multiple pages are accessed simultaneously.

SQL connection pooling is a huge performance win and more connections that are setup concurrently and reused the better!

http://msdn.microsoft.com/en-us/library/8xx3tyca(v=vs.80).aspx

The rule of thumb with .NET connections is Open Late/Close Early and allow the connection pooling to do it's job with as few unique connection strings as possible.
0
 
lawsoAuthor Commented:
OK thanks guys

I will check all of this information and post back soon.
0
 
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Hows it going, need further assistance or is it solved?

regards Marten
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now