Renaming Columns in DB Table: Apex SQL or Examine Dependenci

Click For Summary

Discussion Overview

The discussion centers around the best practices for renaming columns and tables within a database, particularly in the context of a class project. Participants explore different methods, including the use of Apex SQL, which is said to automatically check for dependencies, versus manually reviewing and changing dependencies one by one. The conversation also touches on the implications of renaming in modern relational database management systems (RDBMS) and the separation of business logic from database structure.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested
  • Homework-related

Main Points Raised

  • One participant questions whether renaming databases or tables/columns is being discussed, noting that modern RDBMSs treat database names as arbitrary parameters.
  • Another participant emphasizes the importance of separating business logic from the database structure, suggesting that changes to the schema should primarily involve adjustments in the code of the Data Access Layer (DAL) or similar paradigms.
  • A participant shares a resource for database models that could be useful for constructing schemas.
  • Concerns are raised about receiving warning messages from MSSQL2014 after renaming a table, indicating potential issues with dependencies that may arise during such operations.
  • There is mention of the distinction between Data Definition Language (DDL) and Data Manipulation Language (DML) in the context of renaming operations.

Areas of Agreement / Disagreement

Participants express differing views on the best approach to renaming within a database, with no consensus reached on whether to use automated tools like Apex SQL or to manually check dependencies. The discussion remains unresolved regarding the implications of renaming and the best practices to follow.

Contextual Notes

Some participants highlight the complexity of renaming operations due to potential dependency issues, but there is no agreement on how best to manage these challenges. The conversation also reflects varying levels of experience and understanding of database management practices.

WWGD
Science Advisor
Homework Helper
Messages
7,804
Reaction score
13,113
Hi All,
Just curious as to what those with experience in creating databases believe is the best method when
renaming databases: using Apex SQL , which (supposedly) automatically checks for dependencies or
just sitting down , looking at the dependencies and doing the changes one by one as needed? This is
for a class project. Also, can anyone recommend a good source for schemas to use , maybe
make changes to (EDIT: The project is for a company)?
 
  • Like
Likes   Reactions: Silicon Waffle
Technology news on Phys.org
Renaming databases is not an issue in modern RDBMSs as we work with connections in which the name of the database is an arbitrary parameter. Do you mean renaming tables and/or columns within databases?

In the real world (e.g. for a company), business logic is implemented in code which is linked to database structure. Ideally this is abstracted so that the business logic layer is separated from the data storage layer by at least one level, so alterations to the database schema need only be dealt with by altering the relevant code in the Data Access Layer (DAL)/Data Access Objects (DAO)/Object Relational Models (ORM)/whatever the paradigm you are using.
 
  • Like
Likes   Reactions: jim mcnamara and WWGD
MrAnchovy said:
Renaming databases is not an issue in modern RDBMSs as we work with connections in which the name of the database is an arbitrary parameter. Do you mean renaming tables and/or columns within databases?

In the real world (e.g. for a company), business logic is implemented in code which is linked to database structure. Ideally this is abstracted so that the business logic layer is separated from the data storage layer by at least one level, so alterations to the database schema need only be dealt with by altering the relevant code in the Data Access Layer (DAL)/Data Access Objects (DAO)/Object Relational Models (ORM)/whatever the paradigm you are using.

Thanks, Anchovy, I do mean renaming within a database. I did get a warning message from my MSSQL2014 in that respect for some reason after I renamed a table within a database. And there were error messages even when I "inverted" the renaming (i.e., I gave the table the original name), I had some. And I guess we use the names DDL (Data Definition Language) and DML (Data Manipulation Language) respectively, and in this case the renaming is done within a DDL , i.e., writing code , not doing within a GUI (Graphical Interface).
 

Similar threads

Replies
5
Views
3K
  • · Replies 50 ·
2
Replies
50
Views
9K
  • · Replies 5 ·
Replies
5
Views
3K
Replies
4
Views
4K
  • · Replies 7 ·
Replies
7
Views
4K
  • · Replies 7 ·
Replies
7
Views
7K
  • · Replies 1 ·
Replies
1
Views
4K
Replies
2
Views
3K
  • · Replies 4 ·
Replies
4
Views
7K
  • · Replies 1 ·
Replies
1
Views
1K