Hi All,
Question: We're replacing an existing Oracle OLTP database with a new one in SQL 2012. Should we create a new IDENTITY column to be used by the new GUI, or should we continue to use the existing column that was an identity in the legacy system?
Background: Originally, we decided to migrate the legacy identity column to the new system but create a new IDENTITY column. I don't quite remember our reasoning now, and it seems that using the legacy identity column (without creating a new one) would be just fine. The only reason I can see for doing this would be a way to ID rows created in the legacy system from rows created in the new system.
The existing GUI will be pointed at the new database until it, too, is replaced by a new GUI.
Originally, my question was going to be "should we use some sort of numeric identity column for SalesOrderDetail," but then I couldn't remember why we had decided to create a new IDENTITY column in the new system. I see the legacy system never repeated values for SalesOrderDetailID, and I can think of no good reason for this.
Thanks,
Eric B.