Hidden pk as sequence

Update the internal AIS processing to have tables with no primary key use a hidden column with a sequence. Previous this would use the hidden column with a unique ID generator. The latter has proven to be a performance bottleneck. So simplify the code by removing the unique ID generator and using a sequence instead. 

The challenge here is may pieces of code assumed the hidden column/unique id, and needed to be touched/updated to correct.  The biggest headache here were the Alter Table changes trying to ensure the hidden column, sequence, and PK were correct passed along if unchanged or removed if adding a new PK. 


The full text service has a create listener which monitors all table creation and kicks off a background population of any full text index regardless of if there is data present.

What exactly is the underlying problem regarding "correct processing of identity sequences"? Would a new test case with an identity column cause the same issue? I'm yet to be convinced removing the service is anything but a band-aid.