We frequently have problems with our database CPU being over-utilised by one or two resource-heavy queries and then our users experience poor performance and time outs because the database can't keep up with demand. We don't think one or two queries should be allowed to bring down our whole database, even if they are resource-heavy.

Could I suggest some functionality which would allow us to cap the resources consumed by an individual query, please? Or something which reduces the resources allocated to a particular large query if there isn't enough resource available for incoming requests? Perhaps the Resource Governor available on SQL Server?