Well not exactly "Managing Logins" it's logging everyone off.
I have a distributed (world wide) db accessed by all sorts of user apps.
Needing to put the db into single server mode for upgrades I try to kill spids but that's useless, as soon as I kill them they reappear.
Even if I could kill them all, there are several people with SA and passwords and single mode doesn't seem to keep them out.
Usually you would let everyone know that the system is coming down at X time but I don't know who all the users are and can't communicate with them.
Whatever the soulution is I don't want to do anything that will stop remote applications from working after I finish the upgrade.
Any suggestions?
Software engineers are trained to read and understand code; they are not trained in mind reading. Document the purpose not just the functionality.