We've noticed that processing of the same job / code in background processing is much slower than it is in foreground / interactive processing. Is this an inherent behavior and/or intended design of the way the system works? Our desire is to have specific jobs perform identically in background as they do in foreground and ultimately disallow foreground processing.
Any insight from anyone knowledgeable? (This is a Windows 2k / SQL Server environment.)