Topic
Transaction log
About: Transaction log is a research topic. Over the lifetime, 1651 publications have been published within this topic receiving 41743 citations. The topic is also known as: database log & transaction journal.
Papers published on a yearly basis
Papers
More filters
TL;DR: A failure analysis was conducted, identifying trends among user mistakes, and a summary of findings and a discussion of the implications of these findings were concluded.
Abstract: We analyzed transaction logs containing 51,473 queries posed by 18,113 users of Excite, a major Internet search service. We provide data on: (i) sessions — changes in queries during a session, number of pages viewed, and use of relevance feedback; (ii) queries — the number of search terms, and the use of logic and modifiers; and (iii) terms — their rank/frequency distribution and the most highly used search terms. We then shift the focus of analysis from the query to the user to gain insight to the characteristics of the Web user. With these characteristics as a basis, we then conducted a failure analysis, identifying trends among user mistakes. We conclude with a summary of findings and a discussion of the implications of these findings. # 2000 Elsevier Science Ltd. All rights reserved.
1,414 citations
Patent•
24 Feb 1998
TL;DR: In this paper, a method for collecting, storing, and retrieving data in a database management system is presented, where a transaction file corresponding to the transaction in an outbox of a workgroup user client is copied to an inbox identified to the workgroup client.
Abstract: A method of and system for collecting, storing, and retrieving data in a database management system. The database management system includes a master database server (4), at least one workgroup server (315), and a plurality of workgroup user clients (310). The workgroup server (315) is interposed between the master database server (4) and said workgroup user clients (310). The method creating a transaction in a local database resident on one of the workgroup user clients (310), entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding to the transaction in an outbox of said workgroup user client (310). Next, the transaction file is copied to an inbox identified to the workgroup user client (310) and updating the transaction file into a workgroup database (305) resident on the workgroup server (315). The workgroup database (305) includes a transaction log.
1,313 citations
Patent•
17 Aug 1999
TL;DR: In this paper, the authors present a method for collecting, storing, and retrieving data in a database management system, which includes creating a transaction in a local database resident on a workgroup user client, entering the transaction into a transaction log resident on the work group user client and creating transaction file corresponding to the transaction log in an outbox of the workgroup users client.
Abstract: Method of and apparatus for collecting, storing, and retrieving data in a database management system. The database management system has an enterprise server and at least one workgroup user client. The method includes creating a transaction in a local database resident on said workgroup user client, entering the transaction into a transaction log resident on the workgroup user client, and creating a transaction file corresponding to the transaction log in an outbox of the workgroup user client. The workgroup user client transaction log is read, skipping those transactions which originate at the enterprise server, data files are created corresponding to the entries. The data files corresponding to transactions originating at the workgroup user client are read to an inbox on the enterprise server, thus updating the transactions into an enterprise database on the enterprise server.
1,168 citations
TL;DR: An incremental approach to check the conformance of a process model and an event log is proposed and a Conformance Checker has been implemented within the ProM framework and it has been evaluated using artificial and real-life event logs.
1,111 citations
20 Jun 2005
TL;DR: The ProM framework is introduced and an overview of the plug-ins that have been developed and is flexible with respect to the input and output format, and is also open enough to allow for the easy reuse of code during the implementation of new process mining ideas.
Abstract: Under the umbrella of buzzwords such as “Business Activity Monitoring” (BAM) and “Business Process Intelligence” (BPI) both academic (e.g., EMiT, Little Thumb, InWoLvE, Process Miner, and MinSoN) and commercial tools (e.g., ARIS PPM, HP BPI, and ILOG JViews) have been developed. The goal of these tools is to extract knowledge from event logs (e.g., transaction logs in an ERP system or audit trails in a WFM system), i.e., to do process mining. Unfortunately, tools use different formats for reading/storing log files and present their results in different ways. This makes it difficult to use different tools on the same data set and to compare the mining results. Furthermore, some of these tools implement concepts that can be very useful in the other tools but it is often difficult to combine tools. As a result, researchers working on new process mining techniques are forced to build a mining infrastructure from scratch or test their techniques in an isolated way, disconnected from any practical applications. To overcome these kind of problems, we have developed the ProM framework, i.e., an “pluggable” environment for process mining. The framework is flexible with respect to the input and output format, and is also open enough to allow for the easy reuse of code during the implementation of new process mining ideas. This paper introduces the ProM framework and gives an overview of the plug-ins that have been developed.
958 citations