By combining UUIDs and Auto Incremented Primary Keys, you loose the advantage of generating ids on…
Nicolas Froidure

At first this is what I thought, and am quite possibly wrong, but as I looked at it, SQL Server, at least, implements the sequential UUID as a function, which I assumed means you could call the function (e.g. select newsequentialid()) then use the returned value in subsequent inserts. Because it is still a GUID … right? … it should be guaranteed unique ID, but at least sequential enough to be used in a clustered index.

If I am mistaken, please help me understand so I can correct the post!

Thanks for reading and for your comment.