# US 2015/0149425 A1 · Database job description and scheduling

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0149425 A1
- Document ID: US20150149425A1
- Status: Published application
- Kind: A1
- Application number: 14/310,698
- Filed: 2014-06-20
- Published: 2015-05-28
- Earliest claimed: 2013-11-25
- Assignees: Sap SE
- Inventors: Bjoern Friedmann; Florian Foebel; Boris Gruschko; Christian Mohr; Martin Strenge; Sascha Zorn
- Web page: https://patentgrep.com/patent/US20150149425A1

## CPC

- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 11/3668: Testing of software
- G06F 16/21: Design, administration or maintenance of databases
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/951: Indexing; Web crawling techniques
- G06F 16/953: Querying, e.g. by the use of web search engines
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system includes acquisition of executable code of a database job, generation of a definition of the database job in a database repository, the definition of the database job comprising metadata specifying the executable code of the database job and a schedule for executing the executable code, association of a user with the database job, and activation of the database job.

## Claims

### Claim 1

A system comprising:
a memory storing:
a database; and
a database repository; and
a processor to execute the processor-executable process steps to cause the system to:
acquire executable code of a database job;
generate a definition of the database job in the database repository, the definition of the database job comprising metadata specifying the executable code of the database job and a schedule for executing the executable code;
associate a user with the database job; and
activate the database job.

### Claim 2 (depends on 1)

A system according to claim 1, wherein the metadata specifies the schedule based on a temporal relation to a last day of a month.

### Claim 3 (depends on 2)

A system according to claim 2, wherein the processor is further to execute the processor-executable process steps to cause the system to:
associate a start timestamp and an end timestamp with the database job.

### Claim 4 (depends on 2)

A system according to claim 2, wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository.

### Claim 5 (depends on 2)

A system according to claim 2, wherein the metadata specifies a second schedule for executing the executable code.

### Claim 6 (depends on 1)

A system according to claim 1, further comprising:
associating a start timestamp and an end timestamp with the database job.

### Claim 7 (depends on 1)

A system according to claim 1, wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository.

### Claim 8

A computer-implemented method comprising:
acquiring executable code of a database job;
generating a definition of the database job in a database repository, the definition of the database job comprising metadata specifying the executable code of the database job and a schedule for executing the executable code;
associating a user with the database job; and
activating the database job.

### Claim 9 (depends on 8)

A computer-implemented method according to claim 8, wherein the metadata specifies the schedule based on a temporal relation to a last day of a month.

### Claim 10 (depends on 9)

A computer-implemented method according to claim 9, further comprising:
associating a start timestamp and an end timestamp with the database job.

### Claim 11 (depends on 9)

A computer-implemented method according to claim 9, wherein activating the database job comprises compiling executable code associated with the database job into byte code and storing the byte code in the database repository.

### Claim 12 (depends on 8)

A computer-implemented method according to claim 8, wherein the metadata specifies a second schedule for executing the executable code.

### Claim 13 (depends on 8)

A computer-implemented method according to claim 8, further comprising: associating a start timestamp and an end timestamp with the database job.

### Claim 14 (depends on 8)

A computer-implemented method according to claim 8, wherein activating the database job comprises compiling executable code associated with the database job into byte code and storing the byte code in the database repository.

### Claim 15

A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause to the computer system to:
acquire executable code of a database job;
generate a definition of the database job in a database repository, the definition of the database job comprising metadata specifying the executable code of the database job and a schedule for executing the executable code;
associate a user with the database job; and
activate the database job.

### Claim 16 (depends on 15)

A non-transitory computer-readable medium according to claim 15, wherein the metadata specifies the schedule based on a temporal relation to a last day of a month.

### Claim 17 (depends on 16)

A non-transitory computer-readable medium according to claim 16, the program code executable by the computer system to cause to the computer system to:
associate a start timestamp and an end timestamp with the database job.

### Claim 18 (depends on 16)

A non-transitory computer-readable medium according to claim 16, wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository.

### Claim 19 (depends on 15)

A non-transitory computer-readable medium according to claim 15, wherein the metadata specifies a second schedule for executing the executable code.

### Claim 20 (depends on 15)

A non-transitory computer-readable medium according to claim 15, wherein activation of the database job comprises compilation of executable code associated with the database job into byte code and storing the byte code in the database repository.
