REUSABLE DATA QUERY LANGUAGE STATEMENTS

• US 20080091733A1
• Filed: 10/16/2006
• Published: 04/17/2008
• Est. Priority Date: 10/16/2006
• Status: Active Application

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: Teradata US, Inc. (Teradata Corporation)
• Inventors: Mannion, Leslie, Figge, Jason, Carmer, David, Draper, Linette, Baril, Robert, Fu, Henry, Shelton, Scott, Shah, Anish, Seifert, Christian
• Application Number:
  US11/549,721
• Publication Number:
  US 20080091733A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/242 Query formulation

Abstract

Techniques are presented for reusable data query language statements. User-defined parameter variables with parameter types are interspersed in data query language statements to form a rule. The rule may execute as a standalone application or as part of another application or service. When the rule is executed, parameter values for the parameter variables are dynamically acquired and populated into the data query language statements.

Claims

1. A method, comprising:

receiving a parameter type and a parameter variable for a data query language statement;

iterating the processing associated with receiving zero or more additional times for additional parameter types and additional parameter variables for the data query language statement or for additional data query language statements; and

creating a rule that represents the parameter type, the parameter variable, the data query language statement, and any additional parameter types, any additional parameter variables, and any additional data query language statements.

2. The method of claim 1 further comprising, binding the rule to an object or a plan.

3. The method of claim 2 further comprising:

receiving an instruction to execute the object or the plan; and

interactively prompting a user to provide one of more values for the parameter variable and any additional parameter variables, wherein when the parameter variable or any additional parameter variables are referenced multiple times within the rule, the user is prompted once for the appropriate value.

4. The method of claim 2 further comprising:

receiving an instruction to execute the object or the plan; and

automatically acquiring one or more values from the parameter variable and any additional parameter variables from at least one of another service, a data store table, a command line parameter, and a file.

5. The method of claim 1, wherein receiving further includes receiving the parameter type, the parameter variable, and the data query language statement from a user within a graphical user interface (GUI) tool.

6. The method of claim 1 further comprising, identifying the data query language as an SQL language statement.

7. The method of claim 1 further comprising, executing the rule as at least one of a query, a report, a plan, and a standalone application.

8. A method, comprising:

providing a graphical user interface (GUI) tool for defining user-defined parameter variables to intersperse in one or more SQL statements;

interacting with a user via the GUI tool to define a rule that includes the one or more SQL statements with the interspersed user-defined parameter variables; and

storing the rule for subsequent use.

9. The method of claim 8, wherein interacting further includes receiving parameter types for the parameter variables via the GUI tool from the user.

10. The method of claim 8 further comprising, receiving a schedule constraint via the GUI tool from the user for executing the rule.

11. The method of claim 8 further comprising, executing the rule as at least one or part of another application and as an independent application represented by the rule.

12. The method of claim 11, wherein executing further includes dynamically acquiring parameter values for the user-defined parameter variables from at least one of command line parameters, a data store table, a file, a prompt made to the user for supplying the parameter values, and an automated service.

13. The method of claim 8 further comprising, supplying one or more drop down menus for selecting parameter types to associate with the parameter variables to the user.

14. A system comprising:

a graphical user interface (GUI) tool; and

an rule generator service, where the GUI tool is to interact with a user to receive SQL parameter variables, parameter types associated with the parameter variables, and SQL statements having references to the parameter variables interspersed therein, and wherein the rule generator service is to generate a rule representing modified SQL statements having the interspersed references.

15. The system of claim 14 further comprising, a scheduling service to receive scheduling constraints for executing the rule or an application have the rule embedded therein.

16. The system of claim 14 further comprising, an execution service to interpret the rule when executed for purposes of dynamically acquiring parameter values for the parameter variables.

17. The system of claim 16, wherein the execution service is invoked automatically when the rule is executed, and wherein the execution service acquires the parameter values from at least one of another service, via interactive prompting of a runtime user, via a data store table lookup, via a file lookup, and via command line parameter values.

18. The system of claim 14, wherein GUI tool is segmented into a plurality of frames, and wherein at least one frame dynamically presents the modified SQL statements as the user constructs the rule in a different one of the frames.

19. The system of claim 14, wherein the rule is at least one of a data store query, a report, and a plan, or wherein the rule is at least a part of another data store query, another report, or another plan.

20. The system of claim 14, wherein the parameter types for the parameter variables are enforced against parameter values supplied at runtime for the rule.