Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're using a SQL Server 2008 database. This database provides data for two main applications:

  1. A website to display a Viewer.
  2. A routing application that needs to be highly responsive !

Is it possible to give different priorities to those two applications and what would be all the possibilities available to us ? I'm afraid that our Viewer website, through a bug or anything else would slow down our routing application.

I want to protect the routing application in order to keep it highly responsive, what are the solutions I could use?

share|improve this question
What server? Did you check the Resource Governor? it is only available in special editions, though. – TomTom May 31 '12 at 8:11
I've seen Resource Governor, is there any other ways of doing this ? – Andy M Jun 1 '12 at 8:50
No, as queries are identical to SQL Server before that. Priotitzation is not a concept and proirities / limits are exactly what the governor is for. – TomTom Jun 1 '12 at 9:08
up vote 1 down vote accepted

Andy M, to achieve this level of tunning in SQL, you must use the Resource Governor. It can be a problem, since it's available only in the (expensives) Datacenter & Enterprise editions.

If you can't afford this editions, there's a few things you can consider:


  • Split your database in 2: one for the routing app, another for the viewer app. This way, you can tune them separately, to obtain the best performance;
  • Consider acquiring HDs to your server (SSD, if you can afford), and split the data/index files between them, to increase I/O (thus the responsiveness);


  • If you need a high performance just in querying data, you can pre-process this data, leaving it in its final modeling. This approach can boost your query performance in orders of magnitude;
  • If you have to process information for this requests, but not all of this processing is relevant for the output, try to buffer the processing: analyze what data processing can be post-poned, and just write the data to some dummy tables (maybe in another DB), and process them in a different time.
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.