EP1428140A2 - Systemes et procedes de collecte, de stockage et d'analyse des statistiques d'une base de donnees - Google Patents

Systemes et procedes de collecte, de stockage et d'analyse des statistiques d'une base de donnees

Info

Publication number
EP1428140A2
EP1428140A2 EP00978450A EP00978450A EP1428140A2 EP 1428140 A2 EP1428140 A2 EP 1428140A2 EP 00978450 A EP00978450 A EP 00978450A EP 00978450 A EP00978450 A EP 00978450A EP 1428140 A2 EP1428140 A2 EP 1428140A2
Authority
EP
European Patent Office
Prior art keywords
database
data
analysis
server
statistics
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.)
Withdrawn
Application number
EP00978450A
Other languages
German (de)
English (en)
Inventor
Brent David Tucker
James Frederick Koopmann
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
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 Individual filed Critical Individual
Publication of EP1428140A2 publication Critical patent/EP1428140A2/fr
Withdrawn legal-status Critical Current

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/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3495—Performance evaluation by tracing or monitoring for systems

Definitions

  • This invention relates generally to the field of database administration and, more specifically, to systems, methods, and applications that provide trending analysis of a database system by monitoring internal statistics and structures as provided by a database vendor or through custom process and data acquisition techniques, as such information spans time.
  • This invention also relates to systems, methods, and applications that use collected information concerning databases to assist with database analysis, including, for example, performance evaluation, reliability analysis, and management of database systems.
  • a database system is a product that resides on one or more computer systems and provides multiple users with access to data.
  • databases are used, methodologies for accessing stored data, optimizing database processes, and storing parameter requirements change. It follows that complex database systems may require extensive management.
  • Managing database systems includes the monitoring of processes and resources in order to detect deterioration in the overall reliability and efficiency of a database system.
  • Parameters that can be monitored within a database include, but are not limited to, CPU utilization, physical storage utilization, memory utilization, network traffic, physical database structures, logical database structures, referential integrity, and parameters and files which are required for reliability.
  • CPU utilization physical storage utilization
  • memory utilization network traffic
  • physical database structures physical database structures
  • logical database structures referential integrity
  • parameters and files which are required for reliability.
  • Trends may be evaluated over any period of time, including hours, days, weeks, or months. By retaining historical data for a relatively long period of time, the trends shown will be more accurate, and may be more useful to a database administrator. By reviewing trend information, insight may be gained into both normal and abnormal behavior of a database system.
  • the many benefits that flow from active monitoring of a database system include, for example, detection of potential or actual problem areas within a database system; location of intermittent problem areas; identification of increased periods of load on the database system; verifying the overall quality and performance of a production system; and alleviation of the time and resource constraints placed on database administration personnel. When errors or degradation of performance trends occur, repairs may begin prior to complete failure of the database environment.
  • Trends-based analysis is powerful due to the predictive nature of such analysis. By reviewing growth patterns, utilization patterns, and performance patterns, one may derive the point at which a database may begin to fail to meet the needs of a process. Once a trend is identified, resources and processes may be modified to alleviate problems associated with the trend.
  • Database servers may be run on many different hardware and operating system platforms. While each of these platforms has unique features, database servers are common across all platforms. By monitoring multiple database servers on non- heterogeneous platforms, and providing a common reporting mechanism, a framework of communication can be established that allows personnel to perform more efficiently.
  • Goals of trends-based analysis of database systems are to reduce expenses, improve performance and availability, to sustain or increase revenue, and to improve the performance of personnel by alleviating their need to continuously monitor the database through manual means.
  • Many difficulties are present in existing approaches. First, manual monitoring processes are error prone. Since a human interface is required to perform multiple steps for data collection, and then analyze resulting data and interpret the results, the analysis and decision making process may not be consistent. An inconsistent method of obtaining results may result in improper decisions being made concerning database administration. This problem is compounded by more than one person attempting the analysis, since past experience invariably skews the interpretive results.
  • this invention is directed to a database system statistic collection, analysis, repository creation, and consistent reporting tool that monitors database systems and produces textual, tabular, and graphical reports describing both Trends-based and static data.
  • the tool utilizes a database system for collection, standard Internet protocols for file transmission, a repository database for warehousing of data, and reporting tools which may be viewed electronically, via a web browser or other display means, or as a paper based report. Additionally, clients receiving the report may use a web browser or other query device or software to drill down through data that is retained on the data warehouse server.
  • the database servers to be monitored may reside in local or remote data centers, and each data center may house one or more database systems.
  • the data center housing the analysis system consists of one or more database servers, one or more application servers, and other peripheral equipment as needed. Multiple data centers may exist. Data can be retained on the database server(s) for a period of time, allowing trends analysis to be more accurate. All incoming files can be written to a permanent storage device as an archival method.
  • the analysis process may consist of one or more programs specifically designed to perform trends-based analysis, object analysis, structure analysis (of database structures), and reliability analysis. Additionally, such processes may summarize data and provide categorization for further reporting.
  • the reporting process queries the analyzed and summarized data warehouse for trend information, potential points of contention within the database, performance problems, and reliability concerns.
  • the resulting data is formatted into a consistent series of reports including, but not limited to, executive summaries, management reports, progress reports, reliability reports, and trends-based proactive recommendations and descriptions of potential problems.
  • the statistics to be collected reside on one or more database systems, with each system storing its own statistics collection individually, or optionally with all collection of information written back to a central collection point. Statistics are collected on some predefined interval, are converted through selected algorithms to a historical record format, and are stored in a database schema designed specifically for the system.
  • Each evaluated database system has a database engine, an underlying operating system, and a designated storage facility for the collection methods. Data collection scripts determine which data to collect, the validity of the data, and ensure that the data is stored correctly.
  • a scheduler provided by the operating system controls the initialization or termination of the collection scripts at the predetermined interval.
  • the host for the database has a clock, which is used for time stamping the historical data to preserve order of entry into the system.
  • Data transport occurs on each computer that hosts a collection process, and sends the collected data back to the analysis environment via the Internet.
  • the protocol used for this transmission will vary within commonly used data transmission protocols.
  • data is received in the analysis environment, it is written to permanent off line storage, for example a CD-ROM, so that the data will be available in the case of disaster recovery, or if a client should need the data again after a retention period has expired.
  • the data is received in the analysis environment and is loaded into a staging area.
  • a conversion process uses the staged data to load the data into the data warehouse.
  • a summarization and analysis process interrogates the data, providing several levels of summarization and performing Trends-based analysis on the data.
  • Data retention is specific to the needs of the owner of the database system being analyzed. All collected data, in both raw and summarized form, are retained within the data warehouse.
  • a remote user of the system may connect to the data warehouse server via the Internet and run other analysis against the data as needed, or retrieve additional reports that are not included in the standard report package.
  • Figure 1 is a flow chart illustrating a process in accordance with the present invention for collecting statistics, analyzing those statistics, and effecting reporting within database systems.
  • Figure 2 is a flow chart illustrating a collection process flow in accordance with the present invention.
  • Figure 3 is a flow chart illustrating a reporting process flow in accordance with the present invention.
  • Figure 4 is an illustration of a database system architecture that may have an application in accordance with the present invention configured thereon.
  • Figures 5(a)-(f) are screen snapshots showing sample reports in accordance with the present invention.
  • Figure 1 is a flow chart illustrating a process in accordance with the present invention for collecting statistics, analyzing those statistics, and effecting reporting within database systems. More specifically, Figure 1 describes an overall process 100 that provides for (1) the collection of data, (2) local storage of that data on a database to be evaluated or a repository database established for evaluation, (3) the transport of that data to a remote server or servers, and (4) the loading, summarization, analysis, trend based analysis, storage, extraction and reporting of that data.
  • the process flow can be entered through software at an evaluation site.
  • the collection mechanism is started as a timed activity on the database server holding a repository. One or more collection mechanisms may be started depending on the number of databases to collect from.
  • the data is extracted from the database and placed into a standard export format.
  • the system performs an integrity check to determine if the extraction was successful.
  • the process flags the error in the repository database and branches execution to item 144, End of Process.
  • the exported data is transferred to a production data center.
  • the system performs an integrity check to determine if the transfer of data was successful.
  • the process flags the error in the repository database and branches execution to item 144, End of Process.
  • the transfer process does succeed, the data from the client database is loaded into a staging area in the DBDoctor database server.
  • the system performs an integrity check to determine if the data load was successful.
  • the process flags the error in the repository database and branches execution to item 144, End of Process.
  • the data from the client database is summarized through the execution of a series of summarization scripts.
  • the system performs an integrity check to determine if the summarization was successful.
  • the process flags the error in the repository database and branches execution to item 144, End of Process.
  • the system performs an integrity check to determine if the analysis was successful.
  • the process flags the error in the repository database and branches execution to item 144, End of Process.
  • reports about the data are generated in multiple formats, including reports at executive, managerial and technical personnel levels, for delivery via email, PDF format, or other delivery mechanism.
  • the system performs an integrity check to determine if the reporting was successful.
  • the process flags the error in the repository database and branches execution to item 144, End of Process.
  • the data warehouse is updated to indicate the completion of execution for the currently processed database system.
  • the end of the process occurs.
  • Figure 2 is a flow chart illustrating a collection process flow in accordance with the present invention. More specifically, Figure 2 describes a process 200 for a Statistic and Structure Collection Process in accordance with the present invention. In general, this process determines the number and types of database environments from which data will be collected, collects the data by processing each database, ensures the validity of the collected data, and transfers the data to the remote evaluation site. [0029] At step 202, the process flow can be entered through software at the evaluation site. At step 204, the collection mechanism is started as a timed activity on the database server holding a repository. One or more collection mechanisms may be started depending on the number of databases from which to collect. The databases to be evaluated are determined and placed into a queue.
  • the next database to be processed on the queue is selected for collection.
  • the system performs an integrity check to determine if the end of queue condition was reached.
  • the process checks to see if the data has been flagged for transfer to the remote analysis data center.
  • the data is extracted from the database repository at the client site, and is transported to the DBDoctor data center specified by the operations staff of the licensing company.
  • the process ends.
  • the system performs an integrity check to determine if the database to be collected is accessible.
  • process control is returned to item 206, 'Get next database on the queue to collect'.
  • variables are set which control the collection process for the database to be collected.
  • the database type and version are determined by the process, and variables describing these values are set for further processing.
  • a queue is created which contains the internal structures to be collected.
  • the next structure to be collected is obtained from the queue defined in item 220.
  • the system performs an integrity check to determine if the end of the collection queue has been reached. If the end of the collection queue has been reached, the process branches execution to item 206, 'Get next database on the queue to collect'.
  • step 2208 if the end of the collection queue has not been reached, structure statistics are collected for the current evaluation database type and version.
  • the system performs an integrity check to determine if a valid collection has been taken.
  • step 232 if collection does not succeed, a collection error flag is stored in the registry, and control branches to item 224, 'Get next structure to collect'.
  • step 234 statistics are updated on the repository database. Execution of the process branches to item 206, 'Get next database on the queue to collect' for further processing.
  • Figure 3 is a flow chart illustrating a reporting process flow in accordance with the present invention. More specifically, Figure 3 describes a reporting process 300 in accordance with the present invention. In general, this process determines the number of databases to report on, loads a queue of those databases, processes the queue, and generates and delivers reports.
  • the process flow can be entered through software at the production data center.
  • the reporting mechanism is started as a timed activity on an application server.
  • the databases to be evaluated are determined and placed into a queue.
  • the next database to be processed on the queue is selected for reporting.
  • the system performs an integrity check to determine if the end of queue condition was reached.
  • the process updates the data warehouse with a completion status.
  • the process terminates.
  • the system performs an integrity check to determine if the data for the current database is available. If the data is unavailable for processing, execution branches to item 316, 'Perform Load'.
  • the load process is invoked for the current database. Execution branches to item 322, 'Perform Summary'. At step 318, get information about the client, client databases, and recipient list for processing from the data warehouse. At step 320, the system performs an integrity check to determine if the summarization for the current database has been run. If the data is not summarized, execution branches to item 322, 'Perform Summary'. At step 324, the trend analysis processes are invoked for the current database. At step 326, management reports are produced for the current database. At step 328, executive reports are produced for the current database. At step 330, detailed data reports are produced for the current database. At step 332, reports are assembled for the current database and prepared for delivery.
  • step 334 data is made available for Internet based queries.
  • the HTML version of the report is generated.
  • the report is stored on the web server.
  • the Adobe PDF version of the report is generated.
  • the PDF report is stored on the mail application server.
  • the data warehouse is interrogated to determine if the customer has a recipient list, which includes HTML reports. If not, execution branches to item 344, 'Does customer want a PDF report?'.
  • an email is dispatched to the customer as an informational message informing them that their report is ready.
  • the data warehouse is interrogated to determine if the customer has a recipient list, which includes PDF reports. If not, execution branches to item 348, 'Exit'.
  • an email is dispatched to the customer with a PDF file attachment for the current database. Process execution branches to item 306, 'Get next database on the queue to report.
  • Figure 4 is an illustration of a database system that may have an application in accordance with the present invention configured thereon. More specifically, Figure 4 describes the architecture and design of the database monitoring system environment. In general, the architecture has two physically separate areas, item 402, 'Client Database Environment', and item 412, 'DBDoctor Production Data Center'. The Client Database Environment will be required for each customer served by this service. The DBDoctor Production Data Center may be replicated as required for scalability.
  • the Client Database Environment 402 consists of one or more of item 406, 'Collection Database Server', and zero or more of item 404, Client Database Server.
  • Item 408 is a temporary file generated during extract processes.
  • the databases 404 to be evaluated are loaded with software that enables them to be evaluated from a remote location.
  • the client may have one or more databases to be evaluated.
  • the database being evaluated may also hold the repository database, depicted by item 406, 'Collection Database Server'.
  • the architecture is flexible and will be designed and installed to the customer specifications.
  • Each database server 406 at the client facility may have one or more databases loaded in order to be evaluated. There is no limit to the umber of databases a customer may have, as demonstrated by items 404 (a), 404(b) and 404(c).
  • the Collection Database Server 406 is loaded with an application in accordance with the present invention and databases components, together referred to as a repository.
  • This repository preferably resides on a server with a database installed and functional.
  • the repository may reside on an existing production database, or may reside on a server dedicated to this task. Additionally, multiple Collection Database Servers 406 may be installed at each customer site.
  • the data transfer component 410 may make use of any of a number of electronic transfer protocols, including File Transfer Protocol, Hyper Text Transfer Protocol, Secure Copy, or Virtual Private Network transmission.
  • This Data Transfer uses push technology to deliver the data, contained in the Extracted Data file illustrated by item 408, to the Data Transfer Server, represented by item 414 at the DBDoctor Production Data Center.
  • the Production Data Center 412 houses the equipment and software required for the analysis, data storage, report generation, and client delivery components required by the service.
  • the data transfer server 414 is a highly reliable component that facilitates the transfer of data from a client site to the Production Data Center 412. This server may be a single component, or may be clustered or placed in another highly available environment as needed. This server supports the receipt of information from multiple transfer protocols.
  • the System Database Servers 416 house the data warehouse component of the service. This data is retained for the number of days deemed necessary for the analysis of data to produce trend-based reports.
  • the Application Servers 418 are multi-function, serving to facilitate the load process, summarization process, analysis and reporting process, and mail delivery processes. As illustrated, one or more application servers are required for operation of the service. Items 418 (a) and 418 (b) are representative of these servers.
  • the Client Reports 420 are one of the end results of the service. They are generated on item 418, 'Application Server', and are then made available to the client for use.
  • the E-Mail report 422 is one of the available versions of the reports generated.
  • the Web server 424 makes available the customer data for further analysis. Functions of the web server include, but are not limited to, drill down reporting of data, enhanced trend analysis, shema and structure review, and archival report storage and delivery. This item, as depicted by item 424, may be a single server or one of many as required for load balancing and reliability.
  • the collection mechanism uses a tabular replication of structures to be collected.
  • This replication of internal structures preferably is fully aware of differences between versions of databases being collected and will modify itself depending on the differences between those versions.
  • the collection tables also have various columns to handle items such as customer information, timestamp data, and runtime logic.
  • the collection mechanism is a collection of tables that are complete replicas of internal database structures. These tables are identical to the collected structures in columns names and data types. In addition to the one to one relationship of column values, customer and timestamp columns may be added. During the collection process a simple select and insert statement may be generated to pull the internal data from the database structures and place that data into the replicated structures. At the time this information is selected, customer data and a timestamp is also placed into the table for each row.
  • the customer data is a mechanism to maintain identity of the data after transport to the warehouse storage facility, and the timestamp is placed into the rows so that an image of how the data changes over time may be obtained, and so that data can be grouped by such means as hours of the day, day of the week, and week of the year. Since there are many different database versions that the collection needs to pull data from, a fully aware environment is utilized that will extract the full data definition of the structures to be collected from the internal database dictionaries of the databases to be collected. Once this definition has been extracted the collection process can dynamically generate the select and insert statements that will be used to populate the replicated structures.
  • Figures 5(a)-(f) are illustrations of reports that may be generated using a database management system in accordance with the present invention.
  • Figure 5(a) is an example of an executive summary report, which includes a list of event categories 510 and event severeties 512.
  • Figure 5(b) provides an illustration of an IT management report that lists events in order of severity, e.g., critical 520, serious 522, warning 524, etc.
  • Figure 5(c) provides an illustration of a detail report that addresses in more detail the events listed in the IT management report, shown in Figure 5(b).
  • Figure 5(d) provides an illustration of an executive summary including a usage chart.
  • Figure 5(e) provides an illustration of a management report including a graphic representation of I/O mount point percentages, and
  • Figure 5(f) provides an illustration of detail report regarding mount points.

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)
  • Computer And Data Communications (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un système et un procédé permettant de rassembler, de stocker, de récupérer et d'analyser des données statistiques d'une base de données. Un agent de collecte installé sur le serveur d'une base de données interroge la base de données à un intervalle défini afin de déterminer l'état de la base de données, et de dériver des statistiques sur la performance, les structures et l'utilisation de la base de données. Ces données statistiques sont stockées dans une base de données de collecte comme données historiques. Périodiquement, les données historiques sont déchargées de la base de données de collecte, transférées via un protocole de transfert à un serveur de dépôt de données, et chargées dans ledit serveur. Un résumé des données et une analyse des tendances sont effectués sur les données, et les résultats stockés dans le dépôt de données en stockage rémanent. Périodiquement, le serveur d'une application interroge le dépôt de données sur la base de données analysée, et génère une série de rapports présentant des données sur les tendances, la fiabilité et la performance de la base de données en formats graphique, textuel et tabulaire.
EP00978450A 1999-11-09 2000-11-09 Systemes et procedes de collecte, de stockage et d'analyse des statistiques d'une base de donnees Withdrawn EP1428140A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US16417099P 1999-11-09 1999-11-09
US164170P 1999-11-09
PCT/US2000/030784 WO2001035256A2 (fr) 1999-11-09 2000-11-09 Systemes et procedes de collecte, de stockage et d'analyse des statistiques d'une base de donnees

Publications (1)

Publication Number Publication Date
EP1428140A2 true EP1428140A2 (fr) 2004-06-16

Family

ID=22593291

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00978450A Withdrawn EP1428140A2 (fr) 1999-11-09 2000-11-09 Systemes et procedes de collecte, de stockage et d'analyse des statistiques d'une base de donnees

Country Status (4)

Country Link
EP (1) EP1428140A2 (fr)
AU (1) AU1591201A (fr)
CA (1) CA2390697A1 (fr)
WO (1) WO2001035256A2 (fr)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7240112B2 (en) 2000-05-26 2007-07-03 Ipass Inc. Service quality monitoring process
DE10308851A1 (de) * 2003-02-27 2004-09-30 Software Engineering Gmbh Echtzeitwartung einer relationalen Datenbank
US7779018B2 (en) 2003-05-15 2010-08-17 Targit A/S Presentation of data using meta-morphing
DK1477909T3 (da) 2003-05-15 2007-05-07 Targit As Fremgangsmåde og brugergrænseflade til at lave en præsentation af data under anvendelse metamorfning
US8468444B2 (en) 2004-03-17 2013-06-18 Targit A/S Hyper related OLAP
EP1591928A1 (fr) * 2004-04-30 2005-11-02 Daktronics, Inc. Système et procédé pour la transmission et le traitement d'information de jeu à travers un réseau longue
DK1659503T3 (da) * 2004-11-17 2010-10-04 Targit As Sporingshistorik til database
US7774295B2 (en) 2004-11-17 2010-08-10 Targit A/S Database track history
DK176532B1 (da) 2006-07-17 2008-07-14 Targit As Fremgangsmåde til integration af dokumenter med OLAP ved brug af sögning, computerlæsbart medium og computer
US8640033B2 (en) 2007-06-29 2014-01-28 Microsoft Corporation Unified user experience using contextual information, data attributes and data models
IL195956A0 (en) 2008-12-15 2009-09-01 Hyperroll Israel Ltd Automatic data store architecture detection
IL197961A0 (en) 2009-04-05 2009-12-24 Guy Shaked Methods for effective processing of time series
US9934255B2 (en) 2013-11-11 2018-04-03 International Business Machines Corporation End of retention processing using a database manager scheduler
CN105069134B (zh) * 2015-08-18 2018-07-27 上海新炬网络信息技术股份有限公司 一种Oracle统计信息自动收集方法
CN108334641B (zh) * 2018-03-21 2020-10-16 上海精数信息科技有限公司 采集用户行为数据的方法、系统、电子设备、存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5701471A (en) * 1995-07-05 1997-12-23 Sun Microsystems, Inc. System and method for testing multiple database management systems
US5819066A (en) * 1996-02-28 1998-10-06 Electronic Data Systems Corporation Application and method for benchmarking a database server
US5852818A (en) * 1996-12-23 1998-12-22 Oracle Corporation Non-recursive method for parameter evaluation within an information management system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0135256A2 *

Also Published As

Publication number Publication date
AU1591201A (en) 2001-06-06
WO2001035256A2 (fr) 2001-05-17
CA2390697A1 (fr) 2001-05-17
WO2001035256A3 (fr) 2004-04-01

Similar Documents

Publication Publication Date Title
US9940373B2 (en) Method and system for implementing an operating system hook in a log analytics system
US7941524B2 (en) System and method for collecting and storing event data from distributed transactional applications
Mayer et al. An approach to extract the architecture of microservice-based software systems
US7526508B2 (en) Self-managing database architecture
US7500150B2 (en) Determining the level of availability of a computing resource
US7418461B2 (en) Schema conformance for database servers
EP2471014B1 (fr) Systèmes et procédés de collecte de données à distance
US6141699A (en) Interactive display system for sequential retrieval and display of a plurality of interrelated data sets
US6321263B1 (en) Client-based application availability
US6070190A (en) Client-based application availability and response monitoring and reporting for distributed computing environments
US6901536B2 (en) Service quality monitoring system and method
US7617201B1 (en) System and method for analyzing statistics in a reporting system
EP1428140A2 (fr) Systemes et procedes de collecte, de stockage et d'analyse des statistiques d'une base de donnees
US9576010B2 (en) Monitoring an application environment
US20100088197A1 (en) Systems and methods for generating remote system inventory capable of differential update reports
WO2007036932A2 (fr) Systeme de gestion de table de donnees et methodes associes
US7779300B2 (en) Server outage data management
US10305738B2 (en) System and method for contextual clustering of granular changes in configuration items
CN107104806A (zh) 话单处理方法、装置及系统
US7457991B1 (en) Method for scanning windows event logs on a cellular multi-processor (CMP) server
Lingrand et al. Analyzing the EGEE production grid workload: application to jobs submission optimization
Carlyle et al. Practical support solutions for a workflow-oriented Cray environment
CN117271183A (zh) 数据库异常作业调度重试策略的获取方法及其装置
Shaila et al. Support automation connectivity system for big data applications
Barshefsky et al. 5ESS® field switch performance capture

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020610

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20050531