I'm not sure if this is a thing. I'm sorry about the ambiguous title--I wasn't really sure how to explain it. Basically I have a ASP.NET web page that runs two SQL queries and does some logic to produce a status page for our delivery department. It refreshes / updates every 30 seconds, therefore the database is being queried twice on every client refresh. Well, more and more people are using this application therefore there are more and more queries / minute. Also, it is running against our main database and I can see it causing slowdowns as more these custom web apps are created.
What I'm considering is making a console application and running it as a service on separate server that does the querying / logic every 10 seconds (less than the amount of refreshes being done by multiple clients). The service will update a table which is separate from our main database. Then the client will just have to read that table and format the output instead of doing the main logic.
Thoughts? Other ideas?
Edit: Execution times (happens up to 30 times / minute):
(1605 row(s) affected) SQL Server Execution Times: CPU time = 1123 ms, elapsed time = 1199 ms. (78 row(s) affected) SQL Server Execution Times: CPU time = 0 ms, elapsed time = 4 ms.
Also happening on the main database which hundreds use throughout the day. There hasn't been a significant slowdown, but I'm looking to future-proof. Although I did heavily slow it down when I was sending ~300 queries a minute once for testing. "Sorry!"