I ran the obvious fix on a SQL Server INT primary key, ALTER COLUMN id BIGINT NOT NULL, and got three errors back instead of a wider column.
Msg 5074, twice: the primary key and the foreign key from orders both depend on the column. SQL Server will not change a type while any key, index or schema-bound view still uses it, and ONLINE = ON returns the same error.
So the real migration is drop everything, alter, recreate. Testing how Schemity plans it on two 1,000,000-row tables, that took 20.5 seconds and grew the transaction log from 6 MB to 1 GB, with both tables locked the whole time.
https://schemity.com/blog/sqlserver-change-int-to-bigint-primary-key/

schemity.comSQL Server INT to BIGINT Primary Key: Four Ways to Change It and What Each One Costs - SchemitySchemity tested INT to BIGINT on a SQL Server key: ALTER COLUMN fails with Msg 5074 until the keys go. Four ways to widen it, and when each one fits.
commit 0dae922