Thanks for all the input. The mystery has been solved.

The culprit was another stored procedure that dropped and created the shortened version of the table.

GilaMonster nailed it.

Thanks for the reply. You are correct it does not make sense. That is why I was looking for input.

As to why it is built this...