-2

i seem to be getting paranoid over 2 cases listed below. Can someone provide a general list of conditions for:

  1. when can columns not be added to an existing table

  2. when can columns not be altered

Please skip the reason for same name for either case.

N_E
  • 743
  • 10
  • 16
  • Dont have idea what are you asking. Are you talking about alter table permision? – Juan Carlos Oropeza Nov 03 '15 at 14:24
  • Which DBMS are you talking about? –  Nov 03 '15 at 14:27
  • no, my concern is about general design for database. – N_E Nov 03 '15 at 14:28
  • I am working with SQL Server Management Studio at the moment but i thought same would be apply for oracle – N_E Nov 03 '15 at 14:29
  • by the way, why the negative votes right away? – N_E Nov 03 '15 at 14:30
  • I still havent add negative vote yet, but your question doesnt make sense. In desing you can `add/alter`all the column you want. please read [**How to ask**](http://stackoverflow.com/help/how-to-ask) And [**How to create a Minimal, Complete, and Verifiable example.**](http://stackoverflow.com/help/mcve) – Juan Carlos Oropeza Nov 03 '15 at 14:33
  • For example: In below linked post http://stackoverflow.com/questions/689746/altering-a-column-null-to-not-null – N_E Nov 03 '15 at 14:47

1 Answers1

0

When can these things not happen? When the user trying to do them doesn't have permissions. Users should in general never have these permissions.(incidentally developers should not have prod permissions to do this sort of thing, so that all changes must be deployed with a script that is in source control) In SQL server, you also have DDL triggers that can be set up to prevent changes

HLGEM
  • 94,695
  • 15
  • 113
  • 186