At some point along the way, ASSP and MSSQL are both using 100% of the CPU and it seems that ASSP isn't doing anything. It starts out with the warnings from ASSP that the database took more than 1 second to respond to a query. Then the time gets longer and longer until it's consuming all resources.
Just trying to get a handle on where this is coming from. It will run for months with no problem when I have it connect to my other SQL server, (Windows Server 2008 and MS SQL 2008), but suddenly ASSP won't talk to that one anymore and when it tries the SQL server loses connection with everything else that uses it. The server is older hardware, Core2Duo 3.0GHz, 2GB RAM. It's running Windows Server 2003 and MS SQL Server 2000 Enterprise. Kevin Summers KISTech Studios Photography & Video -----Original Message----- From: Thomas Eckardt [mailto:[email protected]] Sent: Sunday, October 14, 2012 10:56 AM To: For Users of ASSP Subject: [Assp-user] Antwort: ASSP Maxes out MSSQL Server. These connections are required by assp! >tied up 199 connections depending on the configuration , the number could be much higher >so it doesn't choke the SQL what chokes a SQL server a sleeping (idle) connection ? Thomas ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
