Computerized database system and method

• US 6,725,218 B1
• Filed: 04/28/2000
• Issued: 04/20/2004
• Est. Priority Date: 04/28/2000
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Podanoffsky, Michael
• Primary Examiner(s): Vu, Kim
• Assistant Examiner(s): Ly, Anh
• Application Number:
  US09/561,151
• Time in Patent Office: 1,453 Days
• Field of Search: 707/1-10, 707/100, 707/101, 707/102, 707/103, 707/104.1, 707/203, 713/200
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A computerized database system and method are disclosed. In one aspect of the invention, database records are associated with respective unique identification keys. Each key specifies values that specify both a logical location and a physical server assigned to that location where the respective record associated with that key is located.

Claims

1. A computerized distributed database, comprising:

a plurality of geographically distributed servers that store data records, each of said records being identified by and accessible via a respective unique identification key, each respective key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored.

2. A database according to claim 1, wherein the server identification value is a physical address.

3. A database according to claim 1, wherein the logical location value indicates a logical domain.

4. A computerized distributed database, comprising:

a first server and a second server, the first server storing a first version of a data record, the second server storing a second version of the data record, each of said first and second versions of the data record being associated with a respective unique identification key;

each respective identification key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

the first server, in response to a record relocation command, modifying the first version of the data record to include a reference to the respective key of the second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

5. A database according to claim 4, wherein the respective key associated with the first version of the data record specifies a respective logical location value that indicates a respective logical location where the first version of the data record resides and a server identification value that indicates the first server, and also wherein the respective key associated with the second version of the data record specifies a respective logical location value that indicates a respective logical location where the second version of the data record resides and a server identification value that indicates the second server.

6. A method implemented in a computerized distributed database system including a plurality of geographically distributed servers, comprising:

storing data records in the servers, each of said records being identified by and accessible via a respective unique identification key, each respective key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored.

7. A method according to claim 6, wherein the server identification value is a physical address.

8. A method according to claim 6, wherein the logical location value specifies a logical domain.

9. A method implemented in computerized distributed database system including a first and a second server, comprising:

storing in the first server a first version of a data record, storing in the second server a second version of the data record, each of said first and second versions of the data record being associated with a respective unique identification key;

specifying, by each respective identification key, at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

modifying by the first server, in response to a record relocation command, the first version of the data record to include a reference to the respective key of the second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

10. A method according to claim 9, wherein the respective key associated with the first version of the data record specifies a respective logical location value that indicates a respective logical location where the first version of the data record resides and a server identification value that indicates the first server, and also wherein the respective key associated with the second version of the data record specifies a respective logical location value that indicates a respective logical location where the second version of the data record resides and a server identification value that indicates the second server.

11. Computer-readable memory comprising computer-executable program instructions that when executed cause:

a plurality of geographically distributed servers to store data records and to associate each of said records with a respective unique identification key via which the records are identified and may be accessed, each respective key specifying at least one respective location where a respective record resides in a database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored.

12. Computer-readable memory according to claim 11, wherein the server identification value is a physical address.

13. Computer-readable memory according to claim 11, wherein the logical location value specifies a logical domain.

14. Computer-readable memory comprising computer-program instructions that when executed cause:

a first server to store a first version of a data record, a second server to store a second version of the data record, each of said first and second versions of the data record being associated with a respective unique identification key;

each respective identification key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

the first server, in response to a record relocation command, to modify the first version of the data record to include a reference to the respective key of the second version of the data record and to change a read/write status of the first record to a read only status, and the second version of the data record to include a reference to the respective key of the first version of the data record.

15. Computer-readable memory according to claim 14, wherein the respective key associated with the first version of the data record specifies a respective logical location valve that indicates a respective logical location where the first version of the data record resides and a server identification value that indicates the first server, and also wherein the respective key associated with the second version of the data record specifies a respective logical location value that indicates a respective logical location where the second version of the data record resides and a server identification value that indicates the second server.

16. A computerized distributed database storing data records, comprising:

a database management mechanism that identifies and permits access to each of said records using a respective unique identification key, each respective key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored.

17. A database according to claim 16, wherein the server identification value is a physical address.

18. A database according to claim 16, wherein the logical location value indicates a logical domain.

19. A computerized distributed database storing data records, comprising:

a server storing a first version of a data record associated with a respective unique identification key;

each respective identification key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

the server, in response to a record relocation command, modifying the first version of the data record to include a reference to the respective key of a second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

20. A database according to claim 19, wherein the respective key associated with the first version of the data record specifies a respective logical location value that indicates a respective logical location where the first version of the data record resides and a server identification value that indicates the server.

21. A method implemented in computerized distributed database system, comprising:

storing in a server a first version of a data record associated with a respective unique identification key;

specifying, by each respective identification key, at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

modifying by the server, in response to a record relocation command, the first version of the data record to include a reference to the respective key of a second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

22. A method according to claim 21, wherein the respective key associated with the first version of the data record specifies a respective logical location value that indicates a respective logical location where the first version of the data record resides and a server identification value that indicates the server.

48. A computer readable media, comprising:

said computer readable media having instructions written thereon for execution on a processor for the practice of the method of claim 9 or claim 21 or claim 24 or claim 36.

49. Electromagnetic signals propagating on a computer network, comprising:

said electromagnetic signals carrying instructions for execution on a processor for the practice of the method of claim 9 or claim 21 or claim 24 or claim 36.

23. Computer-readable memory comprising computer-program instructions that when executed cause:

a server to store a first version of a data record in association with a respective unique identification key;

each respective identification key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

the server, in response to a record relocation command, to modify the first version of the data record to include a reference to the respective key of a second version of the data record and to change a read/write status of the first record to a read only status, and the second version of the data record to include a reference to the respective key of the first version of the data record.

24. Computer-readable memory according to claim 23, wherein the respective key associated with the first version of the data record specifies a respective logical location valve that indicates a respective logical location where the first version of the data record resides and a server identification value that indicates the server.

25. A computerized distributed database, comprising:

means for storing a first version of a data record and for storing a second version of the data record;

means for associating each of said first and second versions of the data record with a respective unique identification key;

means for specifying, by each respective identification key, at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

means for, in response to a record relocation command, modifying the first version of the data record to include a reference to the respective key of the second version of the data record and for changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

26. A database according to claim 25, wherein the respective key associated with the first version of the data record specifies a respective logical location value that indicates a respective logical location where the first version of the data record resides and a respective server identification value.

27. A method for operating a server, comprising:

storing in the server a first version of a data record associated with a respective unique identification key, the record stored as part of a database;

specifying, by each respective identification key, at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

modifying by the server, in response to a record relocation command, the first version of the data record to include a reference to a second key of a second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

28. The method of claim 27, further comprising:

indicating the first server by a physical address of the first server.

29. The method of claim 27, further comprising:

indicating the first logical location a logical domain in the first server.

30. The method as in claim 27, further comprising:

specifying, by the second key of a second version of the data record, a second server where the second version of the data record resides; and

indicating by a second logical location value a logical location where the second version of the data record resides in the second server.

31. The method of claim 27, further comprising:

indicating the second server by a physical address of the second server.

32. The method of claim 27, further comprising:

indicating by the second logical location a logical domain in the second server.

33. The method of claim 27, further comprising:

setting the second version of the data record to a read/write status.

34. A server, comprising:

means for storing in the server a first version of a data record associated with a respective unique identification key, the record stored as part of a database;

means for specifying, by each respective identification key, at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

means for modifying by the server, in response to a record relocation command, the first version of the data record to include a reference to a second key of a second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

35. The server of claim 34, further comprising:

means for indicating the first server by a physical address of the first server.

36. The server of claim 34, further comprising:

means for indicating the first logical location a logical domain in the first server.

37. The server of claim 34, further comprising:

means for specifying, by the second key of a second version of the data record, a second server where the second version of the data record resides; and

means for indicating by a second logical location value a logical location where the second version of the data record resides in the second server.

38. The server of claim 34, further comprising:

means for indicating the second server by a physical address of the second server.

39. The server of claim 34, further comprising:

means for indicating the second logical location a logical domain in the second server.

40. The server of claim 34, further comprising:

means for setting the second version of the data record to a read/write status.

41. A server, comprising:

a first version of a data record associated with a respective unique identification key, the record stored in the server as part of a database;

each respective identification key specifying at least one respective location where a respective record resides in the database, the respective location being specified by a logical location value that indicates a respective logical location where the respective record resides in the database and a server identification value that indicates a respective physical server assigned to the logical location in which the respective record is stored; and

a processor to modify, in response to a record relocation command, the first version of the data record to include a reference to a second key of a second version of the data record and changing a read/write status of the first record to a read only status, the second version of the data record including a reference to the respective key of the first version of the data record.

42. The server of claim 41, further comprising:

a physical address to indicate the first server.

43. The server of claim 42, further comprising:

a logical domain in the first server to indicate the first logical location.

44. The server of claim 42, further comprising:

the second key of a second version of the data record specifying a second server where the second version of the data record resides; and

a second logical location value indicating a logical location where the second version of the data record resides in the second server.

45. The server of claim 42, further comprising:

a physical address to indicate the second server.

46. The server of claim 42, further comprising:

the second logical location indicated by a logical domain in the second server.

47. The server of claim 41, further comprising:

means for setting the second version of the data record to a read/write status.