florian.reischl (3/5/2009)

---

Wow, that's some news there! How can you not like identity columns? I tell database developpers to put 1 on each and every table in the database. Only in really really rare scenarios we don't put an identity column.

What's your sight on this? It puts an easy uniqueness to the rows for transmitting to another server, it's a perfect field for the update statements, and so is it for the delete. What's so wrong with it?

Hi J-F

I don't like it because of some reasons:

Replication

Our DBAs say they don't like it becase of replicatiion problems. Don't ask me, I'm no DBA and do not know very much about replication. I don't really believe this... :hehe:

Manipulation of many data

Our applications generate many data on client side before they become commited. We use an ID-Table which contains type (= table) specific ID-Ranges. So we can set new IDs to all new rows and then bulk insert them in one bulk.

The profit is that the client application can build all the data within the client application with their final IDs and without the @@IDENTITY select for further links to other objects (rows).

Resume

I think its just a subjective (maybe stupid) sight of me 😉 .

Greets

Flo