2701 results about "Target database" patented technology

A system and method for searching information from a database using a natural language. In one embodiment, the system analyzes a natural language search request and converts the search request into one or more search words. The search words are further converted into a string of bytes, and a subset of a target database, referred to as the datasoup, is searched. If there is a match between the bytes and raw data in the datasoup, the searched data is retrieved from the target database. The searched data is then formatted and provided to a user. Optionally, the searched data can be provided to the user unformatted. In another embodiment, the system includes a system server configured to receive a natural language search request, a core engine coupled to the system server and to the target database, and a system database coupled to the core engine, where the core engine accesses the system database to analyze the search request. The system database stores global rules, one or more preference files, and one or more dictionaries, and the preference file stores information about the user.

Tokens are used to prepare a target database for replication from a source database and to confirm the preparation in an asynchronous coordinated commit replication process. During a dual write replication process, transmission of the replicated data and locking of data records in the target database occurs only on updates.

During replication of transaction data from a source database to a target database via a change queue associated with the source database, one or more multiple paths are provided between the change queue and the target database. The one or more multiple paths cause at least some of the transaction data to become unserialized. At least some of the unserialized data is reserialized prior to or upon applying the originally unserialized transaction data to the target database. If the current transaction load is close or equal to the maximum transaction load capacity of a path between the change queue and the target database, another path is provided. If the maximum transaction threshold limit of an applier associated with the target database has been reached, open transactions may be prematurely committed.

In a database synchronization process, a block of data is read from a source database at the first node. A marker is assigned to the block of data, and the marker is then written to an audit trail at the first node. The marker is sent from the audit trail to a second node having a target database. The block of data is sent from the first node to the second node without passing the block of data through the audit trail. At the second node, the block of data is stored in the target database upon receipt at the second node of the block of data and the marker assigned to the block of data. This process is repeated for additional blocks of data in the source database, wherein a marker is assigned to each subsequent block of data. In this manner, some or all of the source database may be replicated to the target database without having to store or pass any data in the source database in or through the audit trail at the first node.

Techniques exporting data and metadata from a source database environment to a target database environment are provided. The techniques include the steps of analyzing metadata that describes one or more items, the data for which is in a source database, where the one or more items include at least one of a view, a sequence, a dimension, a cube, an ETL mapping, and any database object for which the metadata is stored outside of the source and target databases. The data for each item resides in a data file associated with the source database. The data for each item is incorporated into the target database based on the metadata by providing the target database access to an incorporated data file, where the incorporated data file is the data file or a copy thereof. Techniques are also provided for exporting database data from the source database. The techniques include extracting metadata that describes one or more items, the data for which is in the source database, where the one or more items include at least one of the structures described above. The data for each item resides in a data file associated with the source database. After the exporting, a database server that manages the target database is provided access to an incorporated data file, where the incorporated data file is the data file or a copy thereof.

A method and system for migrating data between databases is provided. Metadata is obtained from a source database and used to determine the manner in which the data within the source database should be migrated to a target database. The metadata provides a mechanism for structuring queries to retrieve the data within the source database in a generic manner, thereby providing a generic determination of the structure of the data to be migrated. The dependencies among tables in the source database are discovered, thereby providing an order to the migration operations to be performed when migrating the data. This order ensures that the data can be migrated correctly in the presence of referential integrity (foreign key) constraints. In addition, custom mapping operations may be performed during the migration operations so that the data from the source database is modified before writing the data to the target database.

The invention relates to a distributed-type database access method and system. The distributed-type database access method comprises: 1. a Web server sends a database access request to a proxy server; 2. the proxy server analyzes the database access request according to a preset analysis rule, and sends the analyzed database access request to a corresponding target database; and 3. the proxy serve sends a result returned by the target database to the Web server. The invention avoids risk of high cost brought by the centralized management of the database and avoids the risks that the whole system fails because of the fault of the single database, the system scale has small possibility of expanding and is limited and the like. The invention effectively realizes the reasonable distribution of physical resources, lowers communication cost, has strong expansibility, can dynamically distribute data flow, and can separate reading from writing; and under the condition of limited resource, performance is maximized.

A system, method and computer program product for enabling light weight table comparison with high-accuracy (high confidence) of tables where one is a copy of the other, which copy may be maintained synchronized by replication. The method performs database comparison using a sample-based, statistics-based, or materialized query tables-based approaches. The method first identifies a block comprising a sub-set of rows of data of a source database table and a corresponding block from a target database table, and obtains a statistical value associated with each block. Then the statistical values for the corresponding source and target block are compared and a consistency evaluation of source and target database is determined based on comparing results. Further methods enable a determination of the data as being persistent or not in manner that accounts for real-time data modifications to underlying source and target database tables while identified blocks are being compared.

Systems and methods consistent with concepts of the present embodiment of the inventive concept provide mechanisms for database migration from one database (source database platform) platform to another (target database platform). The target and source databases can be any relational databases including, without limitation, Oracle, SQL Server (Microsoft), DB2 UDB (IBM), Sybase, MySQL, PostgreSQL, and the like. The inventive methodology will work well for migration of any relational database that implements SQL language from one platform to another. A feature of the invention is the provision of a virtual engine enabling the running of an original application on a migrated database.

A software distribution application (205,250,255) supporting the installation of operating systems on pristine computers (110) is proposed. A new configuration element (210) is added for virtually defining an operating system; the configuration element points to a corresponding image of the operating system on different pristine servers (120). Moreover, the pristine computers can be defined in a target database (220) before they actually exist; each pristine computer subscribes to a reference model (215) specifying the installation of the operating system. A plan (235) is then generated with actions for installing the operating system on the pristine computers. When the plan is submitted for execution, a plug-in module (250,255) associates each pristine computer with the image of the operating system on the respective pristine server. In this way, as soon as a pristine computer is turned on and transmits (458) a remote installation request to the pristine server the associated image is automatically installed (470-483).

A method is provided for loading data from a source database to a target database that includes at least one table. Prior to loading the data from the source database into the target database, at least one referential integrity constraint and/or at least one consistency requirement regarding the data is automatically identified. A subset of the data that satisfies the at least one referential integrity constraint and/or consistency requirement is then automatically identified. The identified subset of the data is then loaded into the target database as a unit of work.

The present invention is drawn to methods for designing synthetic nucleotide sequences encoding polypeptides of interest. The methods involve organizing a database of sequences as a set of N-length oligomer sequences and compiling a list of probability scores for each N-length sequence. The probability scores are used to substitute one or more higher-scoring sequences into the parent nucleotide sequence to generate an optimized sequence. The nucleotide sequence of interest may be further optimized by removing either or both of unintended open reading frames or undesired short DNA elements, and/or substituting oligomer sequences to achieve a specific G:C content. These methods may be used for optimizing expression of heterologous genes in any organism, particularly in plants. The method generates synthetic sequences with a composition similar to that of a target database. These synthetic sequences may be used, for example, for regulating pesticidal activity or herbicide resistance in organisms, particularly plants or plant cells.

A method of transferring batches of data to a target database includes receiving ordered rows of data and loading the ordered rows into batch tables. Each batch table being either a parent table, a child table or a no dependency table. The parent batch tables and no dependency batch tables are entered into a ready queue and the child batch tables are entered into a into a waiting pool. Any batch table in the ready queue may be transferred to the database using one or more processors. Any child batch table is moved to the ready queue if no corresponding parent table is in the ready queue. A dependency count of a child table is maintained and decremented if a parent table is imported to a database. In one embodiment, the corresponding child table in the waiting pool is transferred to the ready queue if the dependency count is zero.

The invention provides a data storage method, device and system based on a blockchain. The data storage system based on the blockchain comprises a transaction server which is used for performing a transaction according to an intelligent contract and a consensus mechanism and obtaining blockchain data; a database server routing and configuration unit which is used for dynamically configuring and routing a database server and obtaining a target database server, wherein the target database server is used for storing the blockchain data; a storage model calling unit which is used for calling a corresponding database access protocol from a uniform database drive interface of various database protocols and calling a corresponding storage model from a target database; and the database server which is used for storing the blockchain data to a database in the storage model and/or a data table.

The invention discloses a data migration method and device used for a database. One specific implementation way of the method comprises the following steps: establishing the mirror image of a source database, migrating total-amount data in the mirror image into a target database, and detecting incremental data in the source database; migrating the detected incremental data to the target database; and when all the incremental data in the source database is migrated to the target database, switching the read and write operation of the database to the target database from the source database. The implementation way realizes on-line data migration between the databases.