Quote:
Originally Posted by sclitheroe
The notion that you can script kicking users out of a database driven app forcefully presumes that doing so leaves the database and any in-flight transactions in a consistent state, that any temporary files or interim data or weird process-managed locks get cleaned up or are ignored, etc.
It's seldom as easy as a kill -9 (or equivalent) as is being suggested late in this thread, which is quite possibly why people are hesitant to try and script this in the first place.
|
I completely agree, and you bring up valid points. As Shazam pointed out they are already doing this, kicking users off, so I'm assuming they have addressed those points. Hopefully the IT person doesn't currently wait for everyone to logout, because that's just making it worse. Now you're going to use my personal unpaid time to screw around at the last second? Or just leave, thinking, "It's ok, they'll just force me out, right?"
The problem, as I see it, isn't that the process needs to be done, or even what process. That's a different problem, and one he's looking for someone to be paid to do [his initial question]. This has a bigger delegation issue, and IT should never be delegated with such tasks.
Even if it's an acquisition, the Accounting Dept has to take on the accounting tasks. No matter how crappy it is. Sucks to be them. IT will take on IT tasks for the acquisition. Sucks to be them for IT related tasks.
I'm just hoping Hulse's-biggest-fan realizes what he's getting into here. When something goes wrong, everyone will abandon you, especially those who say, "Don't worry, you won't be responsible, I'll cover for you!"
ers