I've got a virtual machine with a single SQL instance on it. That instance is home to live, test, and development databases. On occasion, developers or support people will run some massive query that just hogs all available CPU cycles. I've done this myself, too.
In this situation, is there a way to prevent this? I'd like to prevent this without going to additional instances, additional licenses, etc. It just seems a huge oversight if there's not some way of telling the SQL server... never spend more than a quarter of your time working on requests to a specific DB.