Flow enhancement between Customer relationship management (CRM) and Data warehouse
Abstract: CRM is routine that integrates ideas of knowledge management, data mining, and data warehousing so as to support an organization's determination-making method to maintain long term relationships with their customers. This exploration is a piece of a long haul study to analyze methodically CRM components that influence plan choices for CRM data warehouses to manufacture a scientific classification of CRM analysis and to decide the effect of those analysis on CRM data warehousing outline decisions. Extract, transform and load (ETL) is the center procedure of data integration and is normally connected with data warehousing. ETL is a key procedure to unite all the data in a standard, homogenous environment. ETL capacities reshape the significant data from the source frameworks into helpful data to be saved in the data warehouse. If source data taken from various sources is not cleanse, not extracted properly, not transformed and integrated in the proper way then our flow from CRM to Data warehouse will decrease. In this paper we presented advance approach by Query Cache which will increase ETL process then our flow enhancement will automatically increase.
For the quick get to the database we utilize the query cache. Query cache will store all record of executed query. Query cache will keep record of recently executed inquiries. The major objective of the query cache is to diminish the reaction time of query. It will expand the mental aptitude of information product house so framework will retain the most recent work it has performed. This memory will be utilized a while later for answer the aftereffect of questions which has been before performed by the clients. The cache will keep up two state valid and invalid state. At the point when any query put together by the client, the cache memory is initially analyzed to check whether asked for query is as of now store in the cache. On the off chance that the query is saved, then check the state is valid or invalid. In the event that state is valid then data can be get to and if state is invalid then data can't be get to be that as it may, If client send a query of supplement, redesign, erase and drop then information will be change in database and condition of related query will be invalid. Presently invalid state data and query can't be access by client. This can spare vital time and enhance Data warehouse execution by not rethinking the inquiries which are now saved in the cache.
Scientific adviser - Valery Ovchinnikov