Hi, The call tracking system was built on SQL Server 6.1. When it was upgraded to 6.5 the problem was resolved, and identity fields were not corrupted ever since.
Dave > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Weidl > Sent: Wednesday, May 22, 2002 12:18 PM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: Next WiTango_SQL conundrum > > > Hi, > > >Funny you should say that because while with EveryWare we had a support > >tracking system that was developed by Dave Shelley which used an > >autoincrementing identity field which consistently gave us fits > because it > >would become corrupt and start issuing duplicate values. > > There was a known problem in earlier versions of SQL Server (i.e. 6.x) > which somewhat regularly corrupted the autoincrement counter. The problem > seems to have been resolved in subsequent releases. > > If the support system database was an earlier version of SQL Server, I > think you safely ignore that experience now. > > Eric > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
