Stored Procedure Development and Deployment

Patent metadata

Field	Value
Publication number	US-2016350107-A1
Application number	US-201514724856-A
Country	US
Kind code	A1
Filing date	May 29, 2015
Priority date	May 29, 2015
Publication date	Dec 1, 2016
Grant date	—

Abstract

Methods, systems, and computer-readable media for developing, storing, validating, tracking and transferring stored procedures are presented. The stored procedures may be stored in a central storage location. The storage location may receive a first version of a stored procedure and generate a change identifier for the first version. The system may evaluate the stored procedure to determine whether it complies with standards of the entity. In some examples, the first version may be checked-out and transferred to another environment for, for instance, modification to create a second version. The second version may then be transmitted to the central storage location for storage. A second change identifier may be generated and associate with the second version. The second version and the second change identifier may be stored. Similarly, an unlimited number of modifications to the stored procedure, each associated with a unique change identifier from the storage system, may be made.

First claim

1 . A system, comprising:
a first computing device having a first processor, a first communication interface, and a first memory storing computer-readable instructions that, when executed by the first processor, cause the first processor to: receive a first version of a stored procedure, the stored procedure including at least one of: a database procedure, a database function, and a database view; generate a first change identifier for the first version of the stored procedure, the first change identifier including a random string of characters; associate the first change identifier with the first version of the stored procedure; evaluate the first version of the stored procedure to determine whether the first version of the stored procedure complies with standards determined by an entity, evaluating the first version of the stored procedure including comparing parameters of the first version of the stored procedure to stored naming convention standards determined by the entity; responsive to determining that the first version of the stored procedure does comply with the naming convention standards determined by the entity, storing the first version of the stored procedure and the first change identifier together by the first computing device; responsive to determining that the first version of the stored procedure does not comply with the naming convention standards determined by the entity, rejecting the stored procedure including not storing the stored procedure, generating a to a user indicating that the first version of the stored procedure does not comply with the naming convention standards of the entity and requesting a change to the first version of the stored procedure to comply with standards of the entity; receive, from a second computing device, a request to transfer the first version of the stored procedure to the second computing device; and the second computing device having a second processor, a second communication interface, and a second memory storing computer-executable instructions that, when executed by the second processor, cause the second processor to: receive, from the first computing device and via the second communication interface, the first version of the stored procedure and the first change identifier; modify the first version of the stored procedure to create a second version of the stored procedure; transmit the second version of the stored procedure to the first computing device for storage.

2 . The system of claim 1 , the first computing device further including instructions that, when executed, cause the first processor to:
receive, from the second computing device and via the first communication interface, the second version of the stored procedure; responsive to receiving the second version of the stored procedure from the second computing device, generate a second change identifier for the second version of the stored procedure, the second change identifier being different from the first change identifier and the second change identifier including a random string of characters; associate the second change identifier with the second version of the stored procedure; and store the second version and the second change identifier together by the first computing device.

3 . The system of claim 2 , wherein the second computing device includes at least one of: a testing environment and a production environment.

4 . The system of claim 1 , further including instructions that, when executed, cause the processor to:
track the first version of the stored procedure and the second version of the stored procedure based on the first change identifier and second change identifier.

5 . The system of claim 4 , wherein tracking the first version of the stored procedure and the second version of the stored procedure includes recording differences between the first version of the stored procedure and the second version of the stored procedure.

6 . The system of claim 1 , wherein storing the first version of the stored procedure together with the first change identifier by the first computing device includes modifying a file attribute of the first version of the stored procedure to include the first change identifier.

7 . A system, comprising:
a processor; a communication interface communicatively coupled to the processor; and memory storing computer-readable instructions that, when executed by the processor, cause the processor to: receive a first version of a stored procedure, the stored procedure including at least one of: a database procedure, a database function, and a database view; generate a first change identifier for the first version of the stored procedure, the first change identifier including a random string of characters; associate the first change identifier with the first version of the stored procedure; evaluate the first version of the stored procedure to determine whether the first version of the stored procedure complies with standards determined by an entity, evaluating the first version of the stored procedure including comparing parameters of the first version of the stored procedure to stored naming convention standards determined by the entity; responsive to determining that the stored procedure does comply with the naming convention standards determined by the entity, storing the first version of the stored procedure and the first change identifier together in a storage system; and responsive to determining that the first version of the stored procedure does not comply with the naming convention standards determined by the entity, rejecting the stored procedure including not storing the stored procedure, generating a notification to a user indicating that the first version of the stored procedure does not comply with standards of the entity and requesting a change to the first version of the stored procedure to comply with standards of the entity.

8 . The system of claim 7 , further including instructions that, when executed by the processor, cause the processor to:
receive a request to transfer the first version of the stored procedure to at least one of: a testing environment and a production environment; check-out the first version of the stored procedure from the storage system and transfer the first version of the stored procedure to the at least one of: the testing environment and the production environment; receive, by the storage system, a second version of the stored procedure to be checked-in to the storage system, the second version including modifications made to the first version of the stored procedure; responsive to receiving the second version of the stored procedure, generate a second change identifier for the second version of the stored procedure; associate the second change identifier with the second version of the stored procedure; and store the second version of the stored procedure with the second change identifier in the storage system.

9 . The system of claim 8 , wherein transferring the first version of the stored procedure includes transferring the first change identifier with the first version of the stored procedure to the at least one of: the testing environment and the production environment.

10 . The system of claim 8 , further including instructions that, when executed, cause the processor to:
track the first version of the stored procedure and the second version of the stored procedure based on the first change identifier and second change identifier.

11 . The system of claim 10 , wherein tracking the first version of the stored procedure and the second version of the stored procedure includes recording differences between the first version of the stored procedure and the sec

Assignees

• Bank Of America

Inventors

• Bragg Jr Raymond B
• Muldoon William H
• Sanderson Ronald A

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title