Jump to content

Database refactoring: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m changed some word and added commas to easy reading and changed to be easy reading text
Line 1: Line 1:
A '''database refactoring''' is a simple change to a [[database schema]] that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix [[software bug|bug]]s or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.
A '''database refactoring''' is a simple change to a [[database schema]] that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix [[software bug|bug]]s or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.


A database refactoring is conceptually more difficult than a [[code refactoring]]; code refactorings only need to maintain behavioral semantics while database refactorings also must maintain informational semantics.
A database refactoring is conceptually more difficult than a code refactoring; code refactorings only need to maintain behavioral semantics, while database refactorings also must maintain informational semantics.


A database schema is typically refactored for one of several reasons:
'''<u>A database schema is typically refactored for one of several reasons:</u>'''

# To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
# To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for [[database normalization]] of an existing production database, typically to "clean up" the design of the database.
* To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
* To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for database normalization of an existing production database, typically to "clean up" the design of the database.
# To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.
* To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.


==Categories of database refactoring==
==Categories of database refactoring==
{{Tone|date=July 2024}}
{{Tone|date=July 2024}}
In 2006, Scott Ambler and Pramod Sadalage described the following categories of database refactoring:
In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>
* Architecture Refactoring
* Architecture Refactoring
::A change which improves the overall manner in which external programs interact with a database.
::A change that improves the overall manner in which external programs interact with a database.
Methods of Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table With View; Introduce Calculation Method; Introduce Index; Introduce Read Only Table; Migrate Method From Database; Migrate Method To Database; Replace Method(s) With View; Replace View With Methods(s); Use Official Data Source.
Methods of the Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table with View; Introduce Calculation Method; Introduce Index; Introduce Read-Only Table; Migrate Method from Database; Migrate Method to Database; Replace Method(s) with View; Replace View with Method(s); Use Official Data Source.
* Structural Refactoring
* Structural Refactoring
::A change to the table structure of your database schema.
::'''<u>A change to the table structure of your database schema.</u>'''
Methods of Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB With Table; Replace Column; Replace One-To-Many With Associative Tables; Replace Surrogate Key With Natural Key; Split Column; Split Table.
Methods of the Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB with Table; Replace Column; Replace One-to-Many with Associative Tables; Replace Surrogate Key with Natural Key; Split Column; Split Table.
* Data Quality Refactoring
* Data Quality Refactoring
::A change which improves and/or ensures the consistency and usage of the values stored within the database.
::A change that improves and ensures the consistency and usage of the values stored in the database.
Methods of Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non Nullable; Move Data; Replace Type Code With Property Flags.
Methods of the Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non-Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non-Nullable; Move Data; Replace Type Code with Property Flags.

* Referential Integrity Refactoring
* Referential Integrity Refactoring
::
⚫
::A change which ensures that a referenced row exists within another table and/or that ensures that a row which is no longer needed is removed appropriately.
Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.
Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.
* Transformation
* Transformation
⚫
::A change that ensures a referenced row exists within another table and/or ensures that a row no longer needed is removed appropriately.
::A change which changes the semantics of your database schema by adding new elements to it or by modifying existing elements.
Methods of Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data.
Methods of the Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data
* Method Refactoring
* Method Refactoring
::A change which improves the quality of a stored procedure, stored function, or trigger.
::A change that improves the quality of a stored procedure, stored function, or trigger.
Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.
Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.


In 2019, Vladislav Struzik supplemented the categories of database refactoring with a new one:
In 2019 Vladislav Struzik supplemented the categories of database refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>
* Access Refactoring
* Access Refactoring
::A change which relates to data access.
::A change that relates to data access.
Methods of the Access Refactoring category:<ref name="access_refactoring_2">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік, С. В. Грибков, В. В. Чобану // Наукові праці НУХТ. – Т. 26, № 2. – 2020. – С. 31–49. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31515</ref><ref name="access_refactoring_medium"> ''Vladislav Struzik, PhD'' Refactoring: yesterday, today, tomorrow. URL: https://medium.com/@struzik/refactoring-yesterday-today-tomorrow-7fc8c845cfb1 </ref> Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.
Methods of the Access Refactoring category: Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.


==Process of database refactoring==
==Process of database refactoring==
Line 39: Line 41:
# How a single refactoring is implemented
# How a single refactoring is implemented
# How database refactorings are tracked and shared within organizations
# How database refactorings are tracked and shared within organizations
# How a series of database refactorings are applied
# How a series of database refactorings is applied


==See also==
==See also==

Revision as of 14:56, 10 August 2024

A database refactoring is a simple change to a database schema that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix bugs or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.

A database refactoring is conceptually more difficult than a code refactoring; code refactorings only need to maintain behavioral semantics, while database refactorings also must maintain informational semantics.

A database schema is typically refactored for one of several reasons:

  • To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
  • To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for database normalization of an existing production database, typically to "clean up" the design of the database.
  • To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.

Categories of database refactoring

In 2006, Scott Ambler and Pramod Sadalage described the following categories of database refactoring:

  • Architecture Refactoring
A change that improves the overall manner in which external programs interact with a database.

Methods of the Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table with View; Introduce Calculation Method; Introduce Index; Introduce Read-Only Table; Migrate Method from Database; Migrate Method to Database; Replace Method(s) with View; Replace View with Method(s); Use Official Data Source.

  • Structural Refactoring
A change to the table structure of your database schema.

Methods of the Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB with Table; Replace Column; Replace One-to-Many with Associative Tables; Replace Surrogate Key with Natural Key; Split Column; Split Table.

  • Data Quality Refactoring
A change that improves and ensures the consistency and usage of the values stored in the database.

Methods of the Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non-Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non-Nullable; Move Data; Replace Type Code with Property Flags.

  • Referential Integrity Refactoring

Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.

  • Transformation
A change that ensures a referenced row exists within another table and/or ensures that a row no longer needed is removed appropriately.

Methods of the Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data

  • Method Refactoring
A change that improves the quality of a stored procedure, stored function, or trigger.

Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.

In 2019, Vladislav Struzik supplemented the categories of database refactoring with a new one:

  • Access Refactoring
A change that relates to data access.

Methods of the Access Refactoring category: Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.

Process of database refactoring

The process of database refactoring is the act of applying database refactorings to evolve an existing database schema (database refactoring is a core practice of evolutionary database design). There are three considerations that need to be taken into account:

  1. How a single refactoring is implemented
  2. How database refactorings are tracked and shared within organizations
  3. How a series of database refactorings is applied

See also

References

Retrieved from "https://en.wikipedia.org/w/index.php?title=Database_refactoring&oldid=1239631426"