July 24, 2008 at 4:52 am
Hi
MY application is not anle to handle load..
everytime if no of users increases the application gets hanged..
can you please tell me what can be the reasons for this
Thanks
July 24, 2008 at 7:59 am
There could be a very long list of potential issues...
I would start by looking at the database processes to see if there is any process blocking at the point your application starts hanging.
If it was easy, everybody would be doing it!;)
July 24, 2008 at 8:09 am
Could be blocking. What version of SQL Server are you running? If it is MSDE it could be that you need to get a pay version as MSDE has a governor on it.
If you were more specific as to the behavior your application is exhibiting then someone might be able to offer more suggestions. Also what is the hardware SQL Server is running on? Is your application web-based or pc-based?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 24, 2008 at 8:16 am
Hi
SQL 2000 Dev Ed SP1
Application is web based and when it hangs.. we need to close the application either from task manager or from top.
July 24, 2008 at 9:32 am
What is the hardware (CPU, RAM, Disk Setup)?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 24, 2008 at 12:21 pm
Would like to know how are you connecting to the DB. Is the process being killed fron back end when you are closing the application. Tha nature of coding and open connections to DB could also be a reason.
July 24, 2008 at 9:56 pm
The space available on disk is in GB and RAM is 2GB.
The process doesn't need to be killed at back end but from task manager or closing the application from right top corner.
The application particularly gets hanged when trying to create report or running a simualtion.
For creating Report huge no of data is collected from different tables and for simulation also there are various dll's and exe's involved which pass the o/p for tables.
The dll's n exe's pass the result on time, only in populating the results to db .. the application gets hanged.
This hang usually happens when 10 or more users hit the same button simultaenously.
July 24, 2008 at 10:22 pm
There could be lots of reasons, but likely the application is not dealing with the time it takes for something to occur or the load of data being moved.
You haven't really provided any details about what is happening in the application. You mention a "button", but haven't given any idea or details of what the button does. The way to troubleshoot is work your way down through the code, through the processes, determining where in the applicaiton, which method calls are hanging. Implement logging or tracing of the application and SQL Server to narrow down where your difficulties lie.
July 25, 2008 at 6:51 am
khushbu.kumar (7/24/2008)
The space available on disk is in GB and RAM is 2GB.The process doesn't need to be killed at back end but from task manager or closing the application from right top corner.
The application particularly gets hanged when trying to create report or running a simualtion.
For creating Report huge no of data is collected from different tables and for simulation also there are various dll's and exe's involved which pass the o/p for tables.
The dll's n exe's pass the result on time, only in populating the results to db .. the application gets hanged.
This hang usually happens when 10 or more users hit the same button simultaenously.
As Steve said, it sounds like the application may not be handling the wait gracefully. It also sounds like you may have some blocking going on in the database. If there is a specific time of day that this happens you should run Profiler, or even better yet, simulate the problem on a test system, to see what is happening. Specifically looking at the Lock events along with RPC: StmtStarting, RPC: StmtCompleted, SP: StmtStarting, SP: StmtCompleted, SQL: StmtStarting, SQL: StmtCompleted. This will help you see what is happening when the problem occurs. You could also just run an sp_who2 query when the problem is reported in order to see if there is a blocking chain happening.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply