Renaming Columns in DB Table: Apex SQL or Examine Dependenci

Join the discussion
Ask a follow-up here, or get your own question answered by working scientists, mathematicians and engineers — people, not an autocomplete.
Real named experts · corrections over time · the nuance an AI answer skips
3 replies · 3K views
Messages
7,822
Reaction score
13,151
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
Physics 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).