>If you have that many hits/sec then you probably need to take careful measures for everything to work. As I see it you have 2 main approaches:

In my local environment, there isn't. But, this is core code at the framework and it has to be as used for either environment.

>1. Graceful: work from the client side. Set a global flag e.g. "MaintenancePending". When that's set client apps stop trying to connect and users get some sort of "down for maintenance" message. Then clear existing connections (pooled or otherwise). Switching your data fill commands to non-pooled mode when the flag is set may help with this
>
>2. Brute force: work from the server side. The second approach at http://dba.stackexchange.com/questions/43802/how-to-block-user-access-to-perform-database-application-update looks interesting (not tested by me). If you need to force disconnects it can be done but it ROLLBACKs the connections it closes, which is inelegant and may cause users to lose work

Thanks