ElizabethC
New Member
I have a web application running on SQL Server 2008. There is a process of the application that takes some time to complete. I expect multiple users to be calling that process at the same time, but in testing, I notice that one user must wait for the other to finish.I have investigating transaction locking but I don't think it applies here. The process of my application copies a record set, then makes calculations, and then writes results in the database. The record set is taken from a different table than the results table.Initially, I was thinking it had to do with the database connection which had to be sequential. So I split it up so that each database event had its own connection. Didn't make a difference.I also noticed that when the process runs, the CPU shoots straight up to 100%. So I tested on a more powerful box but user 2 still had to wait for user 1 to finish.Can anyone help me understand what is happening so that users can run the process in parallel?