As we know, when databases and SQL Agent jobs are created the owner is set by default to the user who created them. We've changed many of these to sa or an appropriate AD Service Account, but there are still several objects scattered among many instances where objects are owned by individules' Windows logins.
At this time we're facing a reorganization where the existing DBAs are being laid off and replaced by outsourced DBA support. How much of a problem is this (for the database processes that is)?
My underdanding of what "owner" means is that the owner can access these objects while bypassing normal secuity checks. If that is all, then will everything continue to work when the AD accounts are disabled? How about Agent Jobs? What other gotchas are when individual's accounts are disabled? (Not that it will be my problem when this happens, but while I'm still here I do feel responsible to prevent future issues).