Methods and Systems for Auto-Starting and Auto-Stopping Databases

• US 20160080217A1
• Filed: 09/15/2014
• Published: 03/17/2016
• Est. Priority Date: 09/15/2014
• Status: Active Grant

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: McHardy, Ian Roger, Bowman, Ivan Thomas, Khamis, Karim
• Granted Patent: US 9,961,134 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

Systems and methods are presented for auto-starting and auto-stopping databases in a cloud server environment. In some embodiments, a method can include accessing, by an initial server in a network-based system, a request to connect to a target database located in a target server of the network-based system. The method can also include determining, by an administrative database (admin database) residing in the initial server, a location of the target database residing in the target server, switching an execution context from no database in the target server to a copy of the admin database in the target server, performing an auto-start procedure to auto-start the target database in the target server, switching the execution context from the admin database in the target server to the target database in the target server, and transmitting a completion acknowledgement indicating the target server is connected to the target DB.

Claims

1. A method comprising:

accessing, by a target server in a network-based system, a redirect request to connect to a target database (target DB) located in the target server, the redirect request to connect derived from an initial request to connect to the target DB accessed by an initial server in the network-based system, a location of the target DB in the target server determined by an administrative database (admin DB) residing in the initial server;

switching an execution context from no database in the target server to a copy of the admin DB in the target server;

performing, by the admin DB in the target server, an auto-start procedure to auto-start the target DB in the target server;

switching the execution context from the admin DB in the target server to the target DB in the target server; and

transmitting a completion acknowledgement indicating the target server is connected to the target DB.

2. The method of claim 1, further comprising determining whether the target DB is already running in the target server.

3. The method of claim 1, further comprising determining, by the admin DB in the target server, that the target DB is configured for the auto-start procedure.

4. The method of claim 1, further comprising spawning a logic module in the admin DB of the target server, the logic module configured to perform the auto-start procedure of the target DB in the target server.

5. The method of claim 1, further comprising managing, by the admin DB in the target server, a concurrent request to connect to the target DB.

6. The method of claim 1, further comprising determining whether the target DB is idle.

7. The method of claim 6, further comprising measuring an idle time indicating a length of time the target DB is idle.

8. The method of claim 7, further comprising performing an auto-stop procedure when the idle time satisfies a predetermined threshold.

9. The method of claim 8, further comprising managing concurrent requests to connect to the target DB when performing the auto-stop procedure.

10. A network-based system, the network-based system comprising:

an initial server comprising an administrative database (admin DB);

a target server coupled to the initial server and comprising a target database (target DB) and a copy of the admin DB;

the initial server configured to access a request to connect to the target DB located in the target server of the network-based system;

the admin DB of the initial server configured to;

determine a location of the target DB residing in the target server;

redirect the request to connect to the target DB from the initial server to the target server if the target DB does not reside on the initial server;

the copy of the admin DB in the target server configured to;

switch an execution context from no database in the target server to the copy of the admin DB in the target server;

perform an auto-start procedure to auto-start the target DB in the target server;

switch the execution context from the admin DB in the target server to the target DB in the target server; and

transmit a completion acknowledgement indicating the target server is connected to the target DB.

11. The system of claim 10, wherein the target server is further configured to determine if the target DB is already running in the target server.

12. The system of claim 10, wherein the admin DB in the target server is further configured to determine that the target DB is configured for the auto-start procedure.

13. The system of claim 10, wherein the copy of the admin DB in the target server is further configured to spawn a logic module in the admin DB of the target server, the logic module configured to perform the auto-start procedure of the target DB in the target server.

14. The system of claim 10, wherein the copy of the admin DB in the target server is further configured to manage a concurrent request to connect to the target DB.

15. The system of claim 10, wherein the copy of the admin DB in the target server is further configured to determine if the target DB is idle.

16. The system of claim 15, wherein the copy of the admin DB in the target server is further configured to measure an idle time indicating a length of time that the target DB is idle.

17. The system of claim 16, wherein the copy of the admin DB in the target server is further configured to perform an auto-stop procedure if the idle time satisfies a predetermined threshold.

18. The system of claim 17, wherein the copy of the admin DB in the target server is further configured to manage concurrent requests to connect to the target DB when performing the auto-stop procedure.

19. A computer-readable medium embodying instructions that, when executed by a processor, perform operations comprising:

accessing a request at an initial server to connect to a target database (target DB) located in a target server of the network-based system;

determining a location of the target DB residing in the target server;

switching an execution context from no database in the target server to a copy of the admin DB in the target server;

performing an auto-start procedure to auto-start the target DB in the target server;

switching the execution context from the admin DB in the target server to the target DB in the target server; and

transmitting a completion acknowledgement indicating the target server is connected to the target DB.

20. The computer-readable medium of claim 19, wherein the operations further comprise:

upon determining if the target DB is idle, measuring an idle time indicating a length of time that the target DB is idle; and

performing an auto-stop procedure if the idle time satisfies a predetermined threshold.