Asp.net performence Issue

Question

3.67/5 (3 votes)

See more:

Dear Friends

we r using asp.net3.5 and sqlserver2008

We run 2003 Server SP2 with IIS 6.0. Our box has (2)CPU's, and 8 GB of RAM.

Under normal load we have about 100 users accessing our web site.
Under 'peak' load we have about 300 users, and our server is holding us back.

During peak load, the site becomes unresponsive and very slow or Not given proper response and throwing errors like

'Column not found' Or
'Table not found' Or

Application does't returns any Records and some time returns records but not according to our searching criteria.

Regards
Arvind

Posted 16-Dec-09 20:48pm

limba

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Aman Bhullar · Accepted Answer · 2009-12-16T21:23:00

Hi
we also faced the same problem.

Below are the commands that helped to solve the problem.
In our case the first command solved the problem.

ALTER DATABASE <Database Name>
SET READ_COMMITTED_SNAPSHOT ON;

ALTER DATABASE <Database Name>
SET ALLOW_SNAPSHOT_ISOLATION ON;

Note:
1. Do read/study the both commands in MSDN before execution
2. Make sure, your database should not be in use when you fire the commands.