I am mass updating a SQL Server database. I am changing all our
numeric(38,0) columns to
int (yes, SQL Server scripts were created from Oracle scripts).
Using SMO and C# (I am a sw engineer), I managed to generate really nice scripts like SQL Server Management studio would. It all works very nicely except for one particular issue:
for a a handful of tables, when I call
ALTER TABLE [myTable] ALTER COLUMN [columnA] INT it decides to also change the column from
NOT NULL to NULL. That of course is a huge issue since I need to regenerate primary keys for most of those tables on those particular columns.
Obviously, I have plenty of options using SMO to find out which columns are primary keys and force them to be NOT NULL after or while I am updating the data type, but I am really curious as to what can be causing this.