Misunderstanding #22: Resource governor can control IO
Error
Resource tuning controllers cannot control I/O. We hope that the next version of SQL Server can support I/O control. IO control is helpful for reducing the performance impact on large table scan operations.
The following lists of functional resource controllers cannot be completed:
- The Buffer Pool memory can be controlled by the memory controller only.Execution PlanMemory occupied, but the data pages cached in the Buffer Pool cannot be controlled.
- You can control resources of multiple instances as a logical entity. This is not possible. Resource Control for multiple instances can only be implemented through Windows Server resource control. On this basis, you can set resource control for each instance.
- Allows resource controllers to monitor resource usage and generate alarms when the threshold is exceeded.
Don't make a mistake. I don't mean that resource control is not good, but that adding the above functions will be better.
A friend of mine, also the project manager of SQL mvp Aaron Bertrand and SQL Team, wrote a white paper about this: Using the Resource Governor.
