James,

I believe you would be better off using SQL Server's IDENTITY keyword on your PK column. You then would not need to have another table hold the last value used for a PK. This is only if your PK does not have any 'intelligence' in it.

Also, if you use this type in all or most of your PK's, you can still have alternate keys (AK), but your foreign key constraints will be based on these IDENTITY columns, thereby never having to do any cascading updates due to a change in the AK.