Asp.net web application on IIS server , its always throws SQL time out error.

Question

0.00/5 (No votes)

See more:

I have hosted ASP.Net application on IIS server , its always throws SQL time out error, web app time out exception error, takes lots of time for initial load even landing page is simple html content asp page. Tried almost all solutions found on net, but of no use.

Also this behavior has been observed at the time of SQL hangs always.
Please suggest any tips or tricks for the same.

What I have tried:

1. Wrote events in SQL Server to find time out queries list, but found that listed all
queries are simple one liner SQL queries. They are not complicated queries.
2. Improved SQL queries re written it with needed fields instead of using *.
3. Ensured proper closing of sql connection.
4. Set Command time out to zero in code.
5. Reduced size of images used in application.
6. Implemented View State - its improved speed of site loading very quickly, but
problems of hang still persist.
7. Loading .js files at last
8. Removing unnecessary/not required css, js files.
9. Rewritten hanging part of css in inline.
10. Tried posted solution on codeproject, https://www.leansentry.com/", stackiyfy.com

Doing end task for IIS process consuming 100 memory temprarory solves the issue.

Posted 4-Sep-21 21:11pm

Shivachalappa Gotur

Updated 4-Sep-21 21:46pm

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)

Wendelius · Answer 1 · 2021-09-04T21:46:00

If it's the SQL Server queries causing the delay, the key for slow queries is not the complexity. A very simple query can take a lot of time. Two main things to investigate
- Do the queries fetch unnecessary data. You went through the columns but how about the rows?
- Is proper indexing in place. Look ate the WHERE clauses of the problematic statements do you have indexes that provide quick access path to the rows, taken that your only fetching a small portion of the table
- Use Tuning advisor to see what recommendations the database has, see Start and Use the Database Engine Tuning Advisor - SQL Server | Microsoft Docs[^]