Aha! You're using the wrong word. The word you want is "identities", not "indexes". ("Indexes" is probably the right word in some other context, but in SQL, it's not.)
Yes, if you change the identity values in TableA, that will mess up TableB. You can handle that by adding a foreign key constraint to TableB:
alter TableB
add constraint FK_TableA foreign key (TableAID) references dbo.TableA(ID) on update cascade
Then, if you update TableA's ID, it will also update TableB.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon