I believe that you will have to drop the foreign key constraints first. Then update all of the appropriate tables and remap them as they were. ALTER TABLE [dbo.Details_tbl] DROP CONSTRAINT [FK_Details_tbl_User_tbl]; — Perform more appropriate alters ALTER TABLE [dbo.Details_tbl] ADD FOREIGN KEY (FK_Details_tbl_User_tbl) REFERENCES User_tbl(appId); — Perform all appropriate alters to bring the key … Read more
I think you will need to do this as three separate statements. I’ve been looking around and everything i’ve seen seems to suggest you can do it if you are adding a column, but not if you are altering one. ALTER TABLE dbo.MyTable ADD CONSTRAINT my_Con DEFAULT GETDATE() for created UPDATE MyTable SET Created = … Read more
This is a metadata change only: it is quick. An observation: specify NULL or NOT NULL explicitly to avoid “accidents” if one of the SET ANSI_xx settings are different eg run in osql not SSMS for some reason
This is not possible. You will need to do this one by one. You could: Create a Temporary Table with your modified columns in Copy the data across Drop your original table (Double check before!) Rename your Temporary Table to your original name
Try this alter table TableName add constraint df_ConstraintNAme default getutcdate() for [Date] example create table bla (id int) alter table bla add constraint dt_bla default 1 for id insert bla default values select * from bla also make sure you name the default constraint..it will be a pain in the neck to drop it later … Read more
See documentation here: http://www.postgresql.org/docs/current/interactive/sql-altertable.html ALTER TABLE tbl_name ALTER COLUMN col_name TYPE varchar (11);
First, make all current NULL values disappear: UPDATE [Table] SET [Column]=0 WHERE [Column] IS NULL Then, update the table definition to disallow “NULLs”: ALTER TABLE [Table] ALTER COLUMN [Column] INTEGER NOT NULL