Using average replication latency to influence routing query transactions
US-9229999-B2 · Jan 5, 2016 · US
Managing replication configuration availability
US9418134B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9418134-B2 |
| Application number | US-201615010713-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 29, 2016 |
| Priority date | Mar 11, 2014 |
| Publication date | Aug 16, 2016 |
| Grant date | Aug 16, 2016 |
How to read this patent
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
- Title
What the patent document calls the invention.
- Abstract
A short plain-language summary of the technical disclosure.
- Assignees and inventors
Who owns or filed the patent and who is credited as inventor.
- Key dates
Filing, priority, publication, and grant dates set the timeline.
- First independent claim
The legal scope of protection — read this for what is actually claimed.
- CPC / IPC classifications
Technology tags used to group this patent with similar filings.
- Citations and related patents
Prior art links and similar publications in this corpus.
Abstract
Official abstract text for this publication.
A computer-implemented method, carried out by one or more processors, for managing replication configurations. In an embodiment, the method comprises receiving, by one or more processors, a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database; initializing, by one or more processors, a federated view, wherein the federated view is based on at least the source table in the source database as defined in the replication configuration; utilizing, by one or more processors, the federated view to satisfy requesting applications, where requesting applications obtain data from the federated view; responsive to determining the replication of data is in spec, utilizing, by one or more processors, the target table in the target database to satisfy requesting applications.
First claim
Opening claim text (preview).
What is claimed is: 1. A method for managing replication configurations, the method comprising: receiving, by one or more processors, a first replication configuration for replicating data, wherein the first replication configuration defines at least a target table in a target database based on a source table in a source database; determining, by one or more processors, a latency value, wherein the latency value represents a latency of replicating data from the source database to the target database; responsive to determining the latency value exceeds a threshold latency value and a portion of the target table in the target database is damaged, determining, by one or more processors, to utilize a first federated view to satisfy requesting applications; initializing, by one or more processors, the first federated view, wherein the first federated view is based on at least the source table in the source database as defined in the first replication configuration; utilizing, by one or more processors, the first federated view to satisfy requesting applications, wherein requesting applications obtain data from the first federated view; responsive to determining, by one or more processors, the source table matches the target table, utilizing, by one or more processors, the target table in the target database to satisfy requesting applications; responsive to determining the source table does not match the target table, initializing, by one or more processors, a second federated view, wherein the second federated view is based on at least the target table in the target database in the first replication configuration; utilizing, by one or more processors, the second federated view to satisfy requesting applications, where requesting applications obtain data from the second federated view; receiving, by one or more processors, a second replication configuration for replicating data, wherein the second replication configuration defines at least a new target table based on the source table; responsive to determining, by one or more processors, the target table matches the new target table, utilizing, by one or more processors, the new target table in the target database to satisfy requesting applications; responsive to determining the target table does not match the new target table, initializing, by one or more processors, a third federated view, wherein the third federated view is based on at least the new target table in the target database in the second replication configuration; and utilizing, by one or more processors, the third federated view to satisfy requesting applications, where requesting applications obtain data from the third federated view.
Assignees
Inventors
Classifications
Tablespace storage structures; Management thereof · CPC title
Synchronous replication · CPC title
in federated or virtual databases · CPC title
- G06F16/27Primary
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
Physics · mapped topic
Patent family
Related publications grouped by family.
External sources
Frequently asked questions
Answers are generated from the same data shown on this page.
- What does patent US9418134B2 cover?
- A computer-implemented method, carried out by one or more processors, for managing replication configurations. In an embodiment, the method comprises receiving, by one or more processors, a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database; initializing, by one o…
- Who is the assignee on this patent?
- IBM
- What technology area does this patent fall under?
- Primary CPC classification G06F16/27. Mapped technology areas include Physics.
- When was this patent published?
- Publication date Tue Aug 16 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
- What related patents are in patentsdb?
- We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).