Connection dropping between two boxes...

  • I have two boxes used for my website.
     
    The first box is running Windows 2000 Server and IIS with the website
     
    The second box is running Windows 2003 and SQL Server 2000 for the database
     
    The first box is connected to the Internet for obvious reasons
     
    The second box is connected to the first box with a cross over cable on a second NIC.
     
    About every two weeks the first box (running IIS) drops the ability to open a SQL connection to the second box (databse server)
     
    I can still ping the second box from the first and map to it's drives if needed but cannot connect via SQL Server Client or the website
     
    If I restart the first box and then disable and re-enable the network connection between the two it works again for about another two weeks.
     
     
    Any ideas???
  • Any errors in the eventviewer/sql server logs?

    Possible reasons for memory leaks

    Cursors aren't properly released

    Any calls with sp_OACreate not properly released.

    Lingering transactions

  • Thanks,  I will look into these.  Keep in mind, to fix the problem however, I do not need to restart SQL Server box, just the IIS Server.  Not sure if that makes a difference or not.

  • Also, there is no problems being reported in any of the logs

  • Keep in mind, to fix the problem however, I do not need to restart SQL Server box, just the IIS Server.  Not sure if that makes a difference or not.

    It isn't likely to be an memory leak then. That would need a sql server reset.

    Since the IIS box is rebooted all its connections are dropped. (releasing locks, rollbacking transactions...)

    ->Is the amount of connections leveling or does it continues to grow?

    ->Are there any transactions left open

    Is the server cpu licensed or seat licensed?

     

  • Is there another method to check the number of connections other that looking at the admin and activity?  The system is CPY licensed.  Thanks!

  • You can use the sp_who2 stored procedure to check the current connections from time to time. It runs much faster than enterprise manager activity.

    You can also monitor a lot of sql server counters with the performance monitor

    Cpu usage & IO activity may be handy too.

    Is the impossible to connect time predictable? With sql profiler you can monitor the statements sent to sql server (with a performance hit)

     

  • Thanks.  The down time is not predictable (at least that I know of).  I will monitor the connections to see if that might be the issue.

  • Another important point...

    This problem did not happen when SQL Server was on the same box as the web server (IIS).  Only when it was moved to another server.

Viewing 9 posts - 1 through 9 (of 9 total)

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