+2  A: 

Considering i have to create a sequence for each table in Oracle (almost), would this be the standard accepted implementation for simulating Identity or is there a better / easier way to achieve this kind of implementation in Oracle?

Yes, it is very typical in Oracle to create a sequence for each table. It is possible to use the same sequence for several tables, but you run the risk of making it a bottleneck by using a single sequence for many/all tables: see this AskTom q/a

Are there any specific GOTCHA's related to having so many sequences in Oracle?

None that I can think of.

Tony Andrews
Thanks Tony - appreciate the inputs!!! Exactly the help that i was looking for.
InSane
+2  A: 

100+ tables is not very many. I routinely work on databases with several hundred sequences, one for each table. The more the merrier.

It's even conceivable to have more sequences than tables - unlike identity columns in other DBMSs, sequences can be used for more than just creating surrogate key values.

An alternative is to use GUIDs - in Oracle you can call SYS_GUID to generate unique values.

A good article, followed by comments with pros and cons for both approaches: http://rwijk.blogspot.com/2009/12/sysguid.html

Jeffrey Kemp
@Jeffrey - The advice is reassuring as it confirms that i am not doing something silly due to my inexperience with the product. Appreciate it. +1. Thanks!!
InSane