WO2017081737A1 - Système de gestion de données - Google Patents

Système de gestion de données Download PDF

Info

Publication number
WO2017081737A1
WO2017081737A1 PCT/JP2015/081531 JP2015081531W WO2017081737A1 WO 2017081737 A1 WO2017081737 A1 WO 2017081737A1 JP 2015081531 W JP2015081531 W JP 2015081531W WO 2017081737 A1 WO2017081737 A1 WO 2017081737A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
server
business data
user
business
Prior art date
Application number
PCT/JP2015/081531
Other languages
English (en)
Japanese (ja)
Inventor
裕三 石田
宏徳 桂
健吾 矢治
信昭 小塚
明生 齊田
Original Assignee
株式会社野村総合研究所
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 株式会社野村総合研究所 filed Critical 株式会社野村総合研究所
Priority to PCT/JP2015/081531 priority Critical patent/WO2017081737A1/fr
Priority to JP2017549135A priority patent/JP6549245B2/ja
Priority to PCT/JP2016/082855 priority patent/WO2017078158A1/fr
Priority to EP16862217.3A priority patent/EP3373149A4/fr
Publication of WO2017081737A1 publication Critical patent/WO2017081737A1/fr
Priority to US15/965,232 priority patent/US11169984B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures

Definitions

  • the present invention relates to a data management system, and more particularly to a technique for storing and managing various business data generated by an AP server in a DB server.
  • Non-Patent Document 1 Japanese Patent Document 1
  • a second object of the present invention is to realize a data management technique that enables execution of batch processing in parallel with data accumulation without separating target data for batch processing and non-target data.
  • the data management system is a system including an AP server and a DB server, and only reference and addition of records are permitted in the table of the DB server, There is a restriction that deletion and updating are prohibited, and the AP server adds the data generation time as a time stamp to the business data generated as a result of the business processing, and then sends it to the DB server and the corresponding table. If you need to delete the existing business data and the function to request registration, create data cancellation data with a data item that sets the ID of the business data to be canceled. By additionally registering in the cancellation-only table provided in the DB server, it is necessary to effectively invalidate the existing business data and to update the existing business data.
  • update business data that has the same ID as the business data and has a corrected value and a time stamp at the time of correction is generated, and this business data for update is provided in the DB server. If you need to refer to business data at a specific point in the past, and a function that substantially updates existing business data by registering it in the corresponding table, the business data stored in the above table And a function of extracting corresponding business data based on the time recorded in the time stamp.
  • the data management system is the system according to claim 1, wherein the AP server is based on business data generated within a specific period of business data stored in the table.
  • the business data generated by the AP server is stamped with the data generation time as a time stamp, and the business data once generated is deleted and updated. Without being stored in the DB server table semi-permanently. For this reason, even if an unexpected data reference request occurs at a later date, there is an advantage that it can be flexibly handled.
  • the target data and non-target data for batch processing are identified by referring to the time stamp of each business data. Therefore, batch processing can be executed in parallel with data accumulation without separating target data and non-target data for batch processing.
  • FIG. 1 is an overall configuration diagram of a first data management system 10 according to the present invention.
  • a DB server 12, a first AP server 14, a second AP server 16, and a third AP server 18 are shown in FIG. It has.
  • the DB server 12, the first AP server 14, the second AP server 16, and the third AP server 18 are connected to each other via a communication network.
  • a purchase table 20 for example, a purchase cancellation table 22, a sales price table 24, and a sales price cancellation table 26 are provided.
  • the purchase table 20 is set with data items of purchase ID, supplier ID, product ID, quantity, price, and time stamp.
  • the purchase cancellation table 22 is set with data items of purchase ID and time stamp.
  • the sales price table 24 as shown in FIG. 2C, data items of sales price ID, product ID, price, and time stamp are set.
  • sales price cancellation table 26 as shown in FIG. 2D, sales price ID and time stamp data items are set.
  • each table is preliminarily imposed with restrictions on deletion (delete) prohibition and update (update) prohibition. That is, in this system 10, only addition (insert) and reference (select) to each table are allowed.
  • the sales price cancellation data is added to the sales price cancellation table 26 in FIG. 2 (d). . Since the sales price ID of this sales price is filled with the sales price ID of the sales price data to be canceled, the AP server uses the sales price data registered in the sales price table 24 when using this data. Among these, those whose sales price ID is registered in the sales price cancellation table 26 are ignored as being out of scope.
  • the registration data needs to be corrected in this system 10
  • the AP server when modifying the "quantity" of certain purchase data, the AP server newly generates purchase data with the same purchase ID, supplier ID, product ID, and price, but only the quantity changed.
  • the data is transmitted to the server 12 and additionally registered in the purchase table 20.
  • the time when each data was generated is recorded in the time stamp with millisecond accuracy, so the AP server references Sometimes you can definitely identify the latest data.
  • the first AP server 14 accepts purchase data and purchase cancellation data transmitted from the client terminal 30 operated by the purchase staff 28 assigned to each place, and SQL statements corresponding to the contents of each data. Is issued to the DB server 12 and is registered in the purchase table 20 and the purchase cancellation table 22.
  • the second AP server 16 has a function of generating sales price data for the next day by batch processing based on the purchase data generated on the previous day.
  • the processing contents of the second AP server 16 will be described with reference to the flowchart of FIG.
  • the second AP server 16 reads the purchase data for the previous day from the purchase table 20 (S10).
  • the execution date of the batch processing is October 22, the purchase data generated on October 21 corresponds.
  • the second AP server 16 refers to the time stamp so that the target data for batch processing (data generated on October 21) and the non-target data ( Data generated before October 21 or on October 22) can be clearly distinguished.
  • the second AP server 16 refers to the purchase cancellation table 22 and invalidates the purchase data for the previous day subject to batch processing that has a purchase ID registered in the purchase cancellation table.
  • the purchase data is excluded (S12).
  • the second AP server 16 aggregates the purchase price and quantity of each valid purchase data for each product, and calculates the average purchase price for the previous day of each product (S14).
  • the second AP server 16 calculates a selling price for the next day (October 23rd) of each product by adding a predetermined profit to the average purchase price (S16).
  • the second AP server 16 stores the sales price data for the next day of each product in the sales price table 24 during the day (October 22) (S18).
  • the second AP server 16 sends the sales price cancellation data with the sales price ID of the sales price data to the DB server 12 for sales. Register in the price cancellation table 26
  • the third AP server 18 When the third AP server 18 receives a product price presentation request from the client terminal 30 operated by the general user 32, the third AP server 18 refers to the sales price table 24 and the sales price cancellation table 26 and sells each product effective on the day. It has a function of deriving a price and transmitting it to the client terminal 30 and a function of receiving a product order.
  • the sales price effective on the day for the third AP server 18 is the sales price cancellation data corresponding to the sales price data generated on the previous day (October 22) by the second AP server 16. This means that the price is not registered in the sales price cancellation table 26.
  • the third AP server 18 can accurately identify the sales price of each product to be presented on the day.
  • the data generated by each AP server of the system 10 is stamped with the data generation time as a time stamp, and the generated data is not permanently deleted or updated, and is semi-permanent. Are stored in each table. For this reason, for example, even if it becomes necessary to analyze the transition of the purchase price or sales price of a certain product at a later date, it is possible to flexibly cope with the aggregation of past data stored in each table.
  • FIG. 5 shows an example in which the system 10 is configured by the first DB server 12 and the second DB server 12 ′ in addition to the first AP server 14, the second AP server 16, and the third AP server 18. Show.
  • the number of DB servers is not limited to two, and it is desirable to install more DB servers.
  • each of the first DB server 12 and the second DB server 12 ′ includes a purchase table 20, a purchase cancellation table 22, a sales price table 24, and a sales price cancellation table 26.
  • the same data is stored in duplicate.
  • the first AP server 14 registers purchase data and the like, it generates a plurality of SQL statements having the same contents and simultaneously transmits the same data to the first DB server 12 and the second DB server 12 ′.
  • Request registration when the second AP server 16 registers sales price data, etc., a plurality of SQL statements having the same contents are generated and simultaneously applied to the first DB server 12 and the second DB server 12 ′.
  • Request data registration when the second AP server 16 registers sales price data, etc.
  • both the first DB server 12 and the second DB server 12 ′ are requested to extract the data. can do.
  • the AP server recognizes that a communication failure or machine trouble has occurred and moves the DB server to offline mode. . Specifically, the DB server is temporarily disconnected from the system 10, and the operation mode is based on only the remaining DB servers.
  • the disconnected DB server is inspected and necessary recovery measures are taken. For example, if it is determined that the registration completion notification has not arrived due to a failure of the communication device, replace the DB server with a new communication device, and then change the DB server to the write mode (only data writing is permitted, (Prohibited state) and copy the difference data from another DB server.
  • each business data is allowed to be added only, and a rule that does not allow deletion or update is applied. Therefore, data recovery is extremely easy.
  • deletion or update of data is allowed, in order to recover data, addition, deletion, or update of data is started from a certain point based on the update history information held by the DB server. It must be reproduced in order, and this takes a long time and a large load.
  • the DB server is set to the read / write mode (a state in which data writing and reference is allowed) and reconnected to the system 10.
  • FIG. 6 shows a second data management system 50 in which the present invention is applied to user data management work, and is composed of a DB server 52 and an AP server 54.
  • the DB server 52 includes a user table 56 and a user cancellation table 58.
  • DB server 52 For convenience of illustration, only one DB server 52 is illustrated, but a plurality of DB servers having tables common to each other can be used as described above.
  • data items such as a user ID, name, address, telephone number, mail address, and time stamp are set.
  • data items of user ID and time stamp are set.
  • the AP server 54 When a new user registration request is transmitted from the client terminal 62 operated by the user 60, the AP server 54 receives user data including data items such as a user ID, name, address, telephone number, e-mail address, and time stamp. Generate and request the DB server 52 to register in the user table 56.
  • the AP server 54 uses the same user ID, address, User data Y ′ having a telephone number and an e-mail address and having only the name changed to “Hanoko Unno” is newly generated and transmitted to the DB server 52 and additionally registered in the user table 56.
  • the time when each data was generated is recorded in the time stamp with millisecond accuracy.
  • the AP server 54 can definitely identify the latest data at the time of reference.
  • the AP server 54 User ID, name, and email address are provided, and the user data X 'with the address changed to "Mitaka City, Tokyo " and the phone number changed to "0422-45 " is newly generated and sent to the DB server 52. It is additionally registered in the user table 56.
  • the AP server 54 cancels the user with the user ID of the target user data each time.
  • Data A to C are sent to the DB server 52 and registered in the user cancellation table 58 to cope with this.
  • the AP server 54 should immediately perform searches, aggregations, etc. without using other records to recover the data. Can do.
  • the AP server 54 searches the user data Y with the old date and time recorded in the time stamp among the user data matching the user ID of the user data Y ′. By extracting, it can be immediately derived that the maiden name was "Saito".
  • the AP server 54 extracts user data relating to the user ID registered in the user cancellation table 58 from the user table 56, and each user data You can send a promotional email to your email address.
  • FIG. 1 is an overall configuration diagram of a first data management system.
  • FIG. It is a figure which shows an example of the table stored in DB server. It is a flowchart which shows the processing content of a 2nd AP server. It is a data structure figure which shows the processing content of a 2nd AP server. It is a figure which shows the example which installed several DB server. It is a whole block diagram of a 2nd data management system. It is a figure which shows an example of the table stored in DB server. It is a figure which shows the substantial update method and substantial deletion method of user data.
  • First data management system 12 DB server (first DB server) 12 'Second DB server 14 First AP server 16 Second AP server 18 Third AP server 20 Purchase table 22 Purchase cancellation table 24 Sales price table 26 Sales Price Cancellation Table 28 Purchasing staff 30 client terminals 32 General users 50 Second data management system 52 DB server 54 AP server 56 User table 58 User cancellation table 60 users 62 Client terminal

Landscapes

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

Abstract

Le problème décrit par la présente invention est de réaliser une technique de gestion de données avec laquelle il est possible de répondre de façon flexible même lorsqu'il devient nécessaire de se référer à des données passées pendant le fonctionnement du système. La solution selon l'invention porte sur un second système de gestion de données 50 comportant un serveur d'AP 54 et un serveur de BD 52. La table d'utilisateur 56 du serveur de BD 52 est soumise à des restrictions grâce auxquelles seulement une référence à un enregistrement, et un ajout de celui-ci, sont autorisés, et la suppression et la mise à jour d'un enregistrement sont interdites. Le serveur d'AP 54 ajoute une heure du jour à laquelle les données sont générées pour des données d'utilisateur sous la forme d'un horodatage et entraîne l'enregistrement de l'horodatage par le serveur de BD 52. Lorsqu'il est nécessaire de faire référence à des données d'utilisateur à un moment spécifique dans le passé, le serveur d'AP 54 extrait les données d'utilisateur sur la base de l'heure du jour enregistrée dans l'horodatage de chaque donnée d'utilisateur stockée dans la table d'utilisateur 56.
PCT/JP2015/081531 2015-11-06 2015-11-10 Système de gestion de données WO2017081737A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/JP2015/081531 WO2017081737A1 (fr) 2015-11-10 2015-11-10 Système de gestion de données
JP2017549135A JP6549245B2 (ja) 2015-11-06 2016-11-04 データ管理システム
PCT/JP2016/082855 WO2017078158A1 (fr) 2015-11-06 2016-11-04 Système de gestion de données
EP16862217.3A EP3373149A4 (fr) 2015-11-06 2016-11-04 Système de gestion de données
US15/965,232 US11169984B2 (en) 2015-11-06 2018-04-27 Data management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/081531 WO2017081737A1 (fr) 2015-11-10 2015-11-10 Système de gestion de données

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/081327 Continuation WO2017077643A1 (fr) 2015-11-06 2015-11-06 Système de gestion de données

Related Child Applications (2)

Application Number Title Priority Date Filing Date
PCT/JP2015/081327 Continuation WO2017077643A1 (fr) 2015-11-06 2015-11-06 Système de gestion de données
PCT/JP2016/082855 Continuation WO2017078158A1 (fr) 2015-11-06 2016-11-04 Système de gestion de données

Publications (1)

Publication Number Publication Date
WO2017081737A1 true WO2017081737A1 (fr) 2017-05-18

Family

ID=58694842

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/081531 WO2017081737A1 (fr) 2015-11-06 2015-11-10 Système de gestion de données

Country Status (1)

Country Link
WO (1) WO2017081737A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013164647A (ja) * 2012-02-09 2013-08-22 Nomura Research Institute Ltd 時限データの履歴管理システム
JP2014041501A (ja) * 2012-08-23 2014-03-06 Hitachi Solutions Ltd バッチ処理対象データの高速読込み方法及びバッチ管理システム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013164647A (ja) * 2012-02-09 2013-08-22 Nomura Research Institute Ltd 時限データの履歴管理システム
JP2014041501A (ja) * 2012-08-23 2014-03-06 Hitachi Solutions Ltd バッチ処理対象データの高速読込み方法及びバッチ管理システム

Similar Documents

Publication Publication Date Title
CN107818431B (zh) 一种提供订单轨迹数据的方法和系统
CN107391758B (zh) 数据库切换方法、装置及设备
CN109542980B (zh) 一种区块链的数据处理方法、装置、设备及介质
CN104718533B (zh) 企业设备的硬件故障管理系统、方法及架构
CN107633016B (zh) 数据处理方法及装置和电子设备
US9053112B2 (en) Automated data validation
CN108647357B (zh) 数据查询的方法及装置
CN103034735A (zh) 一种大数据分布式文件导出方法
US20130263222A1 (en) Computer system and security management method
US11169984B2 (en) Data management system
CN112214505A (zh) 数据同步方法、装置、计算机可读存储介质及电子设备
US11816163B2 (en) Systems and methods for improved transactional mainframes
WO2019019701A1 (fr) Procédé de traitement pour le recyclage de factures vierges, support de stockage et serveur
US20150088958A1 (en) Information Processing System and Distributed Processing Method
CN108959548B (zh) 业务请求的处理方法及装置
US20140046857A1 (en) System, Method, and Software for Enterprise-Wide Complaint Aggregation
CN105389378A (zh) 一种分离式数据整合系统
WO2017081737A1 (fr) Système de gestion de données
JP2017219958A (ja) 資産管理装置、資産管理方法、資産管理プログラム
JP2010134556A (ja) 障害解決システム、障害解決方法、障害解決プログラム
US11582345B2 (en) Context data management interface for contact center
US10691689B2 (en) Automatic API façade generation in dynamic multi-tenant environments
JP2006350411A (ja) 分散データベースリカバリ方法及び同リカバリシステム及び同リカバリプログラム
JP2013122660A (ja) Ｗｅｂアプリケーションシステム及びそのデータ処理方法
US10353902B2 (en) Non-transitory computer-readable recording medium, retrieval support device, and retrieval support method

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: 15908261

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: JP

122 Ep: pct application non-entry in european phase

Ref document number: 15908261

Country of ref document: EP

Kind code of ref document: A1