Why asp.net app run very slow?

  • One asp.net app ORDER update back end from SQL 2008 to SQL 2012 but run very slow.

    Here is specifications:

    Web server: OS Window 2003 hold ORDER app

    ORDER Back end server: OS Window 2012, SQL 2012

    Does web server OS cause slow?

  • not enough information for us to offer more than vague things to check.

    performance tuning is a wide subject, and the tiny bit you gave us so far isn't enough to diagnose anything;

    slow is relative;

    · You seemed to imply you updated the server from 2008 to 2012? did you rebuild all indexes and update statistics on all tables with full scan (required after a version upgrade)

    · are pages timing out?

    · How much RAM is available on the server? How much is being used by SQL server?

    · How much Data is being returned? are there millions of rows, or columns with huge varbinary/image/varchar maxes being returned?·

    · Are there clustered indexes on all the tables involved?

    · Are there indexes to support the queries?

    · Are any Scalar functions used in the queries?

    · Is There a WHERE statement being used? if not...that's a table scan of all the data.

    · Are there columns that are being selected that are not used (ie a VIEW of 50 columns, but you need only three columns)

    · Are the statistics up to date?

    · Are you using catch all queries?

    · Are the WHERE statement parameters SARG-able?

    · Are any functions being used in the WHERE statement?

    · Are there any inline SELECT statements to get a a single or correlated value (i.e. ColumnName = (SELECT...)

    · Could the Indexes benefit from INCLUDE columns?

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • In addition to what Lowell said, how about identifying where the slow down is from the ASP side of things. I'd suggest looking at a tool like this[/url] to identify where the slowdowns are occurring.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply