Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Flexible Scheme Evolution in Relational Database Model

Flexible Scheme Evolution in Relational Database Model

Scheduled Pinned Locked Moved IT & Infrastructure
databasebusinessxmlarchitectureperformance
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    kushibhai
    wrote on last edited by
    #1

    Specification In a typical database management system a concept of database schema provides full information about a logical organization of database structures. The principal requirement of logical database consistency states that in every moment of time contents of a database must be consistent with the respective database schema. The queries submitted to a database must be syntactically consistent with a database schema as well. The idea of scheme evolution refers to the changes in a database scheme over a certain period of time. It would be convenient to modify a database schema depending on users' requirements. The conventional query languages, like for instance SQL, does not allow for references to a number of different versions of the same database schema. Unfortunately, the frequent modifications of database schema require restructuring of database contents and modification of user applications. As the result, frequent evolution of a database schema significantly decreases performance of a database system and requires continuous upgrades of user applications. Objectives The objective of this project is to propose architecture for database system where frequent evolution of database scheme has no significant impact on performance of the system and it is transparent to users' applications.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups