:: 23-Mar-1999 05:43 (Tuesday) ::
As you’ve most likely noticed, I’ve been able to massage the stats database
back into sanity and things are running smoothly again. There’s code in
place which should detect if this runaway index problem strikes again which
will make corrective measures go much faster.
Anyone out there who was assigned an ID in the 5-6 million range has a new,
more reasonable ID in the 170,000 neighborhood.
Many thanks to Bradley Langhorst and wayne4@bellsouth.net for the tips
on Sybase identity field issues. While we still don’t know exactly what
is causing the behavior for certain, I think we’ve got a few good
working theories now.
More news as it happens… :)