IP Library Granted Patent US 10,810,102
Granted Patent B2
US 10,810,102 · App. 15/362,534 · Granted Oct 20, 2020

Database monitoring by data virtualization

Inventors: Thomas Theodor Koetter (Berlin, DE); Thomas Simenec (Berlin, DE)
Assignee: SAP SE
G06F11/3433G06F16/256G06F16/27H04L67/1095G06F2201/80G06F2201/87
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,810,102
App. No.
15/362,534
Granted
Oct 20, 2020
Kind
B2
Abstract

A computer implemented method for extended monitoring of a database includes establishing a data virtualization communications connection between a first and a second datacenter that is a copy of the first datacenter. Requests for monitoring information corresponding to the first datacenter are made by accessing its system views. Requests for monitoring information corresponding to the second datacenter are made by generating virtual tables on the first datacenter to provide the system views of the second datacenter to the first datacenter and accessing the virtual tables. The monitoring information corresponding to the first datacenter is grouped into a first schema on the first datacenter and the monitoring information corresponding to the second datacenter is grouped into a second schema, separate from the first schema. A union view is generated by combining the monitoring data associated with the two datacenters. Related apparatus, systems, techniques and articles are also described.

Claims (52)

1. A computer implemented method comprising:

establishing a data virtualization communications connection between a first datacenter and a second datacenter, the second datacenter being a copy of the first datacenter;

requesting monitoring information corresponding to the first datacenter by accessing system views of the first datacenter;

requesting monitoring information corresponding to the second datacenter by:

generating at least one virtual table on the first datacenter to provide the system views of the second datacenter to the first datacenter;

accessing the at least one virtual table corresponding to the monitoring information of the second datacenter;

routing a select operation to the second datacenter; and

transferring data to the first datacenter in response to the routing;

grouping the monitoring information corresponding to the first datacenter into a first schema on the first datacenter;

grouping the monitoring information corresponding to the second datacenter into a second schema, separate from the first schema on the first datacenter;

generating a union view by combining the monitoring data associated with the first datacenter and the monitoring data associated with the second datacenter on the first datacenter;

receiving, by the first datacenter, a query requesting monitoring information for both of the first data center and the second data center; and

providing, by the first datacenter accessing the union view, results responsive to the query;

wherein the data virtualization connection interprets the first datacenter and the second datacenter as separate databases.

2. The method of claim 1 , further comprising providing alerting based at least in part on the union view.

3. The method of claim 1 , further comprising:

monitoring the connection status between the first datacenter and the second datacenter; and

updating the at least one virtual table and the union view upon detection that the second datacenter is no longer connected to the first datacenter.

4. The method of claim 1 , wherein a statistic server running on the first datacenter is responsible for requesting the monitoring information from the first datacenter, requesting the monitoring information from the second datacenter, and generating the union view.

5. The method of claim 1 , wherein the first datacenter has read-only access to the second datacenter.

6. The method of claim 1 , wherein the first datacenter is in an active mode and the second datacenter is in an active mode to enable distribution of the workload between the first datacenter and the second datacenter.

7. The method of claim 1 , wherein the database is an in memory database (IMDB).

8. The method of claim 1 , wherein the database is a column oriented database.

9. The method of claim 1 , wherein the data virtualization communications connection utilizes an Open Database Connectivity (ODBC) protocol using the database ODBC driver included as part of the database installation.

10. The method of claim 1 , wherein the data virtualization communications connection is enabled via a Smart Data Access (SDA) tool.

11. A system comprising:

a processor; and

a non-transitory computer readable media having computer executable instructions stored therein, which, when executed by the processor, causes the system to perform operations comprising:

establishing a data virtualization communications connection between a first datacenter and a second datacenter, the second datacenter being a copy of the first datacenter;

requesting monitoring information corresponding to the first datacenter by accessing system views of the first datacenter;

requesting monitoring information corresponding to the second datacenter by:

generating at least one virtual table on the first datacenter to provide the system views of the second datacenter to the first datacenter;

accessing the at least one virtual table corresponding to the monitoring information of the second datacenter;

routing a select operation to the second datacenter; and

transferring data to the first datacenter in response to the routing;

grouping the monitoring information corresponding to the first datacenter into a first schema on the first datacenter;

grouping the monitoring information corresponding to the second datacenter into a second schema, separate from the first schema on the first datacenter; and

generating a union view by combining the monitoring data associated with the first datacenter and the monitoring data associated with the second datacenter on the first datacenter;

receiving, by the first datacenter, a query requesting monitoring information for both of the first data center and the second data center; and

providing, by the first datacenter accessing the union view, results responsive to the query;

wherein the data virtualization connection interprets the first datacenter and the second datacenter as separate databases.

12. The system of claim 11 , wherein the operations further comprise providing alerting based at least in part on the union view.

13. The system of claim 11 , wherein the operations further comprise:

monitoring the connection status between the first datacenter and the second datacenter; and

updating the at least one virtual table and the union view upon detection that the second datacenter is no longer connected to the first datacenter.

14. The system of claim 11 , wherein a statistic server running on the first datacenter is responsible for requesting the monitoring information from the first datacenter, requesting the monitoring information from the second datacenter, and generating the union view.

15. The system of claim 11 , wherein the first datacenter has read-only access to the second datacenter.

16. The system of claim 11 , wherein the first datacenter is in an active mode and the second datacenter is in an active mode to enable distribution of the workload between the first datacenter and the second datacenter.

17. The system of claim 11 , wherein the database is an in memory database (IMDB).

18. The system of claim 11 , wherein the database is a column oriented database.

19. The system of claim 11 , wherein the data virtualization communications connection utilizes an Open Database Connectivity (ODBC) protocol using the database ODBC driver included as part of the database installation.

20. The system of claim 11 , wherein the data virtualization communications connection is enabled via a Smart Data Access (SDA) tool.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 28, 2016
From: KOETTER, THOMAS THEODOR; SIMENEC, THOMAS
To: SAP SE
Reel/Frame 040434/0737 →
Continuity (1)
Related Publication 20180150520A1 · May 31, 2018