Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 7 of 7 total |
What is the proper way to "shut down" EDB Server? |
Thu, Feb 21 2013 12:19 PM | Permanent Link |
Barry | Are there steps I should follow if I want a controlled shutdown of the EDB server (running as a service)?
Let's say I need to "kick" everyone off of the server to do maintenance work on the database for an hour. 1) How do I let the current transactions complete? 2) How do I prevent new sessions from starting? (prevent user's from logging in?) 3) How do I prevent new transactions from starting? 4) How do I get exclusive control of the database and prevent further connections until I am finished my maintenance schedule? I know I could work on a replicated database to avoid downtime, and then switch the users to this database when I'm done, but I'd like to know the steps in case I'm not using replication. Is this documented somewhere? TIA Barry |
Sat, Feb 23 2013 12:14 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Barry,
<< 1) How do I let the current transactions complete? 2) How do I prevent new sessions from starting? (prevent user's from logging in?) 3) How do I prevent new transactions from starting? >> If you simply stop the service, then eventually it will shut down the server after all of the server threads are done doing what they need to do. However, I just added a flag to the server socket to tell it to stop trying to accept connections while the server is waiting for its threads to shut down (next minor release). 4) How do I get exclusive control of the database and prevent further connections until I am finished my maintenance schedule? >> If the EDB Server service is stopped, then you can just access the database directly. Or did you still want to use the EDB Server ? If you have any other questions, please let me know. Tim Young Elevate Software www.elevatesoft.com |
Sat, Feb 23 2013 1:27 PM | Permanent Link |
Barry | "Tim Young [Elevate Software]" wrote:
Barry, << 1) How do I let the current transactions complete? 2) How do I prevent new sessions from starting? (prevent user's from logging in?) 3) How do I prevent new transactions from starting? >> <If you simply stop the service, then eventually it will shut down the server after all of the server threads are done doing what they need to do. However, I just added a flag to the server socket to tell it to stop trying to accept connections while the server is waiting for its threads to shut down (next minor release).> Great, thanks. << 4) How do I get exclusive control of the database and prevent further connections until I am finished my maintenance schedule? >> <If the EDB Server service is stopped, then you can just access the database directly. Or did you still want to use the EDB Server ?> I'd still want to use the EDB Server because it would be a remote database. So I'd likely have to stop anyone except the Administrator user from connecting to the database for a period of time, but still allow users to connect to other databases that aren't down for maintenance. Barry |
Sat, Feb 23 2013 1:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Barry,
<< I'd still want to use the EDB Server because it would be a remote database. So I'd likely have to stop anyone except the Administrator user from connecting to the database for a period of time, but still allow users to connect to other databases that aren't down for maintenance. >> Hmmm, I'll have to think about the implementation details of such a change. Tim Young Elevate Software www.elevatesoft.com |
Sat, Feb 23 2013 8:57 PM | Permanent Link |
Raul Team Elevate | On 2/23/2013 1:27 PM, Barry wrote:
> I'd still want to use the EDB Server because it would be a remote database. So I'd likely have to stop anyone except the Administrator user from connecting to the database for a period of time, but still allow users to connect to other databases that aren't down for maintenance. > No very elegant but how about starting a 2nd instance of the EDB Server running on another port that only you know of - this would only be used for maintenance activities. Raul |
Sun, Feb 24 2013 3:56 AM | Permanent Link |
Barry | Raul wrote:
On 2/23/2013 1:27 PM, Barry wrote: >> I'd still want to use the EDB Server because it would be a remote database. So I'd likely have to stop anyone except the Administrator user from connecting to the database for a period of time, but still allow users to connect to other databases that aren't down for maintenance. >> <No very elegant but how about starting a 2nd instance of the EDB Server running on another port that only you know of - this would only be used for maintenance activities.> Raul, That may work, thanks. Barry |
Mon, Feb 25 2013 12:08 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Raul,
<< No very elegant but how about starting a 2nd instance of the EDB Server running on another port that only you know of - this would only be used for maintenance activities. >> Actually, very elegant, considering that the EDB Server can do "named instances" of the server. Thanks, Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |