Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

M. Feltes

dblp:88/4152 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2001
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
1 paper
Query processing and optimization · 100%

Topics — the 1 heaviest of 1, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Query processing and optimization › query optimization
query tuning
0.012001
Tuning an SQL-Based PDM System in a Worldwide Client/Server Environment · ICDE 2001

Methods — techniques the papers use, named apart from their topics

SQL:1999 advanced features · 0.0
YearPublicationVenuePosition
2001 Tuning an SQL-Based PDM System in a Worldwide Client/Server Environment
abstract
The management of product-related data in a uniform and consistent way is a big challenge for many manufacturing enterprises, especially the large ones, like DaimlerChrysler. So-called product data management (PDM) systems are a promising way to achieve this goal. For various reasons, PDM systems often sit on top of a relational DBMS, using it (more or less) as a simple record manager. User interactions with the PDM systems are translated into a series of SQL queries. This does not cause too much harm when the DBMS and PDM system are located in the same local area network, with high bandwidth and short latency times. The picture may change dramatically, however, if the users are working in geographically distributed environments. Response times may rise by orders of magnitude, e.g. from 1-2 minutes in the local context to 30 minutes and even more in the "inter-continental" context. This paper shows how a more sophisticated utilization of the (advanced) SQL features coming along with SQL:1999 can help to cut down response times significantly.
Erich Müller, Peter Dadam, Jost Enderle, M. Feltes
ICDE4