Chad, you might want to include a piece on how limiting the # of activations can allow for lowering the impact of multiple high-impact bulk work simultaneously requested, so it can be spread out over a longer time when the changes are non-critical.
An example of this could be only loading 1000 rows from a mid-day production file load at a time so you don't completely lock the system down with computations and the like, especially when the first file isn't even completed before the second one comes in. 🙂 It's probably one of the best features of the asynchronous queues I've found to help with load balancing.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA