I really am tempted to try it out sometime. I want it just to rid myself of the evil SEQUENCE crap in Oracle. I like the idea of generating the ID in my .NET code instead of having to retrieve it from Oracle via a second round trip. I hate Oracle.

For SQL Server, well... inserting a record and getting it's new ID back via the IDENTITY column type is SO easy as to be a no-brainer. Unless you need it for replication or whatnot.

Still, I'm tempted because I like to do things *one way* regardless of Oracle or SQL Server, but...

/sigh

Yeah, you do have a point there about doing things one way. I'm not sure if Oracle has anything like SQL Server's NEWID() function. But hey, you'll very rarely have one set of SQL code that can work on both RDBMS. Nor will you ever have one application code set that runs flawlessly on Oracle and SQL Server. It'll be a pretty simple app that does...

I have used the GUID approach a time or two. It didn't seem to cause any problems. One system was a very high throughput application that I was pretty impressed with using the GUIDs for keys.

I say, if you ever get the tickle, go ahead and scratch it. You might like the outcome.