WO2015016807A1 - Analyse et validation de bases de données - Google Patents

Analyse et validation de bases de données Download PDF

Info

Publication number
WO2015016807A1
WO2015016807A1 PCT/US2013/052461 US2013052461W WO2015016807A1 WO 2015016807 A1 WO2015016807 A1 WO 2015016807A1 US 2013052461 W US2013052461 W US 2013052461W WO 2015016807 A1 WO2015016807 A1 WO 2015016807A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
schema
differences
user
database object
Prior art date
Application number
PCT/US2013/052461
Other languages
English (en)
Inventor
Geethapriyan HARIKRISHNAN
Sivapratha MARIMUTHU
Jonathan David Gibson
Original Assignee
Hewlett-Packard Development Company, L.P.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett-Packard Development Company, L.P. filed Critical Hewlett-Packard Development Company, L.P.
Priority to PCT/US2013/052461 priority Critical patent/WO2015016807A1/fr
Publication of WO2015016807A1 publication Critical patent/WO2015016807A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/211—Schema design and management

Definitions

  • a database management tool is configured with functionality for a specific database platform (e.g., ORACLE®, MICROSOFT SQL SERVER®, MYSQL®, SYBASE®, etc.).
  • the database management tool may be licensed individually per user and installed on a client computing device. Further, the database management tool may be specialized to perform a specific function such as comparing, validating, or performing health check-ups for databases.
  • ORACLE® and MYSQL® are registered trademarks of Oracle Corporation, which has its headquarters in Redwood City, California.
  • MICROSOFT SQL SERVER® is a registered trademark of Microsoft Corporation, which has its headquarters in Redmond, Washington.
  • SYBASE ® is a registered trademark of Sybase, Inc., which has its headquarters in Dublin, California.
  • FIG. 1 is a block diagram of an example computing device for providing database analysis and validation
  • FIG. 2 is a block diagram of an example computing device in communication with databases and user devices for providing database analysis and validation;
  • FIG. 3 is a flowchart of an example method for execution by a computing device for comparing database objects
  • FIG. 4 is a flowchart of an example method for execution by a computing device for providing database analysis and validation
  • FIG. 5 is a diagram of an example user interface of a web browser in which a stored procedure version comparison is displayed
  • FIG. 6 is a diagram of an example user interface of a web browser in which a database objects comparison is displayed
  • FIG. 7 is a diagram of an example user interface of a web browser in which a database structure comparison is displayed.
  • FIG. 8 is a diagram of an example user interface of a web browser in which a stored procedure code comparison is displayed.
  • prior database management solutions are typically compatible with a single database platform and capable of performing a specific information management function. Accordingly, current solutions are disparate applications from different technology providers (usually the vendors of the database platforms). The management applications operate in non-integrated, disjointed fashion because each provider's information management platform tool has a unique user interface and security model that is not integrated with tools from other providers.
  • Example embodiments disclosed herein provide database analysis and validation. For example, in some embodiments, schema information is obtained for a first database object of a first database and a second database of a second database, where the first database and the second database are compatible with different database platforms. At this stage, differences between the first database object and the second database object are determined using the schema information. The differences are then used to generate a difference display that includes a missing element that is included in the first database object but is not included in the second database object and an element that exists in the first database object and the second database object but is modified in the second database object.
  • FIG. 1 is a block diagram of an example server computing device 100 for providing database analysis and validation.
  • Server computing device 100 may be any computing device accessible by user computing devices, such as user device A 260A and user device N 260N of FIG. 2.
  • server computing device 100 includes a processor 110, an interface 115, and a machine-readable storage medium 120.
  • Processor 110 may be one or more central processing units (CPUs), microprocessors, and/or other hardware devices suitable for retrieval and execution of instructions stored in machine-readable storage medium 120.
  • Processor 110 may fetch, decode, and execute instructions 122, 124, 126 to provide database analysis and validation, as described below.
  • processor 110 may include one or more electronic circuits comprising a number of electronic components for performing the functionality of one or more of instructions 122, 124, 126.
  • Interface 115 may include a number of electronic components for communicating with databases and user computing devices.
  • interface 115 may be an Ethernet interface, a Universal Serial Bus (USB) interface, an IEEE 1394 (Firewire) interface, an external Serial Advanced Technology Attachment (eSATA) interface, or any other physical connection interface suitable for communication with the user computing device.
  • interface 115 may be a wireless interface, such as a wireless local area network (WLAN) interface or a near-field communication (NFC) interface.
  • WLAN wireless local area network
  • NFC near-field communication
  • interface 115 may be used to send and receive data, such as schema data, difference data, and user configuration data, to and from a corresponding interface of a user computing device.
  • Machine-readable storage medium 120 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions.
  • machine-readable storage medium 120 may be, for example, Random Access Memory (RAM), an Electrically-Erasable Programmable Read-Only Memory (EEPROM), a storage drive, an optical disc, and the like.
  • RAM Random Access Memory
  • EEPROM Electrically-Erasable Programmable Read-Only Memory
  • storage drive an optical disc, and the like.
  • machine-readable storage medium 120 may be encoded with executable instructions for providing database analysis and validation.
  • Schema obtaining instructions 122 may obtain schema information from databases. Specifically, schema obtaining instructions 122 may obtain schema information describing database objects such as database tables, stored procedures, database views, etc. For example, schema information may describe the data columns and corresponding data types of a database table. In another example, schema information may describe parameters, outputs, permissions, and code of a stored procedure. Schema obtaining instructions 122 may obtain the schema information to satisfy a request from a user of the server computing device 100. For example, a user may request a comparison of two database tables from two different databases. In this example, schema obtaining instructions 122 may obtain the schema information from the two databases so that the two database tables may be compared as described below.
  • Differences identifying instructions 124 may identify differences between the schemas of database objects from different databases. If the database objects are data tables, the differences may be identified by analyzing and comparing the schemas of the data tables to determine differences between the data columns and key designations. For example, the names of the data columns in the data tables may be compared to determine if any columns have been added, modified, or deleted. In this example, the data types of matching data columns may be compared to determine if any column names have been modified. Further, the data types of matching columns may also be compared to determine if there are any data length mismatches between the matching columns. In another example, data residing in data tables may be compared to identify data records that have been added, modified, or deleted.
  • Differences display generating instructions 126 may generate a difference display based on the differences identified by the differences identifying instructions 124.
  • the difference display may be generated in a tabular format, where changes and modifications between the database objects are color coded.
  • the difference display may also include identifiers and descriptions of the components of the database objects that are being compared. If the database objects are data tables or data views, the difference display may include column names and data types. If the database objects are stored procedures, the difference display may include a comparison of the source code of the stored procedures as discussed below with respect to FIG. 8.
  • FIG. 2 is a block diagram of an example server computing device 200 in communication via a network 245 with databases (e.g., database A 250A, database N 250N) and user devices (e.g., user device A 260A, user device N 260N). As illustrated in FIG. 2 and described below, server computing device 200 may communicate with databases and user devices to provide database analysis and validation.
  • databases e.g., database A 250A, database N 250N
  • user devices e.g., user device A 260A, user device N 260N.
  • server computing device 200 may communicate with databases and user devices to provide database analysis and validation.
  • server computing device 200 may include a number of modules 202-224. Each of the modules may include a series of instructions encoded on a machine-readable storage medium and executable by a processor of the server computing device 200. In addition or as an alternative, each module may include one or more hardware devices including electronic circuitry for implementing the functionality described below.
  • server computing device 200 may be a notebook, desktop, tablet, workstation, mobile device, or any other device suitable for executing the functionality described below. As detailed below, server computing device 200 may include a series of modules 202-224 for enabling database analysis and validation.
  • Interface module 202 may manage communications with the databases (e.g., database A 250A, database N 250N) and the user devices (e.g., user device A 260A, user device N 260N). Specifically, the interface module 202 may (1) initiate connections with the databases and then send or receive schema data 232 to/from the databases and (2) initiate connections with the user devices and then send or receive difference data 234 to/from the user devices.
  • the databases e.g., database A 250A, database N 250N
  • the user devices e.g., user device A 260A, user device N 260N.
  • the interface module 202 may (1) initiate connections with the databases and then send or receive schema data 232 to/from the databases and (2) initiate connections with the user devices and then send or receive difference data 234 to/from the user devices.
  • Database module 206 may access and manage data in the databases (e.g., database A 250A, database N 250N). Although the components of database module 206 are described in detail below, additional details regarding an example implementation of module 206 are provided above in connection with instructions 122 of FIG. 1.
  • Structured Query Language (SQL) command module 208 may build and execute SQL commands on the databases (e.g., database A 250A, database N 250N).
  • the SQL commands may query, modify, or create database objects in the databases (e.g., database A 250A, database N 2 SON).
  • the SQL commands may be generated for different database providers based on the SQL syntax of the target database (e.g., database A 250A, database N 250N).
  • SQL query commands may be generated to query the database (e.g., database A 250A, database N 250N) for schema data 232 associated with database objects.
  • SQL alter commands may be generated to synchronize a database object with another.
  • a SQL alter command may be generated based on differences identified between the database objects as described below.
  • Schema module 210 may manage schema data 232 obtained from databases (e.g., database A 250A, database N 250N). For example, schema module 210 may use the schema data to build data structures that are used by the comparison module 212. In another example, schema module 210 may log schema data obtained from a database (e.g., database A 250A, database N 250N). In this example, the schema module 210 may manage a history of schema data 232 for database objects in a database (e.g., database A 250A, database N 250N). The history of schema data 232 may be used to perform snapshot comparisons of the databases as described below. In other words, historical database schemas may be compared to other databases even though no active databases include the historical database schemas. [0028] Comparison module 212 may compare database objects using schema data 232 obtained by database module 206. Although the components of comparison module 212 are described in detail below, additional details regarding an example implementation of module 212 are provided above in connection with instructions 124 of FIG. 1.
  • Object comparison module 214 may compare schema data of database objects to identify differences between the database objects. For example, the schema data of data tables from different databases may be compared to identify differences in data columns and data types. In another example, the data in data tables may be compared to identify data records that have been added, modified, or deleted. In yet another example, the schema data of stored procedures may be compared to identify differences in procedure headers and source code. The identified differences may be stored as difference data 234 in storage device 230.
  • Object validation module 216 may use schema data to validate a database object. Validation of a database object may include confirming that the database object conforms to user configurations specified by the user using the user interface module 220. For example, objection validation module 210 may confirm that data tables and/or stored procedures conform to user-specified naming standard for a database (e.g., database A 250A, database N 250N). Validation of a database object may also include a validation of readability, a rollback validation, versioning validation, a health check-up, etc. In the case of versioning, the version of stored procedures may be extracted from metadata in the source code that is formatted as defined by a user.
  • Health check-ups may include environmental health check-ups (e.g., CPU utilization bottlenecks, database jobs, tablespace information, etc.), schema health checks (e.g., session statistics, hit/miss ratios, contention/locking, data dictionary information, rollback segments, etc.), and performance health checks (full table scans, cursor/SQL processing, etc.).
  • Validation of the database may be performed automatically at scheduled intervals, where the results of the validation are provided to an administrator of the target database(s).
  • User interface module 220 may provide a database management application to users of user devices (e.g., user device A 260A, user device N 260N). Although the components of user interface module 220 are described in detail below, additional details regarding an example implementation of module 220 are provided above in connection with instructions 126 of FIG. 1.
  • User configuration module 222 may provide user interface elements for receiving configuration parameters from user devices (e.g., user device A 260A, user device N 260N).
  • Configuration parameters may include naming standards for database objects or versioning metadata formatting.
  • Configuration parameters may also include parameters included in a analysis request from user devices (e.g., user device A 260A, user device N 260N).
  • a analysis request may request a comparison of database objects or databases and may include parameters such as the type of comparison or the selection of database objects to be compared. For example, a analysis request may specify that a version comparison should be performed for all stored procedures in two different databases. In another example, a analysis request may specify that a structure comparison should be performed for all data tables in two different databases.
  • Configuration parameters may be stored in storage device 230 as user configuration data 236.
  • each user is allocated a separate subset of the databases (e.g., database A 250A, database N 250N) as specified by user permissions.
  • a user may only perform database management on the databases he has access to.
  • access to the databases assigned to a user may be encrypted such that it is associated with the credentials of the user.
  • Display module 224 may generate comparison displays for user devices (e.g., user device A 260A, user device N 260N). For example, identified differences between database objects may be included in a difference display for review by a user of a user device (e.g., user device A 260A, user device N 260N). The comparison displays may be rendered in a tabular format such as described below with respect to FIGS. 5-8. In some cases, consolidated reports including multiple types of comparison may be generated. In this case, the consolidated reports may be filterable and sortable by the user. [0035] Storage device 230 may be any hardware storage device for maintaining data accessible to server computing device 200.
  • storage device 230 may include one or more hard disk drives, solid state drives, tape drives, and/or any other storage devices.
  • the storage devices may be located in server computing device 200 and/or in another device in communication with server computing device 200.
  • storage device 230 may maintain schema data 232, difference data 234, and user configuration data 236.
  • Databases may be any database accessible to server computing device 200 over the network 245 that is suitable for providing database content.
  • Databases e.g., database A 250A, database N 250N
  • User devices may be local, networked, or cloud user devices accessible to server computing device 200 via the network 245.
  • Each user device e.g., user device A 260A, user device N 260N
  • FIG. 3 is a flowchart of an example method 300 for execution by a server computing device 100 for providing database analysis and validation. Although execution of method 300 is described below with reference to server computing device 100 of FIG. 1 , other suitable devices for execution of method 300 may be used, such as server computing device 200 of FIG. 2. Method 300 may be implemented in the form of executable instructions stored on a machine- readable storage medium, such as storage medium 120, and/or in the form of electronic circuitry.
  • Method 300 may start in block 305 and continue to block 310, where server computing device 100 obtains a first scheme for a first database object of a first database.
  • the first database object may be a data table, data view, or stored procedure.
  • the first schema may describe the structure of the first database object.
  • a second schema for a second database object of a second database may be obtained.
  • the second schema may describe the structure of the second database object.
  • the first database and the second database may be compatible with different database platforms.
  • the first schema and the second schema may be analyzed to identify differences between the first database object and the second database objects. For examples, differences between the data columns and data types of data tables may be identified.
  • a difference display including the differences identified in block 320 may be generated. For example, the difference display may be as described below with respect to FIGS. 5-8. Method 300 may then continue to block 330, where method 300 may stop.
  • FIG. 4 is a flowchart of an example method 400 for execution by a server computing device 100 for database analysis and validation. Although execution of method 400 is described below with reference to server computing device 100 of FIG. 1 , other suitable devices for execution of method 400 may be used, such as server computing device 200 of FIG. 2. Method 400 may be implemented in the form of executable instructions stored on a machine-readable storage medium, such as storage medium 120, and/or in the form of electronic circuitry.
  • Method 400 may start in block 405 and continue to block 410, where server computing device 100 may display a user interface for database management.
  • the user interface may be presented as a web application that is accessible to user devices. After user credentials are provided, the web application may provide access to the database management functionality.
  • an analysis request is received from a user via the user interface. The analysis request may specify the type of analysis and the set of database objects that should be analyzed.
  • schema information is obtained from the database(s).
  • the schema information may describe the structure of the data tables in the database(s).
  • the schema information may include procedure headers and source code for the stored procedures in the database(s).
  • the schema information is analyzed to generate output. For example, a difference display may be generated that includes identified differences between database objects. In another example, a validation display may be generated that shows the results of a validation analysis of database objects of a database.
  • the output is provided to the user.
  • the output may be display via the web application.
  • the output may be provided in a tabular format such as a spreadsheet file.
  • the output may be sent via electronic mail to the user.
  • Method 400 may then continue to block 435, where method 400 may stop.
  • FIG. 5 is a diagram of an example user interface 500 of a web application in which a difference display for a stored procedure version comparison is shown.
  • the user interface 500 includes a legend 510 describing the rows of the differences 550, 555 shown in tabular format.
  • the user interface 500 also includes an export button 515, an email button 520, and a back button 525.
  • the export button 515 may be selected by the user to export the differences 550, 555 to a spreadsheet file.
  • the email button 520 may be selected by the user to email the differences 550, 555 to a target user.
  • the back button 525 may be selected by the user to navigate to the main menu of the web application.
  • the user interface 500 includes a scroll bar for 560 for browsing the list of differences 550, 555.
  • the columns 530, 535, 540, 545 of the differences 550, 555 are shown.
  • the object type 530 of each of the differences 550, 555 is shown as PROCEDURE, which shows that the differences are related to stored procedures.
  • the object name 535 of the columns 530, 535, 540, 545 shows the name of each of the stored procedures.
  • the first database column 540 and the second database column 545 show the versions of the databases being compared in the user interface 500.
  • difference 550 shows that the stored procedure named SP_NAME_1 has the same version in database 1 ("DB ) and database 2 ("DB 2")
  • difference 555 shows that the stored procedure named SP NAME 2 is version 1 in DB 1 and version 5 in DB 2.
  • FIG. 6 is a diagram of an example user interface 600 of a web application in which a difference display for a stored procedure comparison is shown.
  • the user interface 600 includes a legend 610 describing the rows of the differences 650, 655 shown in tabular format.
  • the user interface 600 also includes an export button 615, an email button 620, and a back button 625.
  • the columns 630, 635, 640 of the differences 650, 655 are shown.
  • the object type 630 of each of the differences 650, 655 is shown as PROCEDURE, which shows that the differences are related to stored procedures.
  • the user interface 600 includes a scroll bar for 660 for browsing the list of differences 650, 655.
  • the first database column 635 and the second database column 640 show the stored procedure names of the databases being compared in the user interface 600.
  • difference 650 shows that both database 1 and database 2 have a stored procedure named SP_SAVE_ENTITY
  • difference 655 shows that database 1 has a stored procedure named SP_RETRIEVE_ENTITY that is not included in database 2.
  • FIG. 7 is a diagram of an example user interface 700 of a web application in which a difference display for a data table comparison is shown.
  • the user interface 700 includes a legend 710, 712 describing the rows of the differences 750, 755, 757 shown in tabular format.
  • the legend 710, 712 may show that the differences 750, 755, 757 are rendered in different colors based on the type of difference.
  • the user interface 700 also includes an export button 715, an email button 720, and a back button 725.
  • the columns 735, 740 of the differences 750, 755, 760 are shown.
  • the user interface 700 includes a scroll bar for 760 for browsing the list of differences 750, 755, 757.
  • the first database column 735 and the second database column 740 show the data table names of the databases being compared in the user interface 700.
  • difference 750 shows that both database 1 and database 2 have a data table named TBL_ENTITY
  • difference 755 shows that database 1 has a data table named TBL_ENTITY_ORDERS that is not included in database 2
  • difference 757 shows that both database 1 and database 2 have a data table named TBL_RECORD_DETAILS but that the table has been modified in database 2.
  • FIG. 8 is a diagram of an example user interface 800 of a web application in which a difference display for a stored procedure source code comparison is shown.
  • the user interface 800 includes a legend 810, 812 describing the rows of the differences 850, 855, 859 shown in tabular format.
  • the user interface 800 also includes an export button 815, an email button 820, and a back button 825.
  • the columns 835, 840 of the differences 850, 855, 859 are shown.
  • the user interface 800 also shows the name of the stored procedure 830 being compared in the difference display.
  • the user interface 800 includes a scroll bar for 860 for browsing the list of differences 850, 855, 859.
  • the first database column 835 and the second database column 840 show the lines of source code of the stored procedure being compared between database 1 and database 2.
  • difference 850 shows that both database 1 and database 2 have the same procedure header
  • difference 855 shows that database 1 returns a VARCHAR2 data type and database 2 returns a BLOB data type
  • difference 859 shows that both database 1 includes a line of source code that is not included in database 2.
  • the differences 850, 855, 859 also show source code comments that are formatted to include versioning information. The version of the stored procedure in each of the databases may be extracted from the source code comments.
  • FIGS. 5-8 show user interfaces for comparing two different databases; however, any number of databases may be compared as described above.
  • an additional column may be added to the difference displays as shown for each of the additional databases.
  • a consolidated difference display may be generated to include two or more of the difference displays shown in FIGS. 5-8.
  • the foregoing disclosure describes a number of example embodiments for providing database analysis and validation by a server computing device.
  • the embodiments disclosed herein enable analysis and validations for databases by cross-platform management application that generates unified displays of modifications and omissions between database objects.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Les modes de réalisation illustratifs concernent l'analyse et la validation de bases de données. Dans les modes de réalisation illustratifs, des informations de schémas sont obtenues pour un objet d'une première base de données et pour un objet d'une seconde base de données, les première et seconde bases de données étant compatibles avec différentes plates-formes de bases de données. Puis les différences entre l'objet de la première base de données et l'objet de la seconde base de données sont déterminées en utilisant les informations de schémas. Les différences sont alors utilisées pour créer un affichage des différences qui comprend un élément manquant qui fait partie de l'objet de la première base de données mais pas de l'objet de la seconde base de données et un élément qui existe dans l'objet de la première base de données et, sous une forme modifiée, dans l'objet de la seconde base de données.
PCT/US2013/052461 2013-07-29 2013-07-29 Analyse et validation de bases de données WO2015016807A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2013/052461 WO2015016807A1 (fr) 2013-07-29 2013-07-29 Analyse et validation de bases de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/052461 WO2015016807A1 (fr) 2013-07-29 2013-07-29 Analyse et validation de bases de données

Publications (1)

Publication Number Publication Date
WO2015016807A1 true WO2015016807A1 (fr) 2015-02-05

Family

ID=52432184

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/052461 WO2015016807A1 (fr) 2013-07-29 2013-07-29 Analyse et validation de bases de données

Country Status (1)

Country Link
WO (1) WO2015016807A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017105700A1 (fr) * 2015-12-15 2017-06-22 Intel Corporation Classification souple de paquets à grande vitesse à l'aide de processeurs de réseau
CN113535727A (zh) * 2021-07-19 2021-10-22 北京数码大方科技股份有限公司 信息系统的数据输出方法及数据输出装置、电子设备
US11334235B2 (en) * 2020-02-28 2022-05-17 Ge Aviation Systems Llc Comparison interface for navigation data

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050149543A1 (en) * 2003-11-24 2005-07-07 Ebay Inc. Backward compatibility in database schemas
US20090037769A1 (en) * 2007-06-19 2009-02-05 Sergey Babkin Dynamic modification of schemas in streaming databases
US20090119319A1 (en) * 2005-06-27 2009-05-07 International Business Machines Corporation System for detecting migration differences of a customized database schema

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050149543A1 (en) * 2003-11-24 2005-07-07 Ebay Inc. Backward compatibility in database schemas
US20090119319A1 (en) * 2005-06-27 2009-05-07 International Business Machines Corporation System for detecting migration differences of a customized database schema
US20090037769A1 (en) * 2007-06-19 2009-02-05 Sergey Babkin Dynamic modification of schemas in streaming databases

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ALI, SYED MOULA: "How to Compare Database Schema in VS 2012, How to Update the Target Database to the Server", 4 March 2013 (2013-03-04), Retrieved from the Internet <URL:http://www.codeproject.com/Tips/555932/How-to-Compare-Database-Schema> *
MICROSOFT DEVELOPER NETWORK: "Compare and Synchronize Database Schemas", MSDN LIBRARY FOR VISUAL STUDIO 2010, 2010, Retrieved from the Internet <URL:http://msdn.microsoft.com/en-us/library/dd193250(v=vs.100).aspx> *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017105700A1 (fr) * 2015-12-15 2017-06-22 Intel Corporation Classification souple de paquets à grande vitesse à l'aide de processeurs de réseau
US11418632B2 (en) 2015-12-15 2022-08-16 Intel Corporation High speed flexible packet classification using network processors
US11334235B2 (en) * 2020-02-28 2022-05-17 Ge Aviation Systems Llc Comparison interface for navigation data
CN113535727A (zh) * 2021-07-19 2021-10-22 北京数码大方科技股份有限公司 信息系统的数据输出方法及数据输出装置、电子设备
CN113535727B (zh) * 2021-07-19 2024-04-09 北京数码大方科技股份有限公司 信息系统的数据输出方法及数据输出装置、电子设备

Similar Documents

Publication Publication Date Title
US11789942B2 (en) Dynamic asset monitoring and management using a continuous event processing platform
US20200125530A1 (en) Data management platform using metadata repository
US10976907B2 (en) Declarative external data source importation, exportation, and metadata reflection utilizing http and HDFS protocols
US8751486B1 (en) Executing structured queries on unstructured data
CN105144080B (zh) 用于元数据管理的系统
US9165049B2 (en) Translating business scenario definitions into corresponding database artifacts
US20200210641A1 (en) Techniques for view capture and storage for mobile applications
US20120310875A1 (en) Method and system of generating a data lineage repository with lineage visibility, snapshot comparison and version control in a cloud-computing platform
US9785725B2 (en) Method and system for visualizing relational data as RDF graphs with interactive response time
US10216769B1 (en) Asset catalog management methods and systems
US20120278334A1 (en) Database System
US9171051B2 (en) Data definition language (DDL) expression annotation
CN111046036A (zh) 数据同步方法、装置、系统及存储介质
CN113051268A (zh) 数据查询方法、数据查询装置、电子设备及存储介质
US7840603B2 (en) Method and apparatus for database change management
CN117171108B (zh) 一种虚拟模型映射方法和系统
EP2904520B1 (fr) Repartition des references d&#39;un tableau simple aux tableaus multiples
WO2015016807A1 (fr) Analyse et validation de bases de données
US20210350071A1 (en) Techniques for document marker tracking
US11693859B2 (en) Systems and methods for data retrieval from a database indexed by an external search engine
US20070282804A1 (en) Apparatus and method for extracting database information from a report
US20230289331A1 (en) Model generation service for data retrieval
US11188228B1 (en) Graphing transaction operations for transaction compliance analysis
US10885157B2 (en) Determining a database signature
US20240211485A1 (en) Systems and methods for generating charts, extracting data, and executing commands in reports

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13890636

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13890636

Country of ref document: EP

Kind code of ref document: A1