I asked a question in this forum a while ago about transactions where only the tail ends were commiting. I posted a lot of information because i wasn't sure what was causing it. If i watch the locks in the SQL performance monitor and also watch the performance tab of the Task Manager on the server (WINNT Server v4.0 build 1381) i can see that just before all the locks are dropped by SQL and any preceeding parts of the transaction are lost forever the CPU usage on the Server peaks at 100%. I also have 'Show Kernel Times' checked on the view menu in the task manager and after CPU peaks the kernel time graph spikes to 100% (apparently this is the kernel scurrying to free some resources). Then the locks are dropped by SQL server and the CPU usage returns to ~40%. Then it hangs out at 80 - 85% for a time and will eventually reach 100% and the process starts again. During all this the memory usage remains fairly constant at ~113MB the server has 128MB of physical ram and another couple hundred available with the page files. Any ideas anyone? TIA. Ruairi
Could your manufacturing facility benefit from real time process monitoring? Would you like your employees to be able to see up to the minute goal and actual production?
For innovative, low cost solutions check out my website.
Could your manufacturing facility benefit from real time process monitoring? Would you like your employees to be able to see up to the minute goal and actual production?
For innovative, low cost solutions check out my website.