Database item versioning

• US 7,296,037 B1
• Filed: 01/21/1999
• Issued: 11/13/2007
• Est. Priority Date: 01/21/1999
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Dengler, Patrick, Ramos, Bill, Kruy, Steve, Pan, Julia Zhenglei
• Primary Examiner(s): Colbert; Ella
• Application Number:
  US09/235,038
• Time in Patent Office: 3,218 Days
• Field of Search: 707/1, 707/10, 707/100, 707/104, 707/200, 707/206, 707/104.1, 707/203, 717/1, 717/100, 717/102, 717/117, 717/108, 717/110, 717/114, 717/124, 717/140, 717/115, 717/122, 717/170, 709/101, 709/102, 709/106, 709/217, 713/1
• US Class Current: 1/1
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/2443 Stored procedures
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

The invention provides database item versioning, such as items like stored procedures found in databases such as Standard Query Language (SQL) databases. In one embodiment, the invention includes a program such as an editor, a database, a source code control and a mechanism. An editor program provides for editing a stored procedure. The databases includes the stored procedure. The SCC source code control system stores versions of the stored procedure. The mechanism checks in and checks out the stored procedure to provide for effective versioning thereof of the stored procedure.

Claims

1. A computer system for providing version control over at least one item in a database while keeping the database operable, comprising:

a source code control system to store versions of the database item in a data storage device;

a first program to check in and check out the database item, such that modification of the database item is restricted when the first program checks in the database item, and such that the first program checks in the database item after the first program checks out the database item;

a database having the database item, wherein the database invokes the first program upon receiving a request to access the database item, and the database continues to provide the requested access to the database item during the invocation of the first program; and

an editor to manipulate the database item after the first program checks out the database item, wherein the first program compares the version of the database item in the source code control system with the version of the database item in the database, and the editor manipulates the database item as a function of the comparison.

2. The computer system of claim 1, wherein the database requests to check out the database item such that the first program checks out the database item.

3. The computer system of claim 1, wherein the first program provides the database a choice of one or more different versions of the database item at the source code control system.

4. The computer system of claim 1, wherein the first program requests to check out the database item and a second program checks out the database item to the first program.

5. The computer system of claim 4, wherein the second program provides the first program a choice of one or more different versions of the database item at the source code control system and one or more different versions of the database item at the database.

6. The computer system of claim 5, wherein the version of the database item at the source code control system is identical to the version of the database item at the database.

7. The computer system of claim 1, wherein the first program requests to check in the database item and the second program checks in the database item into the source code control system.

8. The computer system of claim 7, wherein the second program checks in the database item into the source code control system as saved to the database.