Link to home
Start Free TrialLog in
Avatar of brgdotnet
brgdotnetFlag for United States of America

asked on

Adding columns to an old table could cause a crash in a stored procedure or view?

I have a database with over 150 tables and around 300 stored procedures. There is a table which has been used for a very long time now. Let call it "Customers". I need to add two new columns to this table, The columns can be null, however I am worried that the column addition might break a stored procedure or view. I have around 300 stored procedures that reference the "Customers" table. I don' know which of these stored procedures insert to the Customers table. 

I am thinking that only stored procedures that insert to the Customers table have the potential of crashing, however I am not sure. Maybe they would not crash since the two new columns can have null values. Has anyone ever had to deal with a similar issue?

ASKER CERTIFIED SOLUTION
Avatar of slightwv (䄆 Netminder)
slightwv (䄆 Netminder)

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of slightwv (䄆 Netminder)
slightwv (䄆 Netminder)

>>insert into tbl select * from tbl_2), the default values of the fields should work and there would be no problem either.

There could be if tbl_2 is the one that received the new column and tbl didn't get a new column.
There could be if tbl_2 is the one that received the new column and tbl didn't get a new column.
 in this case if there is an error.