[Syed]

One of our client’s DBA is experiencing an occasional SQL infinite loop problem that him and two of our VB programmers couldn’t figure out. Details are below; any help will be deeply appreciated if you have any clue. If you need more details I can provide that too.

Our client is running an IVR (Interactive Voice Response) application designed in VB6 by a leading IVR company. VB code connects to their SQL 6.5 server using the SQLOLEDB from VB application server, and inserts or updates record via a stored procedure in parent and child tables. This application works for few weeks and then SQL database goes into an infinite record insertion loop and inserts thousands of identical records only in child table until a major crash occurs. Client thinks the problem is in VB application not on SQL side. Please Help!

Thanks in advance

[kebo]

Originally Posted by Syed

One of our client’s DBA is experiencing an occasional SQL infinite loop problem that him and two of our VB programmers couldn’t figure out. Details are below; any help will be deeply appreciated if you have any clue. If you need more details I can provide that too.

Our client is running an IVR (Interactive Voice Response) application designed in VB6 by a leading IVR company. VB code connects to their SQL 6.5 server using the SQLOLEDB from VB application server, and inserts or updates record via a stored procedure in parent and child tables. This application works for few weeks and then SQL database goes into an infinite record insertion loop and inserts thousands of identical records only in child table until a major crash occurs. Client thinks the problem is in VB application not on SQL side. Please Help!

Thanks in advance

With out your code trying to debug your problem could wind up creating an infinite loop.
kevin

[nyquil]

I have to agree with kevin , w/o code, no real idea, only generalizations.

If I were tracing this, I'd check the stored procedure calls from the vb app. Set up a logging mechanism to account for each call. Also set up a specific user on the database, if not already, and have the vb app the only process to use that login to make it easier to decipher db logs.

Post any code relating to where the stored proc is called and the proc itself and we will see what else can be determined.

hope that gives a starting point