« Previous Next »

Thread: IIS becomes very slow and generates message - SQL Server does not exist -

Last post 10-18-2009 3:07 AM by stever@bitshop.com. 9 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (10 items)

Sort Posts:

  • 10-08-2009, 10:29 AM

    • Jvdplas
    • Not Ranked
    • Joined on 10-08-2009, 1:54 PM
    • Posts 5

    IIS becomes very slow and generates message - SQL Server does not exist -

    Hi,

    We are using a IIS 6.0 on a W2k3 machine, connecting via ODBC/TCP towards a SQLServer 2000 running on a W2k machine. The IIS 6.0 website becomes very slow and we receive messages like 'SQL Server does not exist' whenever Requests.Executing shows between 5 and 10 ( it seems more 10 then 5 ). Worth mentioning that we have the same website also running on IIS 5.0/W2K to the same SQL Server with on average the same load without any issues.

    Although we have implmemented most changes mentioned, we have not yet gained any performance.

    Which setting did we oversee ......

    J.  

    PS. We are located in NL / Hilversum and are willing to invite you if you think you are the IIS guru who can fix this issue.

    JvdPlas
    NL / H'sum
  • 10-08-2009, 11:47 AM In reply to

    • tomkmvp
    • Top 10 Contributor
    • Joined on 03-20-2003, 10:27 AM
    • Central NJ
    • Posts 6,235
    • IIS MVPs

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    What code platform are you using?  Why are you using ODBC as opposed to the native SQL Server OLEDB drivers?

    Jvdplas:
    PS. We are located in NL / Hilversum and are willing to invite you if you think you are the IIS guru who can fix this issue.

    Does that include airfare and lodging?  ; )

  • 10-08-2009, 12:30 PM In reply to

    • Jvdplas
    • Not Ranked
    • Joined on 10-08-2009, 1:54 PM
    • Posts 5

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    We are using ODBC for the "classic" ASP pages. Some parts are using OLEDB whenever ASP.Net is used. Not to mention the usage of a small number of Com-objects and a rather large amount of XML calls.

    Fares/lodging: Good point from NJ.....

    JvdPlas
    NL / H'sum
  • 10-08-2009, 3:53 PM In reply to

    • tomkmvp
    • Top 10 Contributor
    • Joined on 03-20-2003, 10:27 AM
    • Central NJ
    • Posts 6,235
    • IIS MVPs

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    Try to use OLEDB where ever you can. 

    Are you storing objects in Session or Application variables?

  • 10-08-2009, 8:37 PM In reply to

    • Jvdplas
    • Not Ranked
    • Joined on 10-08-2009, 1:54 PM
    • Posts 5

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    The OLEDB suggestion did not (yet) cross my mind. Currently testing and checking to see if our current app's are withstanding the OLEDB connection.

    No, storing objects in Session and/or Application objects is not done.

    JvdPlas
    NL / H'sum
  • 10-09-2009, 8:10 AM In reply to

    • Jvdplas
    • Not Ranked
    • Joined on 10-08-2009, 1:54 PM
    • Posts 5

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    We migrated from ODBC to OLEDB, ran a large number of stress tests on our live environment. Results are ( for the moment ) amazing.

    First of all the number of hits we were able to execute more then doubled, and the execution/run time on each of the ASP pages dropped. Secondly the number of "Sql sever does not exist" messages reduced to an average ( during he stress test ) of 4 every 1600 ASP requests.

    During previous stress-tests we were able to produce an average of 35 errors per 700 requests.

    As for the moment it looks rather promising. But, how can we get rid of the last few messages? I would expect to get time-out's instead of the message "Sql server does not exist", and therefore the "quest" has not yet been abanded :-)

    Q: How to solve these last few messages showing "Sql server does not exist"?

    JvdPlas
    NL / H'sum
  • 10-09-2009, 10:43 AM In reply to

    • tomkmvp
    • Top 10 Contributor
    • Joined on 03-20-2003, 10:27 AM
    • Central NJ
    • Posts 6,235
    • IIS MVPs

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    Not sure what else to tell you.  You may get better answers in a SQL Server forum.

  • 10-09-2009, 11:52 AM In reply to

    • Jvdplas
    • Not Ranked
    • Joined on 10-08-2009, 1:54 PM
    • Posts 5

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    Sounds logic, issue is that we currently have the idea that it is still a TCP/IP or IIS setting. One of the other issues is that we see the IWAM user being setup ( due to initial setup), an account which we do not use.

    Anyway, which are the best OLEDB settings for the connection string related to large amounts of SQL requests? I have setup, based upon tests, the following connection string: OBJConnection.Open "Provider=SQLOLEDB;Integrated Security=SSPI;Server=1.2.3.4;Database=OurDb;Min Pool Size=2;Max Pool Size=500;Connect Timeout=60;Network Library=DBMSSOCN;"

     

    JvdPlas
    NL / H'sum
  • 10-09-2009, 1:01 PM In reply to

    • tomkmvp
    • Top 10 Contributor
    • Joined on 03-20-2003, 10:27 AM
    • Central NJ
    • Posts 6,235
    • IIS MVPs

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    Jvdplas:
    One of the other issues is that we see the IWAM user being setup ( due to initial setup), an account which we do not use.

    IWAM is created at install for backwards compatibility if you run in IIS 5 isolation mode.  Under normal IIS 6 native mode it is never used.

    Jvdplas:
    Anyway, which are the best OLEDB settings for the connection string related to large amounts of SQL requests?

    I have no idea as I have only ever needed to use the default settings.

  • 10-18-2009, 3:07 AM In reply to

    Re: IIS becomes very slow and generates message - SQL Server does not exist -

    This sounds like a dns problem; check your dns setings are identical to the other server - primary dns, seconds, suffixes to search and suffix search order.

    Also make sure if you run "cliconfg" (start/run/cliconfg) that tcp/ip is set the same (usually tcp/ip only is what you need, your sql admin should be able to answer if you don't know what the options are).

    Good luck,

    Steve Radich - President
    BitShop.com - IIS Cloud Solution Coming Soon - Join our "Free 3 Month Beta" Waiting List Now...
Page 1 of 1 (10 items)
Microsoft Communities