On Fri, 22 Mar 2013 13:48:21 +0000, Scott Price <scott.pr...@virgin.net> wrote: > You shouldn't need to perform a server shut-down to perform a restore, > and do not need to ever to perform a backup, though it's up to you if > you choose to. What you would need to do is make sure all connections > to the database are closed. If you are using the .NET ADO.NET provider > only, you will by default probably be using connection pooling. As > such, you will likely need to have a call to > > FbConnection.ClearAllPools(); > > That should drop all connections from the local perspective. It will > not help with any other machines connected to the database however. > > After a short pause to let any kind of clean up that's required to > occur, you should be able to restore a database backup to that instance.
Shutting down a database means that the Firebird server will not accept any connections for a specific database (or only accepts a single admin connection). Depending on the exact config you can even force the server to close existing connections. This is a much cleaner way than assuming that the manual work to close connections is sufficient, or that your applications is the only one to connect. You can use FbConfiguration (in FirebirdSql.Data.Services) to shutdown a database. Mark ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
