We have a large volume application based on ASP.NET 3.5 and SQL 2008, where we hope to maintain a high level of 24x7 availability without the need for a maintenance window.
Over time, we became dependent on some stored processes that perform service operations to clean up data that is no longer needed, compile some metrics, etc. Our problem is that these sprocs consume almost the entire processor on the servers, while they lead to significant consequences for the response to the site.
Is there a way to run these sprocs with lower priority? It does not matter how long they take to complete, as long as we can reduce the impact on the database server processor.
source
share