Is using MS SQL Identity good practice?

Question

Is using MS SQL Identity good practice in enterprise applications? Isn\'t it make difficulties in creating business logic, and migrating database from one to another?

Answer 1

Yes.

They generally works as intended, and you can use the DBCC CHECKIDENT command to manipulate and work with them.

The most common idea of an identity is to provide an ordered list of numbers on which to base a primary key.

Edit: I was wrong about the fill factor, I didn't take into account that all of the inserts would happen on one side of the B-tree.

Also, In your revised question, you asked about migrating from one DB to another:

Identities are perfectly fine as long as the migrating is a one-way replication. If you have two databases that need to replicate to each other, a UniqueIdentifier column may be your best bet.

See: When are you truly forced to use UUID as part of the design? for a discussion on when to use a UUID in a database.