Zur Kurzanzeige

dc.contributor.authorHerrmann, Kai
dc.contributor.authorVoigt, Hannes
dc.contributor.authorSeyschab, Thorsten
dc.contributor.authorLehner, Wolfgang
dc.contributor.editorMitschang, Bernhard
dc.contributor.editorNicklas, Daniela
dc.contributor.editorLeymann, Frank
dc.contributor.editorSchöning, Harald
dc.contributor.editorHerschel, Melanie
dc.contributor.editorTeubner, Jens
dc.contributor.editorHärder, Theo
dc.contributor.editorKopp, Oliver
dc.contributor.editorWieland, Matthias
dc.date.accessioned2017-06-20T20:24:48Z
dc.date.available2017-06-20T20:24:48Z
dc.date.issued2017
dc.identifier.isbn978-3-88579-659-6
dc.identifier.issn1617-5468
dc.description.abstractMultiple applications, which share one common database, will evolve over time by their very nature. Often, former versions need to stay available, so database developers find themselves maintaining co-existing schema versions of multiple applications in multiple versions—usually with handwritten delta code—which is highly error-prone and explains significant costs in software projects. We showcase I V D , a tool using the richer semantics of a bidirectional database evolution language to generate all the delta code automatically, easily providing co-existing schema versions within one database. I V D automatically decides on an optimized physical database schema serving all schema versions to transparently optimize the performance for the current workload.en
dc.language.isoen
dc.publisherGesellschaft für Informatik, Bonn
dc.relation.ispartofDatenbanksysteme für Business, Technologie und Web (BTW 2017)
dc.relation.ispartofseriesLecture Notes in Informatics (LNI) - Proceedings, Volume P-265
dc.subjectDatabase evolution
dc.subjectDatabase versioning
dc.subjectCo-existing schema versions
dc.titleInVerDa – The Liquid Databaseen
dc.typeText/Conference Paper
mci.reference.pages619-622
mci.conference.sessiontitleDemo Program
mci.conference.locationStuttgart
mci.conference.date6.-10. März 2017


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige