Database system and method with improved locks

• US 20050216463A1
• Filed: 03/24/2004
• Published: 09/29/2005
• Est. Priority Date: 03/24/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Volker, Paul, Klein, Udo
• Granted Patent: US 7,558,794 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

A method for handling database locks includes detecting a new query from an administrator for a set of database records. Next, it is determined whether the administrator has any chance of being authorized to acquire a new lock. If so, an attempt is made to acquire the new lock and, on the failure to acquire, the administrator is informed that the lock has already been acquired by a prior administrator. Optionally, the new administrator is also provided with identifying information of the prior administrator and contact information for the prior administrator. The new administrator is therefore pre-screened to determine whether there is any chance to acquire a new lock to reduce the chance that an unauthorized new administrator could lock the set of database records. Also, should the new administrator be authorized but not able to access the set of database records due to a prior lock, the new administrator can be informed of the identity and contact information concerning the holder of the prior lock.

Claims

1. A method for handling database locks comprising:

detecting a new query from a new administrator for a set of database records that are associated with a potential new lock;

determining whether said new administrator has any chance of being authorized to acquire said new lock;

attempting to acquire said new lock if said new administrator has a chance of being authorized; and

informing said new administrator of a failure to acquire said new lock if a prior lock has already been acquired due to a prior query by a prior administrator.

2. A method for handling database locks as recited in claim 1 wherein informing said new administrator includes identifying the prior administrator.

3. A method for handling database locks as recited in claim 2 wherein informing said new administrator includes providing contact information for said prior administrator.

4. A method for handling database locks as recited in claim 1 further comprising informing said new administrator that said new administrator is not authorized to acquire said new lock if it is determined that said new administrator has no chance of acquiring said new lock.

5. A method for handling database locks as recited in claim 1 further comprising permitting access to said set of database records if said new administrator acquires said new lock, and designating said new administrator as a prior administrator and said new lock as a prior lock.

6. A method for handling database locks as recited in claim 5 further comprising releasing said prior lock after said prior administrator has checked out from said set of database records.

7. A method for handling database locks as recited in claim 1 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator has write authorization for said set of database records.

8. A method for handling database locks as recited in claim 1 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator has a maximum database access authorization.

9. A method for handling database locks as recited in claim 1 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said set of database records personally pertain to said new administrator.

10. A method for handling database locks as recited in claim 1 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator is organizationally authorized.

11. A method for handling database locks as recited in claim 1 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator is currently authorized.

12. A computer readable media including program code segments for handling database locks comprising:

a code segment detecting a new query from a new administrator for a set of database records that is associated with a potential new lock;

a code segment determining whether said new administrator has any chance of being authorized to acquire said new lock;

a code segment attempting to acquire said new lock if said new administrator has a chance of being authorized; and

a code segment informing said new administrator of a failure to acquire said new lock if a prior lock has already been acquired due to a prior query by a prior administrator.

13. A computer readable media including program code segments for handling database locks as recited in claim 12 wherein informing said new administrator includes identifying the prior administrator.

14. A computer readable media including program code segments for handling database locks as recited in claim 13 wherein informing said new administrator includes providing contact information for said prior administrator.

15. A computer readable media including program code segments for handling database locks as recited in claim 12 further comprising a code segment informing said new administrator that said new administrator is not authorized to acquire said new lock if it is determined that said new administrator has no chance of acquiring said new lock.

16. A computer readable media including program code segments for handling database locks as recited in claim 12 further comprising a code segment permitting access to said set of database records if said new administrator acquires said new lock, and designating said new administrator as a prior administrator and said new lock as a prior lock.

17. A computer readable media including program code segments for handling database locks as recited in claim 16 further comprising a code segment releasing said prior lock after said prior administrator has checked out from said set of database records.

18. A computer readable media including program code segments for handling database locks as recited in claim 12 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator has write authorization for said set of database records.

19. A computer readable media including program code segments for handling database locks as recited in claim 12 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator has a maximum database access authorization.

20. A computer readable media including program code segments for handling database locks as recited in claim 12 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said set of database records personally pertain to said new administrator.

21. A computer readable media including program code segments for handling database locks as recited in claim 12 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator is organizationally authorized.

22. A computer readable media including program code segments for handling database locks as recited in claim 12 wherein determining whether said new administrator has any chance of being authorized to acquire said new lock includes whether said new administrator is currently authorized.

23. A method for making a preliminary determination as to whether a database administrator has authorization to access a set of database records comprising:

determining that a database administrator has no chance of being authorized to access a designated set of database records if said database administrator does not have one or more of;

(a) write authorization for said designated set of database records;

(b) if said designated set of database records are personal database records of said database administrator of a type likely to create a conflict of interest, (c) if the database administrator is not organizationally permitted to access said set of database records;

or (d) if said database administrator is not currently authorized; and

determining that a database administrator has a chance of being authorized if said database administrator has one or more of;

(a) write authorization and maximum administrator authorization; and

(b) write authorization, not maximum authorization, not if said designated set of database records are personal database records of said database administrator of a type likely to create a conflict of interest, if the database administrator is not organizationally permitted to access said set of database records, and currently authorized.

24. A computer readable media including program code segments for making a preliminary determination as to whether a database administrator has authorization to access a set of database records comprising:

a code segment determining that a database administrator has no chance of being authorized to access a designated set of database records if said database administrator does not have one or more of;

(a) write authorization for said designated set of database records;

(b) if said designated set of database records are personal database records of said database administrator of a type likely to create a conflict of interest, (c) if the database administrator is not organizationally permitted to access said set of database records;

or (d) if said database administrator is not currently authorized; and

a code segment determining that a database administrator has a chance of being authorized if said database administrator has one or more of;

(a) write authorization and maximum administrator authorization; and

(b) write authorization, not maximum authorization, not if said designated set of database records are personal database records of said database administrator of a type likely to create a conflict of interest, if the database administrator is not organizationally permitted to access said set of database records, and currently authorized.

25. A database system including locks comprising:

means for detecting a new query from a new administrator for a set of database records capable that is associated with a new lock;

means for determining whether said new administrator has any chance of being authorized to acquire said new lock;

means for attempting to acquire said new lock if said new administrator has a chance of being authorized; and

means for informing said new administrator of a failure to acquire said new lock if a prior lock has already been acquired due to a prior query by a prior administrator.

26. A database system including locks as recited in claim 25 wherein informing said new administrator includes means for identifying the prior administrator.

27. A database system including locks as recited in claim 25 wherein informing said new administrator includes means for providing contact information for said prior administrator.

28. A database system including locks as recited in claim 25 further comprising means for informing said new administrator that said new administrator is not authorized to acquire said new lock if it is determined that said new administrator has no chance of acquiring said new lock.

29. A database system including locks as recited in claim 25 further comprising means for permitting access to said set of database records if said new administrator acquires said new lock, and means for designating said new administrator as a prior administrator and said new lock as a prior lock.

30. A database system comprising:

a plurality of administrator terminals;

a database server capable of being accessed by a plurality of administrators associated with said plurality of administrator terminals, said database server including, at least in part, a database program capable of managing a plurality of records that may be grouped into sets of records, said database program including the functionality of;

(a) detecting a new query from a new administrator at a new administrator terminal for a set of database records capable that is associated with a new lock;

(b) determining whether said new administrator has any chance of being authorized to acquire said new lock;

(c) attempting to acquire said new lock if said new administrator has a chance of being authorized; and

(d) informing said new administrator at said new administrator terminal of a failure to acquire said new lock if a prior lock has already been acquired due to a prior query by a prior administrator on a prior administrator station.

31. A database system as recited in claim 30 wherein informing said new administrator includes identifying, on said new administrator station, the prior administrator.

32. A database system as recited in claim 31 wherein informing said new administrator includes, on said new administrator station, providing contact information for said prior administrator.

33. A database system as recited in claim 30 further comprising informing said new administrator on said new administrator station that said new administrator is not authorized to acquire said new lock if it is determined that said new administrator has no chance of acquiring said new lock.

34. A database system as recited in claim 30 further comprising permitting access to said set of database records via said new administrator terminal if said new administrator acquires said new lock, and designating said new administrator as a prior administrator and said new lock as a prior lock.