Data base development system with methods facilitating copying of data from one data source to another

• US 5,937,415 A
• Filed: 12/11/1996
• Issued: 08/10/1999
• Est. Priority Date: 12/13/1995
• Status: Expired due to Term

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Sheffield, Kim A., Preston, Alan L.
• Primary Examiner(s): Kulik, Paul V.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US08/763,467
• Time in Patent Office: 972 Days
• Field of Search: 707/4, 707/102, 707/200, 707/201, 707/204, 707/526, 345/339
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A Client/Server Database System with improved methods for performing database queries, particularly DSS-type queries, is described. The system includes one or more Clients (e.g., Terminals or PCs) connected via a Network to a Server. In general operation, Clients store data in and retrieve data from one or more database tables resident on the Server by submitting SQL commands, some of which specify "queries"--criteria for selecting particular records of a table. The system implements a "Data Pipeline" feature for programming replication of data from one database to another in client applications. Specifically, a pipeline object and SQL SELECT statement are built using a Pipeline Painter. The Data Pipeline lets a user (developer) easily move data from a high-end database server (e.g., Sybase) to a local database (Watcom SQL), all without the user having to issue SQL commands. The pipeline object facilitates moving data from one database management system to another, or between databases of the same type.

Claims

1. A method for copying data from one data source to another, the method comprising:

selecting source and destination database profiles for source and destination data sources, respectively, each profile comprising sufficient information for supporting a connection to a respective one of the source and destination data sources;

establishing a connection to said source and destination data sources;

displaying a graphical user interface for graphically defining a pipeline object, said pipeline object specifying particular data to copy from the source data source to the destination data source;

saving said pipeline object to a storage device, so that it can be executed upon invocation; and

copying data from the source data to the destination data by executing said pipeline object;

wherein displaying a graphical user interface step includes;

receiving user input for graphically creating a SQL SELECT statement which specifies the data to be copied from the source data to the destination data.

2. The method of claim 1, wherein displaying a graphical user interface step includes:

specifying that copying of data from the source data source to the destination data source includes appending the data to the destination data source.

3. The method of claim 1, wherein displaying a graphical user interface step includes:

specifying that copying of data from the source data source to the destination data source includes updating the destination data source.

4. The method of claim 1, wherein displaying a graphical user interface step includes:

specifying that copying of data from the source data source to the destination data source includes creating a new database table at the destination data source.

5. The method of claim 1, wherein said pipeline object executes in response to invocation from a user-supplied script.

6. The method of claim 1, wherein said source data source comprises a first set of database tables and wherein said destination data source comprises a second set of database tables, each set residing on different servers.

7. The method of claim 1, wherein said data being copied comprises database rows selected from the source data source.

8. The method of claim 7, further comprising:

determining error rows, said error rows comprising those rows, if any, selected from the source data source would, if copied, lead to errors in the destination data source; and

foregoing any copying of such error rows.

9. The method of claim 8, further comprising:

displaying a user interface dialog allowing an end user at runtime to perform a selected one of repairing some or all such error rows or abandoning some or all such error rows.