CN105335401A - Data warehouse index management method, apparatus and system - Google Patents
Data warehouse index management method, apparatus and system Download PDFInfo
- Publication number
- CN105335401A CN105335401A CN201410351744.8A CN201410351744A CN105335401A CN 105335401 A CN105335401 A CN 105335401A CN 201410351744 A CN201410351744 A CN 201410351744A CN 105335401 A CN105335401 A CN 105335401A
- Authority
- CN
- China
- Prior art keywords
- index
- pond
- interface
- operation system
- middle layer
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data warehouse index management method, apparatus and system. The data warehouse index management method comprises: receiving an index output by a data mart through a first interface, wherein the first interface is a unified interface between the data mart and an intermediate layer, and the intermediate layer is a preset interface layer positioned between the data mart and a business system; storing the index in a corresponding index pool; and outputting the index to the corresponding business system through a second interface, wherein the second interface is a unified interface between the intermediate layer and the business system. The method can solve the problem caused by table-level management in a conventional mode, so that the problems of non-unified size, repeated development and difficult management are avoided.
Description
Technical field
The application relates to technical field of data processing, particularly relates to a kind of data warehouse INDEX MANAGEMENT method and apparatus and system.
Background technology
Data warehouse (DataWarehouse, DW) is the data acquisition of a subject-oriented, the change of integrated, metastable, reflecting history, for supporting management decision.Table is the important component part of data warehouse, and a table record is made up of key word (key), tolerance and attribute data.
Data warehouse output-index is generally from multiple Data Mart output, and each Data Mart is according to respective business side demand processing index.Such as loan balance, risk fairground and operation fairground all develop this index and output to business intelligence (BusinessIntelligence, BI) form carry out displayings confession business side check.
Traditional data warehouse is all show as granularity development index, and INDEX MANAGEMENT is also to show grading line pipe reason.But because index is dispersed in the difference table in different pieces of information fairground, between different pieces of information fairground, index of the same name exists bore inconsistence problems, even if also bore inconsistence problems may be there is in the index of the same name between same Data Mart difference table; There is overlapping development between fairground in different pieces of information, waste resource problem; Index is difficult to the problems such as management.
Summary of the invention
The application is intended to solve one of technical matters in correlation technique at least to a certain extent.
For this reason, an object of the application is to propose a kind of data warehouse INDEX MANAGEMENT method, and the method can solve traditional approach and manage to show grading line pipe the problem caused, thus avoids bore inconsistent, overlapping development and unmanageable problem.
Another object of the application is to propose a kind of data warehouse INDEX MANAGEMENT device.
Another object of the application is to propose a kind of data warehouse.
For achieving the above object, the data warehouse INDEX MANAGEMENT method that the application's first aspect embodiment proposes, comprise: receive the index that Data Mart is exported by first interface, described first interface is the unified interface between Data Mart and middle layer, and described middle layer is the default interface layer between Data Mart and operation system; Described index is kept in corresponding index pond; By the second interface, described index is exported to corresponding operation system, described second interface is the unified interface between described middle layer and described operation system.
The data warehouse INDEX MANAGEMENT method that the application's first aspect embodiment proposes, by arranging middle layer, there is unified interface in middle layer and Data Mart, also there is unified interface in middle layer and operation system, the index that Data Mart generates is kept in the index pond in middle layer, the unified management to index can be realized, because middle layer and each Data Mart and each operation system exist unified interface, the problem that bore is inconsistent can be avoided, and, overlapping development can be avoided due to unified management and be difficult to problem of management, thus solve to show grading row index management Problems existing.
For achieving the above object, the data warehouse INDEX MANAGEMENT device that the application's second aspect embodiment proposes, comprise: receiver module, for receiving the index that Data Mart is exported by first interface, described first interface is the unified interface between Data Mart and middle layer, and described middle layer is the default interface layer between Data Mart and operation system; Preserve module, for described index being kept in corresponding index pond; Sending module, for described index being exported to corresponding operation system by the second interface, described second interface is the unified interface between described middle layer and described operation system.
The data warehouse INDEX MANAGEMENT device that the application's second aspect embodiment proposes, by arranging middle layer, there is unified interface in middle layer and Data Mart, also there is unified interface in middle layer and operation system, the index that Data Mart generates is kept in the index pond in middle layer, the unified management to index can be realized, because middle layer and each Data Mart and each operation system exist unified interface, the problem that bore is inconsistent can be avoided, and, overlapping development can be avoided due to unified management and be difficult to problem of management, thus solve to show grading row index management Problems existing.
For achieving the above object, the data warehouse that the application's third aspect embodiment proposes, comprising: the device described in second aspect, and, Data Mart and operation system; Described device between described Data Mart and described operation system, for carrying out unified management to index.
The data warehouse that the application's third aspect embodiment proposes, by arranging middle layer, there is unified interface in middle layer and Data Mart, also there is unified interface in middle layer and operation system, the index that Data Mart generates is kept in the index pond in middle layer, the unified management to index can be realized, because middle layer and each Data Mart and each operation system exist unified interface, the problem that bore is inconsistent can be avoided, and, overlapping development can be avoided due to unified management and be difficult to problem of management, thus solve to show grading row index management Problems existing.
The aspect that the application adds and advantage will part provide in the following description, and part will become obvious from the following description, or be recognized by the practice of the application.
Accompanying drawing explanation
The application above-mentioned and/or additional aspect and advantage will become obvious and easy understand from the following description of the accompanying drawings of embodiments, wherein:
Fig. 1 is the schematic flow sheet of the data warehouse INDEX MANAGEMENT method that the application one embodiment proposes;
Fig. 2 is the schematic flow sheet of the data warehouse INDEX MANAGEMENT method that another embodiment of the application proposes;
Fig. 3 is the system architecture schematic diagram that Fig. 2 is corresponding;
Fig. 4 is the structural representation of the data warehouse INDEX MANAGEMENT device that another embodiment of the application proposes;
Fig. 5 is the structural representation of the data warehouse INDEX MANAGEMENT device that another embodiment of the application proposes;
Fig. 6 is the structural representation of the data warehouse that another embodiment of the application proposes.
Embodiment
Be described below in detail the embodiment of the application, the example of described embodiment is shown in the drawings, and wherein same or similar label represents same or similar element or has element that is identical or similar functions from start to finish.Being exemplary below by the embodiment be described with reference to the drawings, only for explaining the application, and the restriction to the application can not being interpreted as.On the contrary, the embodiment of the application comprise fall into attached claims spirit and intension within the scope of all changes, amendment and equivalent.
Fig. 1 is the schematic flow sheet of the data warehouse INDEX MANAGEMENT method that the application one embodiment proposes, and the method comprises:
S11: receive the index that Data Mart is exported by first interface, described first interface is the unified interface between Data Mart and middle layer, and described middle layer is the default interface layer between Data Mart and operation system.
Wherein, the present embodiment can create a middle layer between existing Data Mart and operation system, and this middle layer is carried out unified management to the index that each Data Mart externally exports or is called unified maintenance.
Interface between middle layer and Data Mart can be called first interface, and the index that different Data Marts exports all exports to middle layer by this unified first interface.
S12: described index is kept in corresponding index pond.
Wherein, can setting target pond in middle layer, index pond comprises public index pond and operational indicator pond, public index pond (publice) is one, the number of the type of service that number and the operation system in operational indicator pond comprise is identical, and mutually corresponding, such as, comprise reporting system and risk system in operation system, then the operational indicator pond arranged in the intermediate layer comprises report form index pond and risk indicator pond.
Described middle layer comprises index pond, and described index pond comprises public index pond and operational indicator pond, and described public index pond is one, and the number in described operational indicator pond is identical with the number of the class of service that described operation system comprises.
There is not index of the same name in same operational indicator pond, comprise or do not comprise index of the same name in different business index pond, there is not index of the same name in public index pond and each operational indicator pond.
Different pieces of information fairground can generate the index needed for corresponding service, and such as, form fairground can index needed for generating report forms system, and risk fairground can generate the index needed for risk system.
After Data Mart generates index, index can be saved in the index pond of corresponding business, such as, the index that form fairground generates is kept in report form index pond, and the index that risk fairground generates is kept in risk indicator pond.
S13: by the second interface, described index is exported to corresponding operation system, described second interface is the unified interface between described middle layer and described operation system.
Wherein, index in different index pond can export to corresponding operation system by the second unified interface, such as, reporting system can obtain index by the second interface from report form index pond, and risk system can obtain index by the second interface from risk indicator pond.
In addition, different business systems can also obtain index from public index pond, and such as, reporting system can obtain index from public index pond, and risk system also can obtain index from public index pond.
The present embodiment is by arranging middle layer, there is unified interface in middle layer and Data Mart, also there is unified interface in middle layer and operation system, the index that Data Mart generates is kept in the index pond in middle layer, the unified management to index can be realized, because middle layer and each Data Mart and each operation system exist unified interface, the problem that bore is inconsistent can be avoided, and, overlapping development can be avoided due to unified management and be difficult to problem of management, thus solving to show grading row index management Problems existing.
Fig. 2 is the schematic flow sheet of the data warehouse INDEX MANAGEMENT method that another embodiment of the application proposes, and Fig. 3 is the system architecture schematic diagram that Fig. 2 is corresponding.
See Fig. 3, the system of the present embodiment comprises Data Mart 31, middle layer 32 and operation system 33.Data Mart 31 can comprise risk fairground, credit fairground, operation fairground etc.Middle layer 32 can be called DW index interface layer, and middle layer 32 comprises public index pond, report form index pond, risk indicator pond etc., also comprises converter, derivatization device, screening washer and tracker.Operation system 33 comprises reporting system and risk system etc.
See Fig. 2, the method comprises:
S21: Data Mart processes data source, obtains corresponding index.
Such as, risk fairground processes data source, obtains this index of loan balance.
S22: index is exported to middle layer by first interface by Data Mart.
Wherein, first interface can adopt java or .net to realize.
Respective index all can be exported to middle layer by unified first interface by different pieces of information fairground.
S23: the converter in middle layer, according to the preset format in described index pond, is reconstructed the index received, and the index after reconstruct is kept in corresponding index pond.
Wherein, Data Mart can adopt table mode to export when output-index, and such as, risk fairground generates a table, and this table comprises multiple index, and afterwards, this table can be exported to middle layer by risk fairground.
See Fig. 3, what middle layer was arranged is index pond, and each index pond comprises following index: index coding (code), pond coding (code), index English name, index Chinese name, dimension, computation rule, data warehouse source is shown, status attribute, founder, amendment people.
Because the form in the index pond that middle layer is arranged is different from the tableau format that Data Mart exports, therefore, converter can be reconstructed the table received, with the form in applicable index pond.
After converter is changed the index received, index can be kept in corresponding index pond, such as, the index that risk fairground exports be kept in risk indicator pond.
In order to ensure that bore is unified and avoid overlapping development, each index pond can meet: do not comprise index of the same name in same operational indicator pond, and different business index pond can comprise index of the same name, and in any operational indicator pond, index is not of the same name with index in public index pond.
Index pond is a kind of structural design, can adopt oracle, and the traditional databases such as mysql or distributed data base realize.
S24: the derivatization device in middle layer derives according to existing index in described index pond the index made new advances.
Such as, in index pond, existing index comprises a day loan balance, and so derivatization device can derive a moon loan balance according to day loan balance.
In addition, the index derived can be kept in the index pond belonging to the index of source, such as, day loan balance be arranged in operation indicator pond, so derive according to day loan balance the moon loan balance obtained and also can exist in operation indicator pond.
S25: after the index in index pond is recombinated according to the form of operation system demand by the screening washer in middle layer, exports to corresponding operation system.
Such as, risk system needs loan balance index and index of exceeding the time limit, then screening washer can take out loan balance index and index of exceeding the time limit from risk indicator pond, and exports to risk system after recombinating according to the form that risk system needs.
Wherein, operation system can use the index in public index pond and corresponding operational indicator pond, and such as, reporting system can use the index in public index pond and report form index pond, and risk system can use the index in public index pond and risk indicator pond.
S26: the tracker in middle layer is followed the tracks of the generation of the index in described index pond, use and alteration.
Such as, middle layer from Data Mart, receive a new index and after being saved in index pond, tracker can record this new index, or derivatization device derives the index made new advances according to existing index after, tracker also can record this new index.Or,
After operation system uses an index, tracker also can record the index of this use.Or,
When the index in operational indicator pond is placed into after in public index pond, tracker also can record this change, such as, when risk personnel find that certain index exists inside operation indicator pond, and demand bore is consistent with operation indicator pond, this index in operation indicator pond so can be applied for move to public index pond.
In addition, tracker can also carry out reach the standard grade life cycle management on monitoring, line, index of index and to stop using lower wire management control etc., concrete, can be used temperature according to index metadata by the frequency monitoring index used; The data such as storage space, computer memory can be taken by index view monitor control index data and realize health degree monitoring; Can by reach the standard grade access and the control of stopping using of rolling off the production line of index metadata interface control index.
The present embodiment is by arranging middle layer and index pond, the management of service index pond substitutes traditional table level INDEX MANAGEMENT, owing to there is unified INDEX MANAGEMENT platform, can avoid between each Data Mart or bore disunity problem in same Data Mart between different table, the interface bore realizing index transmission is consistent; Be kept in index pond because index is unified, the overlapping development and problem of resource waste that each Data Mart can be avoided to develop respectively cause; By arranging the middle layer to index unified management, unified management and tracking can be carried out to index life cycle, making business side can check indication information by visual system.
Fig. 4 is the structural representation of the data warehouse INDEX MANAGEMENT device that another embodiment of the application proposes, and this device 40 comprises receiver module 41, preserves module 42 and sending module 43.
The index that receiver module 41 is exported by first interface for receiving Data Mart, described first interface is the unified interface between Data Mart and middle layer, and described middle layer is the default interface layer between Data Mart and operation system;
Wherein, the present embodiment can create a middle layer between existing Data Mart and operation system, and this middle layer is carried out unified management to the index that each Data Mart externally exports or is called unified maintenance.
Interface between middle layer and Data Mart can be called first interface, and the index that different Data Marts exports all exports to middle layer by this unified first interface.
Preserve module 42 for described index being kept in corresponding index pond;
Wherein, can setting target pond in middle layer, index pond comprises public index pond and operational indicator pond, public index pond (publice) is one, the number of the type of service that number and the operation system in operational indicator pond comprise is identical, and mutually corresponding, such as, comprise reporting system and risk system in operation system, then the operational indicator pond arranged in the intermediate layer comprises report form index pond and risk indicator pond.
Described middle layer comprises index pond, and described index pond comprises public index pond and operational indicator pond, and described public index pond is one, and the number in described operational indicator pond is identical with the number of the class of service that described operation system comprises.
There is not index of the same name in same operational indicator pond, comprise or do not comprise index of the same name in different business index pond, there is not index of the same name in public index pond and each operational indicator pond.
Different pieces of information fairground can generate the index needed for corresponding service, and such as, form fairground can index needed for generating report forms system, and risk fairground can generate the index needed for risk system.
After Data Mart generates index, index can be saved in the index pond of corresponding business, such as, the index that form fairground generates is kept in report form index pond, and the index that risk fairground generates is kept in risk indicator pond.
Sending module 43 is for exporting to corresponding operation system by the second interface by described index, and described second interface is the unified interface between described middle layer and described operation system.
Wherein, index in different index pond can export to corresponding operation system by the second unified interface, such as, reporting system can obtain index by the second interface from report form index pond, and risk system can obtain index by the second interface from risk indicator pond.
In addition, different business systems can also obtain index from public index pond, and such as, reporting system can obtain index from public index pond, and risk system also can obtain index from public index pond.
In an embodiment, described middle layer comprises index pond, and described index pond comprises public index pond and operational indicator pond, and described public index pond is one, and the number in described operational indicator pond is identical with the number of the class of service that described operation system comprises.
In an embodiment, there is not index of the same name in same operational indicator pond, comprise or do not comprise index of the same name in different business index pond, there is not index of the same name in public index pond and each operational indicator pond.
In an embodiment, described index pond comprises following index:
Index is encoded, and encode in pond, index English name, index Chinese name, dimension, computation rule, and data warehouse source is shown, status attribute, founder, amendment people.
This preservation module can the index pond of concrete corresponding said method embodiment.
See Fig. 5, this device 40 also comprises: converter 44, for the preset format according to described index pond, is reconstructed described index, the index after reconstruct to be kept in corresponding index pond.
Wherein, Data Mart can adopt table mode to export when output-index, and such as, risk fairground generates a table, and this table comprises multiple index, and afterwards, this table can be exported to middle layer by risk fairground.
See Fig. 3, what middle layer was arranged is index pond, and each index pond comprises following index: index coding (code), pond coding (code), index English name, index Chinese name, dimension, computation rule, data warehouse source is shown, status attribute, founder, amendment people.
Because the form in the index pond that middle layer is arranged is different from the tableau format that Data Mart exports, therefore, converter can be reconstructed the table received, with the form in applicable index pond.
After converter is changed the index received, index can be kept in corresponding index pond, such as, the index that risk fairground exports be kept in risk indicator pond.
In order to ensure that bore is unified and avoid overlapping development, each index pond can meet: do not comprise index of the same name in same operational indicator pond, and different business index pond can comprise index of the same name, and in any operational indicator pond, index is not of the same name with index in public index pond.
Index pond is a kind of structural design, can adopt oracle, and the traditional databases such as mysql or distributed data base realize.
See Fig. 5, this device 40 also comprises: screening washer 45, after described index being recombinated according to the form of described operation system demand, exports to corresponding operation system.
Such as, risk system needs loan balance index and index of exceeding the time limit, then screening washer can take out loan balance index and index of exceeding the time limit from risk indicator pond, and exports to risk system after recombinating according to the form that risk system needs.
Wherein, operation system can use the index in public index pond and corresponding operational indicator pond, and such as, reporting system can use the index in public index pond and report form index pond, and risk system can use the index in public index pond and risk indicator pond.
See Fig. 5, this device 40 also comprises: derivatization device 46, for deriving according to existing index in described index pond the index made new advances.
Such as, in index pond, existing index comprises a day loan balance, and so derivatization device can derive a moon loan balance according to day loan balance.
In addition, the index derived can be kept in the index pond belonging to the index of source, such as, day loan balance be arranged in operation indicator pond, so derive according to day loan balance the moon loan balance obtained and also can exist in operation indicator pond.
See Fig. 5, this device 40 also comprises: tracker 47, follows the tracks of for the generation to the index in described index pond, use and alteration.
Such as, middle layer from Data Mart, receive a new index and after being saved in index pond, tracker can record this new index, or derivatization device derives the index made new advances according to existing index after, tracker also can record this new index.Or,
After operation system uses an index, tracker also can record the index of this use.Or,
When the index in operational indicator pond is placed into after in public index pond, tracker also can record this change, such as, when risk personnel find that certain index exists inside operation indicator pond, and demand bore is consistent with operation indicator pond, this index in operation indicator pond so can be applied for move to public index pond.
In addition, tracker can also carry out reach the standard grade life cycle management on monitoring, line, index of index and to stop using lower wire management control etc., concrete, can be used temperature according to index metadata by the frequency monitoring index used; The data such as storage space, computer memory can be taken by index view monitor control index data and realize health degree monitoring; Can by reach the standard grade access and the control of stopping using of rolling off the production line of index metadata interface control index.
The present embodiment is by arranging middle layer and index pond, the management of service index pond substitutes traditional table level INDEX MANAGEMENT, owing to there is unified INDEX MANAGEMENT platform, can avoid between each Data Mart or bore disunity problem in same Data Mart between different table, the interface bore realizing index transmission is consistent; Be kept in index pond because index is unified, the overlapping development and problem of resource waste that each Data Mart can be avoided to develop respectively cause; By arranging the middle layer to index unified management, unified management and tracking can be carried out to index life cycle, making business side can check indication information by visual system.
Fig. 6 is the structural representation of the data warehouse that another embodiment of the application proposes, this system 60 comprises Data Mart 61, middle layer 62 and operation system 63, middle layer 62 between Data Mart 61 and operation system 63, for carrying out unified management to index.The concrete composition in middle layer 62 can see Fig. 4 or embodiment illustrated in fig. 5.
The present embodiment is by arranging middle layer, there is unified interface in middle layer and Data Mart, also there is unified interface in middle layer and operation system, the index that Data Mart generates is kept in the index pond in middle layer, the unified management to index can be realized, because middle layer and each Data Mart and each operation system exist unified interface, the problem that bore is inconsistent can be avoided, and, overlapping development can be avoided due to unified management and be difficult to problem of management, thus solving to show grading row index management Problems existing.
It should be noted that, in the description of the application, term " first ", " second " etc. only for describing object, and can not be interpreted as instruction or hint relative importance.In addition, in the description of the application, except as otherwise noted, the implication of " multiple " is two or more.
Describe and can be understood in process flow diagram or in this any process otherwise described or method, represent and comprise one or more for realizing the module of the code of the executable instruction of the step of specific logical function or process, fragment or part, and the scope of the preferred implementation of the application comprises other realization, wherein can not according to order that is shown or that discuss, comprise according to involved function by the mode while of basic or by contrary order, carry out n-back test, this should understand by the embodiment person of ordinary skill in the field of the application.
Should be appreciated that each several part of the application can realize with hardware, software, firmware or their combination.In the above-described embodiment, multiple step or method can with to store in memory and the software performed by suitable instruction execution system or firmware realize.Such as, if realized with hardware, the same in another embodiment, can realize by any one in following technology well known in the art or their combination: the discrete logic with the logic gates for realizing logic function to data-signal, there is the special IC of suitable combinational logic gate circuit, programmable gate array (PGA), field programmable gate array (FPGA) etc.
Those skilled in the art are appreciated that realizing all or part of step that above-described embodiment method carries is that the hardware that can carry out instruction relevant by program completes, described program can be stored in a kind of computer-readable recording medium, this program perform time, step comprising embodiment of the method one or a combination set of.
In addition, each functional unit in each embodiment of the application can be integrated in a processing module, also can be that the independent physics of unit exists, also can be integrated in a module by two or more unit.Above-mentioned integrated module both can adopt the form of hardware to realize, and the form of software function module also can be adopted to realize.If described integrated module using the form of software function module realize and as independently production marketing or use time, also can be stored in a computer read/write memory medium.
The above-mentioned storage medium mentioned can be ROM (read-only memory), disk or CD etc.
In the description of this instructions, at least one embodiment that specific features, structure, material or feature that the description of reference term " embodiment ", " some embodiments ", " example ", " concrete example " or " some examples " etc. means to describe in conjunction with this embodiment or example are contained in the application or example.In this manual, identical embodiment or example are not necessarily referred to the schematic representation of above-mentioned term.And the specific features of description, structure, material or feature can combine in an appropriate manner in any one or more embodiment or example.
Although illustrate and described the embodiment of the application above, be understandable that, above-described embodiment is exemplary, can not be interpreted as the restriction to the application, and those of ordinary skill in the art can change above-described embodiment, revises, replace and modification in the scope of the application.
Claims (17)
1. a data warehouse INDEX MANAGEMENT method, is characterized in that, comprising:
Receive the index that Data Mart is exported by first interface, described first interface is the unified interface between Data Mart and middle layer, and described middle layer is the default interface layer between Data Mart and operation system;
Described index is kept in corresponding index pond;
By the second interface, described index is exported to corresponding operation system, described second interface is the unified interface between described middle layer and described operation system.
2. method according to claim 1, it is characterized in that, described middle layer comprises index pond, and described index pond comprises public index pond and operational indicator pond, described public index pond is one, and the number in described operational indicator pond is identical with the number of the class of service that described operation system comprises.
3. method according to claim 2, is characterized in that, there is not index of the same name in same operational indicator pond, comprises or do not comprise index of the same name in different business index pond, and public index pond and each operational indicator pond do not exist index of the same name.
4. method according to claim 2, is characterized in that, described index pond comprises following index:
Index is encoded, and encode in pond, index English name, index Chinese name, dimension, computation rule, and data warehouse source is shown, status attribute, founder, amendment people.
5. the method according to any one of Claims 1-4, is characterized in that, describedly described index is kept in corresponding index pond, comprising:
According to the preset format in described index pond, described index is reconstructed, the index after reconstruct is kept in corresponding index pond.
6. the method according to any one of Claims 1-4, is characterized in that, the described operation system described index being exported to correspondence, comprising:
After described index being recombinated according to the form of described operation system demand, export to corresponding operation system.
7. the method according to any one of Claims 1-4, is characterized in that, also comprises:
The index made new advances is derived according to existing index in described index pond.
8. the method according to any one of Claims 1-4, is characterized in that, also comprises:
The generation of the index in described index pond, use and alteration are followed the tracks of.
9. a data warehouse INDEX MANAGEMENT device, is characterized in that, comprising:
Receiver module, for receiving the index that Data Mart is exported by first interface, described first interface is the unified interface between Data Mart and middle layer, and described middle layer is the default interface layer between Data Mart and operation system;
Preserve module, for described index being kept in corresponding index pond;
Sending module, for described index being exported to corresponding operation system by the second interface, described second interface is the unified interface between described middle layer and described operation system.
10. device according to claim 9, it is characterized in that, described middle layer comprises index pond, and described index pond comprises public index pond and operational indicator pond, described public index pond is one, and the number in described operational indicator pond is identical with the number of the class of service that described operation system comprises.
11. devices according to claim 10, is characterized in that, there is not index of the same name in same operational indicator pond, comprise or do not comprise index of the same name in different business index pond, and public index pond and each operational indicator pond do not exist index of the same name.
12. devices according to claim 10, is characterized in that, described index pond comprises following index:
Index is encoded, and encode in pond, index English name, index Chinese name, dimension, computation rule, and data warehouse source is shown, status attribute, founder, amendment people.
13. devices according to any one of claim 9 to 12, is characterized in that, also comprise:
Converter, for the preset format according to described index pond, is reconstructed described index, the index after reconstruct to be kept in corresponding index pond.
14. devices according to any one of claim 9 to 12, is characterized in that, also comprise:
Screening washer, after described index being recombinated according to the form of described operation system demand, exports to corresponding operation system.
15. devices according to any one of claim 9 to 12, is characterized in that, also comprise:
Derivatization device, for deriving according to existing index in described index pond the index made new advances.
16. devices according to any one of claim 9 to 12, is characterized in that, also comprise:
Tracker, follows the tracks of for the generation to the index in described index pond, use and alteration.
17. 1 kinds of data warehouses, is characterized in that, comprising:
Device as described in any one of claim 9 to 16, and, Data Mart and operation system;
Described device between described Data Mart and described operation system, for carrying out unified management to index.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410351744.8A CN105335401B (en) | 2014-07-22 | 2014-07-22 | Data warehouse INDEX MANAGEMENT method and apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410351744.8A CN105335401B (en) | 2014-07-22 | 2014-07-22 | Data warehouse INDEX MANAGEMENT method and apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105335401A true CN105335401A (en) | 2016-02-17 |
| CN105335401B CN105335401B (en) | 2019-02-26 |
Family
ID=55285938
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410351744.8A Active CN105335401B (en) | 2014-07-22 | 2014-07-22 | Data warehouse INDEX MANAGEMENT method and apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105335401B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105809358A (en) * | 2016-03-16 | 2016-07-27 | 浪潮通信信息***有限公司 | Network management performance report demand support modeling method based on data driving |
| CN107346321A (en) * | 2016-05-06 | 2017-11-14 | 阿里巴巴集团控股有限公司 | Data warehouse management method and device |
| CN107679096A (en) * | 2017-09-08 | 2018-02-09 | 北京京东尚科信息技术有限公司 | The shared method and apparatus of index between Data Mart |
| CN110941601A (en) * | 2019-11-12 | 2020-03-31 | 北京三快在线科技有限公司 | Method and device for determining standard caliber of index, electronic equipment and storage medium |
| CN111400356A (en) * | 2020-06-04 | 2020-07-10 | 浙江口碑网络技术有限公司 | Data query method, device and equipment |
| CN112465364A (en) * | 2020-12-03 | 2021-03-09 | 合肥天源迪科信息技术有限公司 | Management system for index library |
| CN113760947A (en) * | 2020-12-24 | 2021-12-07 | 北京京东尚科信息技术有限公司 | Data center, data processing method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706911A (en) * | 2009-11-23 | 2010-05-12 | 浪潮集团山东通用软件有限公司 | Method for implementing service-oriented index model in business intelligence system |
| WO2010139167A1 (en) * | 2009-06-05 | 2010-12-09 | 深圳市脑库计算机***有限公司 | Expert support application system platform for government affair and business affair decision-making and its construction method |
| CN101986333A (en) * | 2010-12-01 | 2011-03-16 | 福州维胜信息技术有限公司 | Auxiliary decision supporting system of hospital |
| CN102497435A (en) * | 2011-12-16 | 2012-06-13 | 海南杰福瑞网络科技有限公司 | Data distributing method and device of data service |
-
2014
- 2014-07-22 CN CN201410351744.8A patent/CN105335401B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010139167A1 (en) * | 2009-06-05 | 2010-12-09 | 深圳市脑库计算机***有限公司 | Expert support application system platform for government affair and business affair decision-making and its construction method |
| CN101706911A (en) * | 2009-11-23 | 2010-05-12 | 浪潮集团山东通用软件有限公司 | Method for implementing service-oriented index model in business intelligence system |
| CN101986333A (en) * | 2010-12-01 | 2011-03-16 | 福州维胜信息技术有限公司 | Auxiliary decision supporting system of hospital |
| CN102497435A (en) * | 2011-12-16 | 2012-06-13 | 海南杰福瑞网络科技有限公司 | Data distributing method and device of data service |
Non-Patent Citations (6)
| Title |
|---|
| 冯吉: ""江苏电信数据仓库软件的设计与实现"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 初莹莹: ""基于数据仓库实现对外部监管的支撑探析"", 《中国金融电脑》 * |
| 宋培钟等: ""基于数据仓库的银行个人信贷***的分析与设计"", 《金融理论与实践》 * |
| 王寿根等: "《上海企业信息化论坛上海市计算机用户协会2002年年会论文集》", 31 October 2002, 中国计量出版社 * |
| 甘绍宁: "《专利文献研究 2012》", 31 July 2012, 知识产权出版社 * |
| 陈乃醒等: "《中国中小企业发展报告 2006-2007》", 30 April 2007, 中国经济出版社 * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105809358A (en) * | 2016-03-16 | 2016-07-27 | 浪潮通信信息***有限公司 | Network management performance report demand support modeling method based on data driving |
| CN107346321A (en) * | 2016-05-06 | 2017-11-14 | 阿里巴巴集团控股有限公司 | Data warehouse management method and device |
| CN107679096A (en) * | 2017-09-08 | 2018-02-09 | 北京京东尚科信息技术有限公司 | The shared method and apparatus of index between Data Mart |
| CN107679096B (en) * | 2017-09-08 | 2020-06-05 | 北京京东尚科信息技术有限公司 | Method and device for sharing indexes among data marts |
| CN110941601A (en) * | 2019-11-12 | 2020-03-31 | 北京三快在线科技有限公司 | Method and device for determining standard caliber of index, electronic equipment and storage medium |
| CN110941601B (en) * | 2019-11-12 | 2023-05-30 | 北京三快在线科技有限公司 | Method and device for determining standard caliber of index, electronic equipment and storage medium |
| CN111400356A (en) * | 2020-06-04 | 2020-07-10 | 浙江口碑网络技术有限公司 | Data query method, device and equipment |
| CN112465364A (en) * | 2020-12-03 | 2021-03-09 | 合肥天源迪科信息技术有限公司 | Management system for index library |
| CN112465364B (en) * | 2020-12-03 | 2024-03-19 | 合肥天源迪科信息技术有限公司 | Management system for index library |
| CN113760947A (en) * | 2020-12-24 | 2021-12-07 | 北京京东尚科信息技术有限公司 | Data center, data processing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105335401B (en) | 2019-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105335401A (en) | Data warehouse index management method, apparatus and system | |
| Nelson et al. | Climate challenges, vulnerabilities, and food security | |
| JP6388655B2 (en) | Generation of multi-column index of relational database by data bit interleaving for selectivity | |
| CN101867494B (en) | Soft hardware performance monitoring method based on monitoring template, and system thereof | |
| EP4211589A1 (en) | Interactive graphical user interfaces for simulated systems | |
| Fadiya et al. | Advancing big data for humanitarian needs | |
| US11947934B2 (en) | Auto-generating interactive workflow user interfaces for simulated systems | |
| US11429497B2 (en) | Predicting and handling of slow disk | |
| US20110029489A1 (en) | Dynamic Information Hierarchies | |
| CN103473672A (en) | System, method and platform for auditing metadata quality of enterprise-level data center | |
| Sandquist | Introduction to system science | |
| US20140229222A1 (en) | Integrated project planning and management application | |
| US20160026708A1 (en) | Selection of data storage settings for an application | |
| CN103257987A (en) | Rule-based distributed log service implementation method | |
| US20100076935A1 (en) | Method, system, and computer for analytical reporting and archiving of data | |
| CN113723822A (en) | Power supply service data management system | |
| CN104123298A (en) | Method and device for analyzing product defects | |
| Ghanta et al. | Ml health: Fitness tracking for production models | |
| Wang et al. | Block storage optimization and parallel data processing and analysis of product big data based on the hadoop platform | |
| CN110347406A (en) | A kind of method and device of the operation data of acquisition applications | |
| Wang et al. | Research and design of RFID data processing model based on complex event processing | |
| CN105279122A (en) | XML-based data exchange system | |
| WO2023052821A1 (en) | Methods and systems for optimizing scattered databases and accessing complex data structures for end-user integrated platforms | |
| Cipriotti et al. | A systematic strategy to analyse individual‐based models reveals pathways of degradation and recovery in Patagonian rangelands | |
| Mucchetti | BigQuery for Data Warehousing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201009 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201009 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right |