Greg (L), Tony
That's it then! BIGINT IDENTITY columns for SQL Server/Azure sound like the
easiest way out. I've never tried that combination before, never needed it,
but that will make my EF5 generated POCOs have identical properties for
both databases (I hope).
I actually admire the "clarity" of GUIDs, but I remember overnight how
irritating they are to manipulate in scripts and debugging windows. The
worse thing is filling lookup tables like this:
insert into Foo values('2b123a1b-e144-4448-8035-b336ad2ec93a', 'Option-1');
insert into Foo values('63bd431a-9032-4af1-acc4-06995d06c553', 'Option-2');
Things get cluttered really fast.
I should know more about how this plan works on the weekend and I'll report
anything useful.
Greg (K)
