Subject Forcing closure of client transactions
Author robertgilland
We have a situation,
where we need certain processes to work regardless,

User 1 has a record open in a transaction,

our process which needs to update this record from running.

We are thinking about using a hammer approach:


1. We give a countdown message of an imminent closure of database.
2. We disconnect from the database
3. We shut down the database this will kick every one off.
4. We bring the database back online.
5. We reconnect to the database then run our process.

Have other people had to do things like this?
or is there a better way?

Kind Regards,