Customer Statistics Based on Database Lock Use

• US 20080027938A1
• Filed: 10/05/2007
• Published: 01/31/2008
• Est. Priority Date: 01/27/2005
• Status: Active Grant

• Current Assignee: Philip Hartman
• Original Assignee: Philip Hartman
• Inventors: Hartman, Philip
• Granted Patent: US 9,020,997 B2
• Time in Patent Office: Days
• US Class Current: 707/8
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0226 Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

A method and service for establishing a web-based network that includes an enterprise locking service. The enterprise locking service is able to coordinate multiple, cooperating applications that need to ensure that one and only one user is modifying a database record at a given time. These database records may be stored in multiple databases having potentially different database record locking protocols. Through monitoring and tracking of requests for database locks, the enterprise locking service is also able to determine database usage trends under various metrics.

Claims

1. A method comprising:

determining a database usage trend according to a frequency of database lock requests, the database lock requests being submitted to an enterprise locking service, to one or more of a plurality of databases.

2. The method of claim 1, wherein the database usage trend is based on a geographic location of the user from whom the database lock request originated.

3. The method of claim 1, wherein the database usage trend is based on a geographic region associated with a database being locked.

4. The method of claim 1, wherein the database usage trend is based on whether the database lock request was initiated by an individual or an enterprise.

5. The method of claim 1, wherein the database usage trend is based on a profitability metric of a requester that requested the database lock.

6. The method of claim 1, wherein the database usage trend is based on a profitability metric of an object being locked.

7. The method of claim 1, wherein the database usage trend is based on a class of a customer that initiated the database lock request.

8. The method of claim 1, wherein the database usage trend is based on a time of day that the database lock requests were sent.

9. The method of claim 1, wherein the database usage trend is based on an access channel identifier that identifies what type of access channel from which the database lock request was sent.

10. A computer program product, residing on a computer usable medium, comprising:

program code for determining a database usage trend according to a frequency of database lock requests, the database lock requests being submitted to an enterprise locking service, to one or more of a plurality of databases.

15. The computer program product of claim 15, wherein the database usage trend is based on a class of a customer that initiated the database lock request.

11. The computer program product of claim 14, wherein the database usage trend is based on a geographic region from which the database lock request originated.

12. The computer program product of claim 14, wherein the database usage trend is based on a geographic region associated with a database being locked.

13. The computer program product of claim 14, wherein the database usage trend is based on whether the database lock request was initiated by an individual or an enterprise.

14. The computer program product of claim 15, wherein the database usage trend is based on a profitability metric of a product line object being locked.

16. The computer program product of claim 15, wherein the database usage trend is based on an access channel identifier that identifies what type of access channel from which the database lock request was sent.