Are there any repercussions using Negative Primary Keys for tables (Identity Increment -1, Identity Seed -1 in SQL Server 2005)?
The reason for this is we\'re creati
I think having 2 sources is not the right reason for this approach, while technically allowed. It's not scalable (+1 to Larry Lustig's answer for that).
I would just create a view or stored procedure that combines both data, by converting the IDs as needed, and would have application to use it instead of direct table reads and unions. This would be scalable by modifying the view/SP later to add one more source.
If negative numbers turn out to break something, use even numbers for one and odd numbers for the other.
It is not an issue. Just make sure your Identity column is of a type that allows negative numbers.